Bug 1402274

Summary: gdm fails to start wayland session
Product: [Fedora] Fedora Reporter: mvetter <marcusvetter.gbugzilla>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 25CC: carwyn, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:51:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
failed_gdm_log.txt (journactl) none

Description mvetter 2016-12-07 07:29:56 UTC
Created attachment 1228909 [details]
failed_gdm_log.txt (journactl)

Description of problem:

On a system with two graphics cards (Intel integrated graphics controller and an AMD discrete card), gdm fails to start in Wayland mode.

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, gdm starts in wayland mode correctly.


Version-Release number of selected component (if applicable):
3.22.1

How reproducible:
Always.

Steps to Reproduce:
1. install extra graphics card
2. boot machine
3. gdm fails to start in Wayland mode

Actual results:
gdm and gnome-shell do not work in Wayland mode.

Expected results:
gdm and 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 stuff like this:
Dec 07 16:28:13 localhost.localdomain gnome-shell[1005]: Can't initialize KMS backend: could not find drm kms device
Dec 07 16:28:13 localhost.localdomain gnome-session[982]: gnome-session-binary[982]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Dec 07 16:28:13 localhost.localdomain gnome-session-binary[982]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Dec 07 16:28:13 localhost.localdomain gnome-session-binary[982]: Unrecoverable failure in required component org.gnome.Shell.desktop
Dec 07 16:28:13 localhost.localdomain gdm-launch-environment][852]: pam_unix(gdm-launch-environment:session): session closed for user gdm

The full log is attached.

Comment 1 Carwyn Edwards 2017-01-02 22:06:48 UTC
Seems like a duplicate of bug #1402283

Comment 2 Fedora End Of Life 2017-11-16 18:44:51 UTC
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.

Comment 3 Fedora End Of Life 2017-12-12 10:51:57 UTC
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.