Created attachment 1084456 [details]
journal from an affected boot

This is a journal from an affected boot. It's the first boot after install; it includes g-i-s user creation, then login, then the first logout attempt fails with this bug. Note: I then went out and tried to log out two more times, as I was working on other bugs too. The first logout attempt is the one relevant to this bug.

Created attachment 1085268 [details]
updated journal (23 Final RC2)

Still happens with 23 Final RC2; attaching updated journal, this time with only this bug in it (no subsequent logout/login attempts). I *did* see the distinctive 'pebbled grey' GDM background very briefly. When I click 'log out' what actually happens is the screen goes blank briefly, then comes back to the desktop - just between the blank screen and the desktop I briefly saw a flash of the GDM background, it seemed.

I guess this is technically a violation of "Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops." - https://fedoraproject.org/wiki/Fedora_23_Beta_Release_Criteria#Shutdown.2C_reboot.2C_logout - when installing Workstation and just for the first logout. I'd probably be inclined to -1 and CommonBugs it, but we should at least discuss it.

I just hit this with TC2 workstation x86_64

Hmm, in fact, it seems it logs you out and automatically logs you back in. I just hit it again, and I had a console open; when it came back to the desktop, the console was gone.

Oooh!

I wonder if this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1272706 somehow? The session that g-i-s tries to set up when you finish it instead is somehow 'kicking in' after you first log out?

Created attachment 1085327 [details]
my journalctl (23 Final RC2)

Reproduced here on the first login, with TC2 workstation x86_64 on a qemu-kvm guest.

Additionally, I noticed some details:
1) After hitting the bug, I switched to another VT with Ctrl+Alt+F3 in order to retrieve journalctl's log.
2) Then, I've tried to switch back and the virtual screen "freezed". I issued a reboot via virt-manager.
3) I'm hitting this on every boot, don't know if it may be related or not: https://bugzilla.redhat.com/show_bug.cgi?id=1259985.

so yeah, I just did an install creating a user in anaconda instead of in g-i-s, and the first log out attempt worked.

OK, yeah, seems like it's definitely caused by 1272706. Every time I hit that bug - i.e. after creating a user in g-i-s I get sent to GDM, not to a logged-in desktop - I also hit this bug: when I log out, I'm immediately logged back in. Any time I *don't* hit that bug, I don't hit this bug either: the first logout works.

So I suspect what's happening is some kinda race. g-i-s tries to start up a session as the user you just created, but it doesn't do it fast enough or does it too fast or something(?), and GDM comes up. You log in manually. When you log out, the session g-i-s was trying to start up 'kicks in' somehow. I'll poke about at the code a bit, but probably a dev is more likely able to spot the cause of this than me.

FWIW, I hit the two bugs testing both in a KVM and on bare metal almost all the time (think once or twice I got lucky). I managed to get a successful g-i-s to session transition only by adding 'nomodeset', as suggested by kalev, in a VM boot.

Discussed at 2015-10-22 Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-meeting-2/2015-10-22/f23-final-go_no_go-meeting.2015-10-22-16.00.log.txt . As this is a one-time bug and easy to document (though it's bad from a polish perspective) this was rejected as a blocker, but it was accepted as a freeze exception because, indeed, it's pretty bad OOTB polish and we should fix it if possible.

I've also seen this on F25 alpha when gnome-settings-daemon wasn't reacting to any IPC due to bug #1366775.

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.