Created attachment 1010634 [details] output of journalctl -a Description of problem: I installed system without user (I created just root). After g-i-s is finished on the first boot the system switches to gdm. I can log in to newly created user account. But when I want to power down the system the warning appears about another user still logged in - and it is still the same user. It seems that the original session where the g-i-s was run is still alive. Version-Release number of selected component (if applicable): gnome-initial-setup-3.16.0-1.fc22 gdm-3.16.0.1-1.fc22 Workstation Live Beta TC7 How reproducible: always Steps to Reproduce: 1. Install the system from TC7 image, don't create a user (just root) 2. boot to g-i-s and fill something. Finish it! Actual results: gdm appears after while Expected results: user session starts Additional info: This could be somehow connected to bug 1206404. It behaves nearly same, just gdm is started in this case. There is also flashing cursor on one of tty. I propose it for FE too.
I suspect it's more to do with the GDM-on-Wayland stuff, it's likely messing with the intended transitions? IIRC g-i-s user creation is meant to hand off straight into a logged in user session, there is not meant to be a login screen after g-i-s finishes. Note also that in a normal F22 boot at present, gdm remains running after you login to GNOME (gdm on tty1, GNOME on tty2). This is related to the Wayland stuff too.
Discussed at 2015-04-06 blocker review meeting: https://meetbot.fedoraproject.org/fedora-blocker-review/2015-04-06/f22-blocker-review.2015-04-06-16.00.log.txt . Rejected as an FE: roshi and sgallagh reproduced in the meeting and we agreed it wasn't significant enough to risk destabilizing GDM/g-i-s for, more of a polish issue better suited to be fixed after the Beta freeze.
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.