Red Hat Bugzilla – Bug 443050
Fast User Switching not working at all
Last modified: 2015-01-14 18:20:56 EST
Description of problem:
Fast User Switching doesn't seem to work in today's rawhide (fresh install).
Just one normal user created, if I log in, click on the User Switch Applet,
choose Other and on the GDM login screen choose back the only normal user
(which has "Already logged in" text next to it), enter password resp. swipe
finger, then the screen just flickers and after 2s or so I'm offered the GDM
login screen again, this time without the "Already logged in" text next to my
login name. I can reproduce this reliably, every time.
Version-Release number of selected component (if applicable):
I'd note that even the home directory was created freshly, so this isn't related
to garbage from older distros in $HOME/.* directories or files.
Fast user switching isn't working here either. A fresh preview release install
updated to rawhide.
Two users already logged in
User 2 locks screen
User 1 clicks 'switch user' on screensaver
User 1 enters password in GDM to access current session
Screen flickers and then returns to GDM screen again
User 1's session has been unlocked, but GDM has switched to the wrong virtual
terminal. If you use Ctrl-Alt-Fn you find the active session ready to use.
This happens most if not every time and is a very visible failure of previously
Given the closeness of the F9 release I'm surprised this regression isn't
getting some attention.
Seems to be fixed in gdm-2.21.10-0.2008.04.28.1.fc9. You can get it from koji:
or just wait a day or two for it to land in rawhide.
I see just very limited improvement, from the 8 attempts to fast switch user 6
attempts were unsuccessful and 2 were successes, with 2.21.10-0.2008.04.28.1.fc9
and 3 users. In the unsuccessful case I'm thrown back at the GDM greeter screen
instead of the desktop switched away from earlier, or, in the last attempt I got a
Unable to start new display, Could not identify the current session dialog already
when clicking on the FAS applet.
Note Jakub and Martin have different issues. Jakub only has one user on his system.
Not anymore, for testing I've useradd(8)ed two further users, with freshly
created homes and no configuration changes whatsoever for them. Then
unsuccessful switching attempts were both from switching to a different, but
already logged in, user, and from switching to the same user.
Did you make sure gdm was fully restarted (telinit 3; telinit 5) after updating
Yes, the laptop was rebooted after upgrade.
Jon found some issues related to ending up on the wrong vt because we shut down
the greeter X server after switching to the new user's VT.
He's addressing them now which will hopefully fix a lot of problems people are
Can you please try:
No improvement with gdm-2.21.10-0.2008.04.29.2.fc10.i386.
After some unsuccessful switching attempts I've created fresh 3 new users
(foo) and rebooted. Logging in as foo3 in gdm, type password, clicking on
Other in FUS applet, got to GDM greeter. Click foo3 again, type password and
after short screen flicker I'm back at GDM greeter, with no user marked as
logged in. Log in as foo3 again, click on Other in FUS applet, got Unable to
start new display/Could not identify the current session dialog and the screen
got locked. Typed foo3's password, the dialog was still there. Chose Lock
Screen from menu,
Switch User, got to GDM greeter, logged in as foo4, chose foo3 in FUS applet,
got locked screen for foo3 and could actually successfully switch to foo3 after
typing foo3's password. The FUS applet doesn't mention foo4 user though, which
is logged in, only Other. Click Other, got back Unable... dialog and locked
screen, chose Switch user. Both foo3 and foo4 are marked in GDM Greeter as
logged in, log in as foo5. FUS applet shows me foo3/foo4/foo5 users (foo5
grayed out), pick Other. Now in GDM greeter only foo4 and foo5 are marked as
At this point, I believe this is an update candidate, not a release blocker.
So there is more than one thing going on here. The "Unable to start..."
message is due to bug #444500 .
Does it look like your x server is crashing? That would explain why users are
no longer showing up as logged in.
Apparently X server wasn't crashing, nor the 2.22.0-1.fc9 gdm helped.
But finally after yum updating tonight which installed:
it works just fine.