On a PC upgraded from F24 (and earlier to F25). When the Wayland based session was failing it was falling back to X and working, so this would seem to be a regression compared to the previous X based situation. This was the case with the monitor connected using HDMI to either onboard or external graphics. The PC has both an onboard Intel graphics chipset, and a PCIe Radeon card. Unfortunately there isn't an option in the BIOS to disable the onboard graphics or set priority. Wayland seemed to be failing, and the only clue in the logs was: gnome-shell: Can't initialize KMS backend: could not find drm kms device and gnome-session-binary: Unrecoverable failure in required component org.gnome.Shell.desktop Adding i915.modeset=0 to the kernel parameters via grub resolves the issue, with the monitor connected to the PCIe graphics card. I believe this is disabling modesetting for the onboard graphics which, to my uninformed mind, suggests something in the stack at or below Wayland wasn't dealing well with both being active (as I say, X clearly could cope with this, somehow).
I can confirm this also happens on my system. Logging into Fedora 25 Gnome wayland session fails on Dell laptop with Intel Haswell CPU and discrete Radeon HD 8790M graphics. This used to work fine on F24 w/ 4.7.x kernel. Hardware name: Dell Inc. Latitude E6540/0725FP Version-Release number of selected component (if applicable): Name : kernel-core Arch : x86_64 Epoch : 0 Version : 4.8.11 Release : 300.fc25 Name : gnome-shell Arch : x86_64 Epoch : 0 Version : 3.22.2 Release : 2.fc25 Name : mutter Arch : i686 Epoch : 0 Version : 3.22.2 Release : 3.fc25 I ended up disabling radeon kms mode setting by adding radeon.modeset=0 to grub. With this kernel configuration, I can now start Gnome Wayland session successfully.
Seems to be a similar problem to bug #1402283
Same here, desktop system CPU i915 based device + Nvidia discrete using nouveau: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) Adding i915.modeset=0 means that I no longer get this: Jan 02 17:32:09 fenix.rachub.curig.net gnome-shell[1025]: Can't initialize KMS backend: could not find drm kms device Jan 02 17:32:09 fenix.rachub.curig.net gnome-session[1017]: gnome-session-binary[1017]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Jan 02 17:32:09 fenix.rachub.curig.net gnome-session-binary[1017]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Jan 02 17:32:09 fenix.rachub.curig.net gnome-session-binary[1017]: Unrecoverable failure in required component org.gnome.Shell.desktop
I can confirm the above problem and solution. Pressing e at boot and setting i915.modeset=0 after quiet and then pressing ctrl+x fixes everything. $ loginctl Find my session number $ loginctl show-session <my session number> shows Type=wayland Before it used to show X11 no matter what was selected at login. The first login would fall back to X11. If I tried logged out and in again, it would just send me instantly back to the login screen. To get back in to GNOME I would have to select the x11 option in the dropdown at the login screen. If autologin is enabled this setting is unavailable, and the entire graphical interface is unusable.
I can confirm this as well 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 think this is the same bug https://bugzilla.gnome.org/show_bug.cgi?id=777669
This is still a problem. Fedora 26 beta using rawhide kernel (problem existed on main kernel as well). Name : kernel Version : 4.12.0 Release : 0.rc5.git2.2.fc27 Arch : x86_64 Name : gnome-shell Version : 3.24.2 Release : 1.fc26 Arch : x86_64 Name : mutter Version : 3.24.2 Release : 2.fc26 Arch : x86_64 System is a newly purchased Dell XPS 8920 desktop. lspci: 00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] (rev cf) Similar logs as others produced from GDM: Jun 18 18:47:41 fedora-workstation.localdomain gnome-shell[27410]: Can't initialize KMS backend: could not find drm kms device session-binary[27352]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Jun 18 18:47:41 fedora-workstation.localdomain gnome-session-binary[27352]: DEBUG(+): GsmAutostartApp: (pid:27410) done (status:1) Jun 18 18:47:41 fedora-workstation.localdomain gnome-session-binary[27352]: Unrecoverable failure in required component org.gnome.Shell.desktop Jun 18 18:47:41 fedora-workstation.localdomain gnome-session-binary[27352]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Jun 18 18:47:41 fedora-workstation.localdomain gdm-wayland-session[27308]: session exited with status 0 Jun 18 18:47:46 fedora-workstation.localdomain gdm[27159]: GdmSession: checking if file 'gnome.desktop' is wayland session: no Adding i915.modeset=0 renders graphics horribly, so that is not an option.
Just to confirm: This is still an issue on Fedora 26 stable: * kernel-4.12.8-300.fc26.x86_64 * gnome-shell-3.24.3-1.fc26.x86_64 * mutter-3.24.4-1.fc26.x86_64 Adding i915.modeset=0 works around the problem but it's not a solution if you use the IGPU as well.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.