You are not logged in.
I'm starting up in init 5 but when I switch to a virtual console I need to push every key twice after login. E. g. for updatedb I need to do something like this "uuppddaatteeddbb" [plus pushing ENTER twice]. What the heck is going wrong here? It looks like after a while it returns to normal behaviour, but anyway, that's annoying. Any ideas on this?
Thanks, Susu
Album reviews (in german): http://schallwelle.filzo.de
Offline
I also get this but only after coming out of hibernate. I haven't tried figuring out what was happening because it only lasts a short time.
Offline
I recently had that same problem in a fresh install of Debian Sid. The problem only occurred after starting X. I didn't figure it out either, however I strongly believe xf86-video-intel is to blame. I used the same xorg.conf that I use with Arch, the only difference is that I use the i810 with Arch, and I tried "intel" with Debian.
Do you use the intel driver? If so, can you see if booting to run level 3 stops this weird behavior?
Good luck,
peart.
Offline
I have seen this with the i810 and vesa driver...
Offline
I have a nvidia card (GeForce 6600 GT) with nvidia 100.14.19-3. I use kdemod with compiz-fusion, if it matters. I tried what's happening when booting to runlevel 3, but it's all the same and happened on every vc. After entering a few commands the keyboard behaviour returns to normal.
Album reviews (in german): http://schallwelle.filzo.de
Offline
Sorry to resurrect an old thread, but.. has anyone figured this out?!? I've had this since November-ish as well and it is driving me *nuts*.
The problem is pretty much exactly as the OP describes: keyboard is unresponsive after logging in on a virtual console. Keystrokes are randomly dropped so that you have to type some keys twice. This happens on every VC. Sometimes the problem disappears after typing a few commands, sometimes it does not. Stopping xorg does not affect the problem.
What is quite interesting is that I never seem to get dropped keys when typing my password. Could this be a framebuffer related issue?
Offline