From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:188.8.131.52) Gecko/2008070208 Firefox/3.0.1
Description of problem:
In X, if I hold down the left shift key for more than 10 seconds I can no longer enter any keyboard input.
I have tried running setxkbmap from a menu with the mouse, and I have tried restarting my window manager, but neither affects the keyboard fuction.
Logging out to the login screen, the keyboard resumes function.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start X
2. Hold down shift key for 10 seconds
I also observe random freezing of the keyboard (I haven't found a recipe how to
certainly reproduce this, so I haven't filed it yet), but following your steps
doesn't reproduce this for me.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 313043 [details]
xorg configuration file
Created attachment 313045 [details]
xorg log /var/log/Xorg.0.log
It may be that you're activating SlowKeys (after 8 seconds). This sometimes
looks like the keyboard is unresponsive because you have to hold down each key
one second or so to actually make it generate an event.
Please open a terminal, hold shift until it happens, then keep pressing some
letter. Do the characters appear after a timeout?
If so - System, Hardware, Keyboard Preferences, Accessibility, untick "Allow to
turn accessibility features on and off from the keyboard".
Yes, that seems to be what is affecting me. Thanks.
This seems to be toggle (luckily, HUH! ;)
I have restarted my desktop twice today because of this.
Even this is not a bug (but a feature) the users should be better
informed this may happen (and harder to set this feature on, I have
2 Fedora 10 machines which both suffer for this feature)
Well, next time I briefly start GNOME desktop to do this change.