GNOME Bugzilla – Bug 777669
Logging in with "GNOME" and not "GNOME on Xorg" still starts X11 instead of Wayland session
Last modified: 2018-05-24 11:32:03 UTC
On one of my two Fedora 25 machines, choosing the new "GNOME" session (instead of "GNOME on Xorg") in gdm still reliably gives me an X11 session: [jonas@falcon ~]$ loginctl SESSION UID USER SEAT 3 1000 jonas seat0 c2 42 gdm seat0 2 sessions listed. [jonas@falcon ~]$ loginctl show-session 3 --all | grep Type Type=x11 [jonas@falcon ~]$ On my laptop with a Fedora 25 installation, everything works fine. The affected gdm version is GDM 3.22.1.
I can also confirm this with GDM 3.22.1. After booting up, the first login always defaults to Xorg. To get to Wayland, I need to logout and back in. I don't know whether this affects it, but I also have GDM configured to use X11 instead of Wayland in its configuration file.
After doing some testing, it seems this only occurs when the GDM setting WaylandEnable is set to false. After setting it to true, the issue no longer persists.
I am getting an X11 session with the standard GDM config. In fact, I just added an explicit WaylandEnable=true and rebooted, and I'm still just getting an X11 session.
If you logout and back in without rebooting, are you then able to enter with Wayland? If you're using proprietary Nvidia graphics drivers (seeing as these aren't yet supported for Gnome), it's possible it may not even allow it and default to Xorg, though I'm not 100% sure of this. Just a theory.
When I logout and try to log back in, I can't (goes black for a short second then gdm login comes back) unless I pick "GNOME on Xorg" explicitly. Pretty weird. I'm using mesa radeon/i915 (dedicated AMD gpu + onboard gpu, a desktop PC).
I believe this is the same bug as the following: https://bugzilla.redhat.com/show_bug.cgi?id=1403512 I also have this issue as Jonas describes it. This seems to result from gnome-desktop/gdm not handling multiple graphics cards. Specifically in Jonas, and my case an integrated Intel iGPU and dedicated AMD GPU which are both not disabled. The temporary workaround is to add `i915.modeset=0` to the kernel boot parameters until its properly fixed. Below is my comment from the RH tracked bug (if i read it right, gdm doesnt have an issue with two gpus and wayland, its gnome-desktop when it tries to initialise with wayland): Fedora 26 Alpha Name : kernel Version : 4.11.0 Release : 0.rc5.git0.1.fc26 Arch : x86_64 Name : gnome-shell Version : 3.24.0 Release : 1.fc26 Arch : x86_64 Name : mutter Version : 3.24.0 Release : 1.fc26 Arch : x86_64 When logging in the desktop will silently fallback to x11 The following logs are produced from GDM: Can't initialize KMS backend: could not find drm kms device AMD Apr 08 19:46:16 jupiter gdm[989]: GdmDisplay: session type: wayland Apr 08 19:46:16 jupiter gdm[989]: GdmSession: setting session to type 'wayland' Apr 08 19:46:16 jupiter gdm[989]: GdmSession: type wayland, program? yes, seat seat0 Apr 08 19:46:16 jupiter gdm-launch-environment][1101]: GdmSessionWorker: Set PAM environment variable: 'XDG_SESSION_TYPE=wayland' Apr 08 19:46:17 jupiter gdm[989]: GdmSession: type wayland, program? yes, seat seat0 Apr 08 19:46:17 jupiter gdm[989]: GdmSession: type wayland, program? yes, seat seat0 Apr 08 19:46:17 jupiter gdm-launch-environment][1101]: GdmSessionWorker: start program: /usr/libexec/gdm-wayland-session "gnome-session --autostart /usr/share/gdm/greeter/autostart --debug" Apr 08 19:46:17 jupiter gdm-launch-environment][1101]: GdmSessionWorker: opening session for program '/usr/libexec/gdm-wayland-session' Apr 08 19:46:17 jupiter gdm-wayland-session[1127]: Enabling debugging Apr 08 19:46:17 jupiter gdm-wayland-session[1127]: Running session message bus Apr 08 19:46:17 jupiter gdm-wayland-session[1127]: session message bus already running, not starting another one Apr 08 19:46:17 jupiter gdm-wayland-session[1127]: Running wayland session Apr 08 19:46:17 jupiter gdm-wayland-session[1127]: session exited with status 0 Apr 08 19:46:23 jupiter gdm[989]: GdmSession: checking if file 'gnome.desktop' is wayland session: no Apr 08 19:46:37 jupiter gdm[989]: GdmSession: checking if file 'gnome.desktop' is wayland session: no Apr 08 19:56:07 jupiter gdm[989]: GdmDisplay: session type: wayland Apr 08 19:56:07 jupiter gdm[989]: initial setup doesn't have a wayland session, failing back to X11 Manually trying to launch a wayland gnome-shell sessions results in the following # dbus-run-session -- gnome-shell --display-server --wayland mutter-WARNING **: Can't initialize KMS backend: could not find drm kms device Adding i915.modeset=0 solves the problem, but this never used to happen as far as i remember.?
I have two GPUs in the affected machine as well, so this explains a lot!
Yes this would make sense. I too have dual GPU (intel + Nvidia in my case).
(In reply to CubeTheThird from comment #8) > Yes this would make sense. I too have dual GPU (intel + Nvidia in my case). In your case, nvidia binary drivers still don't support kms yet (as far as im aware) so it will silently default to x11 anyway even if your iGPU is disabled or using i915.modeset=0
I use mesa/i915 and mesa/radeon drivers, with an intel skylake i7-7600 GPU and AMD Radeon R7 270 (GCN 1.0 / Oland).
There is a relative bug https://bugzilla.gnome.org/show_bug.cgi?id=774306 But the result is contrary.
I have the same issue - however for me, trying to log into the wayland session simply throws me back to GDM with the following error in the journal: >gnome-shell[1221]: Can't initialize KMS backend: could not find drm kms device Disabling modeset is not really an option, because this is a laptop setup - primary intel + amd dgpu, and amdgpu does not support the "modeset" setting.
$ dbus-run-session -- gnome-shell --display-server --wayland (gnome-shell:3908): Can't initialize KMS backend: could not find drm kms device .. happens also on Ubuntu 17.10 with the GNOME wayland session on a Macbook with hybrid Intel/Nvidia cards (with nouveau driver). Would be neat if this could be fixed
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/294.