Bug 1225665
Summary: | GDM does not appear after logging out on a secondary seat | |||
---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | C. N. <vkngbrsrkr> | |
Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 22 | CC: | jnuzman, rstrode | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1413052 (view as bug list) | Environment: | ||
Last Closed: | 2016-07-19 14:18:09 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: | ||
Embargoed: |
Description
C. N.
2015-05-27 23:33:53 UTC
I experience the same problem with my multiseat setup. In my case, the first seat is driven by an Intel HD GPU and the second by an AMD card. I'm using the same GDM version (gdm-3.16.1.1-1.fc22.x86_64) on Fedora 22. A few observations: * This issue does *not* occur when Wayland greeter is disabled (WaylandEnable=false in /etc/gdm/custom.conf). With X11 greeter on both seats, it is possible to log in and log out on the second seat with no issues. * The Wayland greeter only runs on the first seat. The second seat always uses the X11 greeter. * The gdm session appears to be started successfully after log out on the second seat, but the screen is blank. Killing the gdm session to force restart of a new session on the second seat does not fix the problem. (On the other hand, restarting gdm.service brings up a working greeter on both seats.) Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. |