Arch Linux

spirit

Member

Registered: 2010-03-19

Posts: 11

Re: GNOME 3.20 through Wayland

Hi,

It's working for me with putting XDG_SESSION_TYPE=wayland  in /etc/environment  , but not in /etc/profile.

wast3

Member

Registered: 2012-01-26

Posts: 27

Website

Re: GNOME 3.20 through Wayland

Wayland session starts fine and is perfectly usable with i915, but all applications run under XWayland unless I have GDK_BACKEND='wayland,x11' in /etc/environment.

In this case most gnome apps run fine in Wayland mode (Firefox, despite being compiled with gtk3, still runs under XWayland), but vdpau-based graphic acceleration doesn't work anywhere. Freshplugin, Geary,  Evolution all log Vdpau errors related to the VA-Api backend not starting. Firefox has glitches with html5 content on some sites (gfycat being one).

The guide also says to export CLUTTER_BACKEND='wayland', but if I do so GDM doesn't start at all.

Exporting QT_QPA_PLATFORM='wayland-egl' allows all Qt5 applications to run under Wayland. That works, but the look uniformity with gtk is lost. All Qt apps have different window borders, very strange fonts, and look generally very ugly.

Power draw seems higher in Wayland too.

All in all, Wayland experience improved, but it's still far from being usable on a day to day basis IMO, unless you run everything under XWayland, but then there's little point in having the two frameworks running on top of each other.

In the end, I uncommented WaylandEnable=false in in gdm and forgot about all of it :-)

Last edited by wast3 (2016-04-17 10:08:07)

sultanoswing

Member

Registered: 2008-07-23

Posts: 314

Re: GNOME 3.20 through Wayland

Am looking forward to Wayland developing in the months / years ahead, good luck to the team & testers!

Last edited by sultanoswing (2016-04-19 08:37:09)

---

6.5.3.arch1-1(x86_64) w/Gnome 44.4
Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | Intel NUC 7i5RYK | ASUS ux303ua | Surface Laptop

razerraz

Member

Registered: 2014-06-27

Posts: 8

Re: GNOME 3.20 through Wayland

All in all, Wayland experience improved, but it's still far from being usable on a day to day basis IMO, unless you run everything under XWayland, but then there's little point in having the two frameworks running on top of each other.

I don't agree with that.

I switch to wayland since gnome 3.20 release for allday usage, and I'm very happy with it. The main obstacle was the lack of network transparency since I was using ssh -X to draw a conky from remote hosts. I've changed my methods, creating sockets that just transport datas and not all the crap related to the display. It works a lot better this way, wayland misfeature force me to reconsider things a better way...

And you're right, I mostly use Xwayland apps (firefox, libreoffice, eclipse, gimp), and they are running faster this way. Try it on a small hardware, arm dev boards for instance, it's obvious. Besides, apps are less exposed to security holes X11 had for decades, and for all wayland support is WIP.

The only issues I have from now are :
Nothing like numlockx
Pure wayland (client and server) remote desktop viewing

leebickmtu

Member

Registered: 2016-06-07

Posts: 5

Re: GNOME 3.20 through Wayland

I am also missing the 'GNOME under Wayland' option since the Update to 3.20.
I can still see the Gear-Icon and the two options 'GNOME' and 'GNOME classic'.
How can I make the Wayland option reappear? or at least activate it manually?

Everything used to work under the previous GNOME version...
'GNOME on Wayland' is also shown in lightdm, only gdm does not seem to show it...

THX

I had this same problem and fixed it by enabling early KMS. Turns out KMS is required for GNOME on Wayland. It should have been loading KMS late anyways but the option was missing from GDM until I enabled early KMS.
Follow instructions here for enabling it in mkinitcpio.conf - https://wiki.archlinux.org/index.php/ke … _KMS_start

Last edited by leebickmtu (2016-06-07 04:35:36)

j1simon

Member

From: Denmark

Registered: 2016-01-28

Posts: 189

Re: GNOME 3.20 through Wayland

Today I've read this thread and I've tried to enable Wayland with:

$ cat /etc/environment
XDG_SESSION_TYPE=wayland
GDK_BACKEND='wayland,x11'

If I put these lines in /etc/profile doesn't work.

I have enabled Wayland in gdm too:

[daemon]
WaylandEnable=true
.....

But if I activate "AutomaticLogin", Wayland doesn't start because:

gdm-autologin][617]: GdmSessionWorker: Set PAM environment variable: 'XDG_SESSION_TYPE=x11'

When I enter in my gnome session I see these processes:

USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
gdm        642  0.0  0.0 178576  4468 tty1     Ssl+ 01:16   0:00 /usr/lib/gdm/gdm-wayland-session gnome-session --autostart /usr/share/gdm/greeter/autostart --debug
gdm        693  0.0  0.1 297380 42648 tty1     Sl+  01:16   0:00 /usr/bin/Xwayland :1024 -rootless -noreset -listen 4 -listen 5 -displayfd 6

Is Wayland running?
Because if I set GDK_BACKEND=wayland, GTK applications refuse to start with the error "Gtk-WARNING **: cannot open display: :0"
If I set QT_QPA_PLATFORM=wayland-egl, QT applications doesn't start with error: "Failed to create display (No such file or directory)"

I use the nouveau driver with an old NVIDIA card (GeForce GT 220).