Description of problem: I have a 2-seat configuration. If I log out of the second seat, GDM does not appear until I reboot. Version-Release number of selected component (if applicable): GDM 3.16.1.1 How reproducible: Every time I tried (about 5 times) Steps to Reproduce: 1. Configure 2 seats with loginctl 2. Log on to the secondary seat 3. Log out of the secondary seat. Actual results: Screen goes black on the secondary seat. Expected results: GDM login screen appears on the secondary seat. Additional info: I upgraded via fedup from 21. I'm using the standard GNOME session. Logging on and off works fine on the first seat. The first seat is driven by an Nvidia card, and the second seat is driven by the Intel HD graphics. Is there any other information I can provide?
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.