Description of problem:
If you try to switch user accounts (meaning live switching, not logging out), you'll very soon end up with just a blank gray screen and a cursor, nothing else.
This has been reported upstream here:
It is very easy to trigger this bug (or let's say it's very hard to not see this bug). You just need to create two users and play with account switching for a minute or two (switching, not logging out). Some reproducers are included in the upstream bug report. I've tried to find out the simplest reproducer and attach it below in the reproducer section.
I have attached a video here, please watch it:
The two users have a different wallpaper (a red and a green one) so that you can easily distinguish them.
After you end up in the gray screen, there's nothing you can do as a general user, there is no button and no keyboard shortcuts work (like ctrl+alt+del). I've tried to wait, and after waiting 7 minutes the screen was still all gray. The general user will need to hard-reset the machine.
Power users can switch to the existing user sessions using Ctrl+Alt+Fx shortcuts.
Version-Release number of selected component (if applicable):
confirmed on several different bare metal machines and also in a cleanly installed VM
confirmed by different users (all of my family members)
Steps to Reproduce:
1. create two users (let's call them Red and Green), reboot
2. log in as Red, click Switch User
3. log in as Green, click Switch User
4. log in as Red, click Switch User
5. see blank gray screen
user switching is broken
users can switch their profiles without problems
I'm proposing this as a F22 Beta blocker due to this criterion:
"Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops. "
Account switching is not mentioned in that criterion, but it seems to me that it's in the same spirit as "logging out" (and logging in, which is in a different criterion), it's just not explicitly mentioned.
Alternatively, this can be considered to be a conditional violation of all of our graphical-related criteria, provided that multiple users use your machine and use account switching. The user in question is either precluded from returning to his or her existing session, or even logging in completely (see the first use case in the upstream report). Once that happens, only hard reboot "resolves" this for a general user.
I tested it and it really fixes the problem, great!
Ray, would it be difficult to push the same fix into F21 as well? It's a very visible issue.
gdm-3.14.1-3.fc21 has been submitted as an update for Fedora 21.
This is still not fixed, please refer to the upstream report.
Discussed at Fedora Blocker Review Meeting 2015-01-26
AcceptedBlocker for Beta - This bug is a conditional violation of the criterion: "Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops." As "Switch User" is an offered mechanism.
The core problem seems to have been fixed in gdm 3.15.90, per the upstream report. There is still some mouse cursor related issue present, but that will be filed separately (and I'll propose it as another blocker, if needed).
maybe we should keep this open for f21 still?
Ugh, I still experience issues on bare metal, I'm adding back the blocker bug keywords :/ Let me know if it makes sense to split this into two bugs, one for F21 and one for F22.
This has been fixed upstream. Now we just need a new build for F22.
Near as I can tell, this can be closed: the fix - https://git.gnome.org/browse/gnome-shell/commit/?id=b1de1ada25ef155f20864447c78b0e18c71a5586 - went into GNOME Shell 3.15.92, which is in stable for F22 already.
I am closing this again provisionally, feel free to re-open if I interpreted wrongly.
gdm-3.14.2-1.fc21 has been submitted as an update for Fedora 21.