Comment 4 for bug 580755

I tried another idea:

I thought that, since the lock-up occurs during the sign-on process, I could bypass that stage by changing "login" to log me in automatically.

A little while after completing the boot menu, The message, as in comment #2 above, appeared (There is a problem with the configuration server. (/usr/lib/libconf2-4/gconf-sanity-check-2 exited with status 256).

I don't know whether the keyboard was locked at that stage, as when I pressed "enter" nothing seemed to happen for a while (I think that the OK button may have indicated a click; the message stayed on the screen for a fair while). But eventually it disappeared, & the desktop was displayed.

However, the mouse & keyboard were locked, so I could not use the PC.

Regards, Garry.