gdm login fails on Wayland

English Install/Boot/Login
1

Good day

I am having trouble logging into Gnome on Wayland.

I have my display manager set to GDM, which works fine but when I select GNOME (Wayland) it fails with the following logged in journalctl.

Mar 27 12:35:25 largo.site gnome-shell[6130]: libnm symbols detected; Mixing libnm with libnm-util/libnm-glib is not supported
Mar 27 12:35:25 largo.site org.gnome.Shell.desktop[6130]: == Stack trace for context 0x5638c29ad4c0 ==
Mar 27 12:35:25 largo.site org.gnome.Shell.desktop[6130]: #0 0x5638c2d77950 i resource:///org/gnome/shell/ui/status/network.js:1648 (0x7f61c9f232b8 @ 52)
Mar 27 12:35:25 largo.site org.gnome.Shell.desktop[6130]: #1 0x7ffda0115c60 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f620c3b4de0 @ 71)
Mar 27 12:35:25 largo.site org.gnome.Shell.desktop[6130]: #2 0x7ffda0115d30 b self-hosted:917 (0x7f620c3ebef0 @ 394)
Mar 27 12:35:25 largo.site systemd[1]: Started Process Core Dump (PID 6417/UID 0).
Mar 27 12:35:26 largo.site org.gnome.Shell.desktop[6130]: (EE) failed to read Wayland events: Connection reset by peer
Mar 27 12:35:26 largo.site gnome-session[6097]: gnome-session-binary[6097]: WARNING: Application ‘org.gnome.Shell.desktop’ killed by signal 5
Mar 27 12:35:26 largo.site gnome-session-binary[6097]: Unrecoverable failure in required component org.gnome.Shell.desktop
Mar 27 12:35:26 largo.site gnome-session-binary[6097]: WARNING: Application ‘org.gnome.Shell.desktop’ killed by signal 5
Mar 27 12:35:26 largo.site gsd-keyboard[6331]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 27 12:35:26 largo.site org.gnome.SettingsDaemon.Keyboard.desktop[6331]: libGL error: Connection closed during DRI3 initialization failure
Mar 27 12:35:26 largo.site org.gnome.SettingsDaemon.Color.desktop[6327]: libGL error: Connection closed during DRI3 initialization failure
Mar 27 12:35:26 largo.site gsd-color[6327]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 27 12:35:26 largo.site org.gnome.SettingsDaemon.Wacom.desktop[6309]: libGL error: Connection closed during DRI3 initialization failure
Mar 27 12:35:26 largo.site org.gnome.SettingsDaemon.MediaKeys.desktop[6337]: libGL error: Connection closed during DRI3 initialization failure
Mar 27 12:35:26 largo.site org.gnome.SettingsDaemon.XSettings.desktop[6308]: libGL error: Connection closed during DRI3 initialization failure
Mar 27 12:35:26 largo.site gsd-wacom[6309]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 27 12:35:26 largo.site org.gnome.SettingsDaemon.Clipboard.desktop[6324]: libGL error: Connection closed during DRI3 initialization failure
Mar 27 12:35:26 largo.site org.gnome.SettingsDaemon.Power.desktop[6293]: libGL error: Connection closed during DRI3 initialization failure
Mar 27 12:35:26 largo.site gsd-media-keys[6337]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 27 12:35:26 largo.site gsd-xsettings[6308]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 27 12:35:26 largo.site gsd-clipboard[6324]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 27 12:35:26 largo.site gsd-power[6293]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Mar 27 12:35:26 largo.site at-spi-bus-launcher[6161]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server “:0”
Mar 27 12:35:26 largo.site at-spi-bus-launcher[6161]: after 21 requests (21 known processed) with 0 events remaining.
Mar 27 12:35:26 largo.site gdm-password][6077]: pam_unix(gdm-password:session): session closed for user xxxxxxxxxxxxx
Mar 27 12:35:26 largo.site gdm[2918]: GdmDisplay: display lasted 4.755913 seconds

os-release

NAME=“openSUSE Tumbleweed”

VERSION=“20180324”

ID=opensuse
ID_LIKE=“suse”
VERSION_ID=“20180324”
PRETTY_NAME=“openSUSE Tumbleweed”
ANSI_COLOR=“0;32”
CPE_NAME=“cpe:/o:opensuse:tumbleweed:20180324”
BUG_REPORT_URL=“https://bugs.opensuse.org”
HOME_URL=“https://www.opensuse.org/”

Any help would be appreciated.
Thanks

2

This might not help much.

Login to Gnome-Wayland works fine for me (using GDM). I have Intel graphics and only standard Tumbleweed repos (including Packman).

It is known that Wayland has problems with some video hardware (such as nVidia). I don’t know if that is relevant to your problem.

In any case, the places to look are your video hardware, and whether you are using non-standard repos.

3

In ***dora I had problems with Nvidia and Wayland. I disabled Wayland from gdm. From what I read I understand that Wayland is not very good to go now. Especially with Nvidia.

4

No problem with Nvidia Driver + Wayland + Lightdm+Yast…ecc

http://s18.imagestime.com/out.php/i1164106_Schermatada20180327161154.png](http://www.imagestime.com/imageshow.php/1164106_Schermatada20180327161154.png.html)

5

I am glad to hear that.
Sorry for off-topic - do you have problems with gnome-shell memory leaks in gnome 3.28?

6

I got it to work, mostly.

GDM and Gnome works on Wayland but there are a few issues such as the mouse movement that lags, transparency doesn’t work and overall degraded performance.

Just for interest sake I’m running openSUSE Tumbleweed 20180324 on a MacBook Pro 10,1 with an NVIDIA GeForce GT 650M Mac Edition display adapter using the Nouveau driver.
I’m sure using the NVidia driver will resolve the degraded performance.

Thanks

7

I also had the same problems. That’s why I said that “Wayland is not very good to go now”.

8

I’m lucky, I do not find any problem:)

9

There was something strange, Wayland that was fine like Xorg, trying to make it work I modified files in Root and I was thinking of using Wayland, but it was not so “echo $ XDG_SESSION_TYPE” does not tell the truth, my session is Xorg, I realized why I uninstalled Wayland and the answer from “echo $ XDG_SESSION_TYPE” was always wayland

I am mortified

10

echo $WAYLAND_DISPLAY
If did not contain any value, no Wayland.