Hey. It finally happened. The keyboard failed. Remembered to do the list of post-relogin debug commands.

Specifically:

Please create the following files immediately after you've logged in:
dmesg > ~/dmesg_boot
cp /var/log/Xorg.0.log ~/Xorg.0.log
Try to replug the keyboard or access a terminal at your computer using VPN, SSH or similar.
Now create the following files:
dmesg > ~/dmesg
diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff
cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp
diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff

Regards,
Matt `da Wolf
=============
ARE YOU READY FOR SOME FOOTBALL??!!
GO REDSKINS!!!
ADOPT A WOLF!
WOLVES! LOVE THEM!
SAVE THE WOLVES!
VISIT WOLF PARK!
BUSH. WHAT AN IDIOT!
MINE THE BORDERS!
NOT DEMOCRAT OR REPUBLICAN. POLITICALLY INDEPENDENT!
RON PAUL FOR 2008!

Alex Magaz wrote:

Yesterday the keyboard stopped working on my Fedora 8, but this time,
there was a window giving me a hint. It was a window from Gnome telling
me slow keys had been activated. (yes, although I use KDE, sometimes
Gnome settings seems to get loaded and messes up with KDE.) Slow keys
get activated after holding down Shift for 8 seconds, then you have to
hold each key for 500ms (default) to it take effect. For some reason on
my Kubuntu setting I didn't have any notification enabled (neither a
message nor a speaker beep), so then it appeared like keyboard not
responding. Well, I'm really only guessing, because after doing a lot of
tests with Gnome and KDE accessibility settings in both installations, I
think I'm getting a bit confused :-)

Matt, could you check if in your accessibility settings "Activation
gestures" (translation) are enabled and notifications disabled? Also, if
your keyboard fails again, could you try whether disabling accessibility
resolves the problem or not?