You are not logged in.
Hi everybody,
On my Archlinux installation I am running GNOME. I have been trying to run GNOME through wayland, however, in such case I cannot run X11 applications (e.g. Firefox, LibreOffice). Running GNOME on Xorg, everything works fine. I am wondering how to properly run GNOME on wayland while being able to run X11 applications.
My setup:
* A HP Elitebook 8570W notebook, having an AMD Firepro M4000 (Cape Verde) GPU.
* As driver I installed ATI (mesa package)
* As DE I run GNOME, booted by gdm.
* The following xorg packages are installed, among which certainly xorg-server-xwayland
xorg-bdftopcf 1.1-1
xorg-font-util 1.3.1-1
xorg-font-utils 7.6-4
xorg-fonts-alias 1.0.3-1
xorg-fonts-encodings 1.0.4-4
xorg-fonts-misc 1.0.3-5
xorg-mkfontdir 1.0.7-8
xorg-mkfontscale 1.1.2-1
xorg-server 1.19.5-1
xorg-server-common 1.19.5-1
xorg-server-xwayland 1.19.5-1
xorg-setxkbmap 1.3.1-1
xorg-xhost 1.0.7-1
xorg-xkbcomp 1.4.0-1
xorg-xrdb 1.1.0-2
xorg-xset 1.2.3-1* Obviously, everything is fully up to date running a vanilla 64bit Archlinux.
What I have done so far:
1. In order to properly boot GNOME on wayland I added:
MUTTER_ALLOW_HYBRID_GPUS=1to /etc/environment as the elitebook has both intel as well as ati graphics cards.
With this, GNOME on wayland boots fine, running terminal, evolution etc. Firefox however does not boot.
2. In order to test wayland I have been running weston as well. Weston boots fine with in GNOME legacy.
Weston.ini looks like:
[core]
#modules=xwayland.so
xwayland=true
[launcher]
icon=/usr/share/icons/hicolor/24x24/apps/firefox.png
path=/usr/bin/firefoxIf modules=xwayland.so is left uncommented weston reports an old loading method is used and requests xwayland=true to be used. Behavior is equal in both cases.
Running Firefox through weston results in the same behavior as on GNOME, i.e. two processes which do not respond and no single window created.
Weston reports:
Gdk-message: firefox: fatal IO error 111 (connection refused) on Xserver :1. and
failed to bind to @/tmp/.X11-unix/X0: Address already in use3. I have reinstalled firefox, but that doesn't solve the problem
Some logs:
https://pastebin.com/mwhZR0U4 - Xorg.0.log from /var/log
https://pastebin.com/i8sttCB9 - Xorg.1.log from /var/log
https://pastebin.com/u6aPLF4W - Xorg.0.log.old from /var/log
https://pastebin.com/QxR10ayN - dmesg | grep ati
https://pastebin.com/f1jZCdy6 - dmesg | grep radeon
https://pastebin.com/88PcGSGR - weston output while running weston and launching firefox
Any help on properly running X11 applications through wayland is greatly appreciated.
I am completely new to the forum, hence any feedback regarding missing information, logs, etc is welcome. I have been searching for any error code, but have not found anything so far. Apologies if anything has been missed.
Offline
Have you read the Arch Wiki? It clearly stated that gnome session the default session uses wayland by default and that there's apparently an option called GNOME on Xorg for things that don't work yet see:
https://wiki.archlinux.org/index.php/GN … E_Sessions
For details!
Have you read the Arch Wiki? It clearly stated ...
It's also clear that you don't know what xwayland is and didn't understand a word of the OP's post. Please don't do this.
Last edited by Scimmia (2017-12-19 18:22:40)
Offline
Stewart Little wrote:Have you read the Arch Wiki? It clearly stated ...
It's also clear that you don't know what xwayland is and didn't understand a word of the OP's post. Please don't do this.
Sorry!
There shouldn't be any extra steps necessary. X applications should work out of the box via XWayland on Gnome under wayland (as long as xorg-server-xwayland is installed, but afaik gnome shouldn't start on wayland without it).
My best guess is this has something to do with your hybrid graphics setup.
Offline
There shouldn't be any extra steps necessary. X applications should work out of the box via XWayland on Gnome under wayland (as long as xorg-server-xwayland is installed, but afaik gnome shouldn't start on wayland without it).
My best guess is this has something to do with your hybrid graphics setup.
At least good to know that I didn't skip any xwayland configuration steps I couldn't find! For the Hybrid Setup, could it be that xwayland automatically wants to bind to the first graphics card, but actually needs the second?
Sadly, hybrid graphics are seen much more often nowadays to increase power efficiency: if working as intended the radeon card should only render for heavier duties with the intel running onboard for battery efficiency. Does give headaches though.
If anybody has any clue that would be highly welcome :).
Offline
At least good to know that I didn't skip any xwayland configuration steps I couldn't find! For the Hybrid Setup, could it be that xwayland automatically wants to bind to the first graphics card, but actually needs the second?
XWayland doesn't bind to any hardware. It is basically a normal Xorg server which talks to X11 clients, but instead of talking to hardware it is just another Wayland client. E.g. see https://www.phoronix.com/scan.php?page= … Documented.
Offline
pianorama wrote:At least good to know that I didn't skip any xwayland configuration steps I couldn't find! For the Hybrid Setup, could it be that xwayland automatically wants to bind to the first graphics card, but actually needs the second?
XWayland doesn't bind to any hardware. It is basically a normal Xorg server which talks to X11 clients, but instead of talking to hardware it is just another Wayland client. E.g. see https://www.phoronix.com/scan.php?page= … Documented.
Thanks! That is insightfull. If xwayland talks to another wayland client, hardware cannot explain the current behavior right? Do you have any idea where
failed to bind to @/tmp/.X11-unix/X0: Address already in usecomes from? I have been trying to google it but to no avail.
Offline
Do you have any idea where
failed to bind to @/tmp/.X11-unix/X0: Address already in usecomes from? I have been trying to google it but to no avail.
You can check which process is using that file with fuser.
You could also check if XWayland process is running after you've started gnome or weston, to determine whether XWayland fails to start, or if clients fail to connect with it for some reason. (To my knowledge gnome-shell shouldn't run withouth Xwayland though, so I'd imagine it was the latter).
Offline
A bit late response from my side, but I'm thankfull for the directions anyway:
Booting Weston within GNOME reports: "failed to bind to @/tmp/.X11-unix/X0: Address already in use". Inspecting the file with fuser reports:
/usr/lib/xorg-server/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/XauthorityMoreover, I can confirm that when running Gnome Legacy, Xwayland is indeed running. Launching weston in a new TTY does not report a failed to bind.
Hence, I do not think the failed to bind error will lead us any closer to the solution, as it seems to be Gnome - Weston specific.
Let me try to find some more in Gnome On Weston
Offline