Created attachment 1228916 [details] failed_wayland_gnome_shell_log.txt (journalctl) Description of problem: On a system with two graphics cards (Intel integrated graphics controller and an AMD discrete card), gnome-shell crashes in wayland mode (returns to the gdm login screen). The machine is using the Intel integrated graphics for video output. The AMD card has no monitors attached to it. It's only used for GPGPU computing via OpenCL. When the AMD card is removed, gnome-shell works correctly in wayland mode. Version-Release number of selected component (if applicable): 3.22.2-2.fc25 How reproducible: Always. Steps to Reproduce: 1. install second graphics card 2. boot machine 3. gnome-shell fails in Wayland mode Actual results: gnome-shell does not work in Wayland mode when two graphics cards are present. Expected results: gnome-shell should work in Wayland mode, no matter how many video cards the system has. Additional info: kernel 4.8.11-300 extract from lspci: 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: Advanced Micro Devices, Inc. [AMD/ATI] Oland GL [FirePro W2100] journalctl log has: Dec 07 16:32:49 localhost.localdomain gnome-shell[2222]: Can't initialize KMS backend: could not find drm kms device Dec 07 16:32:49 localhost.localdomain gnome-session[2189]: gnome-session-binary[2189]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Dec 07 16:32:49 localhost.localdomain gnome-session-binary[2189]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Dec 07 16:32:49 localhost.localdomain gnome-session-binary[2189]: Unrecoverable failure in required component org.gnome.Shell.desktop Dec 07 16:32:49 localhost.localdomain gdm-password][2164]: pam_unix(gdm-password:session): session closed for user tmp I've attached two logs: one for booting into gdm, and one for attempting to log in using gnome-shell.
Created attachment 1228917 [details] failed_gdm_log.txt (journalctl)
Same problem happens when the AMD card is swapped out for an Nvidia card.
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
Same with these two cards on F25: 0: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) nouveau is the primary with the i915 unused.
Seems to be a similar problem to bug #1403512
Same here, workaround with radeon.modeset=0 helped with the problem.
Issue persists in Fedora 27 on HP Spectre x360 13 ( i7-8th gen ) when thunderbolt 3 eGFX enclosure is connected. lspci shows both video adapter ( onboard intel, and eGFX which is an nVidia GTX1080 card ). With i915.modeset=0 kernel param, the eGFX adapter works fine, but the laptop display is not available for Wayland.
Ok, I take it back. I performed the following: * Added the following line to /etc/udev/rules.d/99-thunderbolt.rules ACTION=="add", SUBSYSTEM=="thunderbolt", ATTR{authorized}=="0", ATTR{authorized}="1" * removed the i915.modeset=0 kernel option * Rebooted with the Thunderbolt 3 eGFX enclosure connected * Profit Environment: * OS: Fedora 27 * Kernel: 4.13.12-300. * Enclosure: Mantiz Venus MZ-02 * eGFX card: Asus ROG STRIX GTX1080 card installed
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.