Comment 3 for bug 427947

I see that this issue has been idle for a while. Can only assume that the original poster managed to resolve. I have exactly the same issue in Lucid, and now in Maverick (the move to the alpha was in desperation, and not easily undone).

Where I differ is that I can reproduce the crash at will with a certain sequence of operations. I've also evolved a an operational procedure that avoids the issue.

Firstly I have an older machine AMD Athlone, 1GHz, 1GB ram, several disks, NVidia (older model). I'm running 10.10 Alpha aka Maverick Merkat. I am using the propriatry NVidia drivers.

To reproduce:

- First log in. All is normal.
- Lock terminal with Ctrl-Alt-L (I've remapped it to Ctrl-Alt-KPDelete). Screen saver should appear.
- move mouse so that the screen saver disappears and you are prompted for password to unlock.
- Do not supply the password. Instead select the "switch user" option. This is where my son was helpful in discovering this procedure.
- log in as a different user. All is normal.
- log out.

The expectation at this point is that you'll be returned to the locked screen where the first user would be able to supply original password to regain access. But no!

On logging out as the second user, the screen goes blank. There is no response from the mouse or keyboard (indeed even the CapLock and NumLock LED's are non-responsive). Alt-F1 will not bring forth a console.

Oddly, though, Alt-SysReq-REISUB does reboot the machine.

On my machine, this is 100% reproducable.

To avoid:

My machine is used by two people, myself and my son. We have agreed that when we are finished our sessions, we will not lock the screen and switch users, rather we will logout and log in again. So far this is avoiding the issue.

I would like to see this issue addressed so that the screen locking feature is functional.

So. What do you need from me to move this along?

Paul.