Bug 13300

Description of problem:

When using the "Switch user" facility, clicking on "Cancel" instead of activating a session or starting a new session leads to a situation in which the only option de facto available is to unlock the current session -- the "Switch user" button is shown, but does nothing. The reason for this is that there are now two separate instances kscreenlocker_greet running. The workaround is to do console login (Ctrl-Alt Fn) login as root and kill the later instance of kscreenlocker_greet. The problem also becomes visible if in such a situation one clicks on "Unlock" -- the result is quite obviously two overlayed windows.

(BTW, the text on the three-button switcher window still says that the default session is usually assigned to F7. That' no longer the case. It is usually F1 oe F2.)

Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1. Invoke "Switch user" (Application Menu -> Leave -> Switch User)
2. Start another session
3. Invoke "Switch user" again (as either of the two users
4. In the resultin window click the "Switch Users" button
5. The window expands, offering "Activate", "Start New Session" and "Cancel"
6. Click on "Cancel"
7. On the resulting window the "Switch user" now does not respond to clicks


Reproducible: 

Steps to Reproduce: