Bug#443059: Keyboard freezes - probably shouldn't be a closed bug.
I've seen this problem in several hardware combinations - using the
i810 driver on real hardware and vmware drivers under VMWare Fusion on
a Mac. I don't think the BusType hack is a good enough solution to
warrant closing this bug - there's some sort of nasty interaction with
gdm which causes this. I've found using other login managers (kdm or
xdm) I never see the problem, but with gdm I do, on most boots of my
virtual machine. Normally one of two things happens:
1) I can't log in at the gdm greeter at all
2) I can log in, but the keyboard lockup happens during the session a
little later, sometimes almost immediately.
Once the lockup has happened, I can log in remotely, and have tried to
see what's going on. For example, I can run xev from a remote SSH
session, and look to see if X events are appearing at all from the
keyboard. They aren't.
I can also then strace the X server, and see whether it's seeing
activity from the keyboard, and it is. So the events are being
discarded somewhere between the X server receiving them and the GNOME
session receiving them.
One suspicion I have is whether this is a security feature - if the
time is changing on the machine (say, because of NTP, or VMWare's
synchronise VM clock with host option) I wonder whether some
protection mechanism against replay attacks is kicking in?
Tim
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
Reply to: