||'''This page is potentially out of date as of Intrepid due to input-hotplug'''.  Please remove this message if you update the page.||

## 20121020 https://launchpad.net/~penalvch I don't feel comfortable removing above message as I'm not familiar enough with this statement to believe I have updated it sufficiently. Despite this, asking for the == General information == is mostly redundant. Now that we are in the Apport era, when one files a bug by it, a requirement as per https://wiki.ubuntu.com/Bugs/Responses#Missing_Apport_Information , against the xorg package, the following attachments (that requesting is redundant) are automatically attached to the bug report and then shifted to xserver-xorg-input-evdev by bugbot (ex. https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1064265 ) Otherwise, reporting against evdev only gives dependencies.txt:
## BootDmesg.txt -> gives very similar info as uname -a, and gives exactly same as cat /proc/version_signature
## Lspci.txt -> same as lspci -vvnn

<<Include(Debugging/Header)>>

||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position:  98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>||

= Introduction =

Problems with keyboard detection typically fall into one of these categories:
 1. Your keyboard doesn't work at all. 
 1. Your USB keyboard stops working after a while.
 1. Some keys of your keyboard don't work (as expected).

= How to file a bug report =

Keyboard related bugs should initially be filed against '''[[https://launchpad.net/ubuntu/+source/xorg|xorg]]''', as [[https://launchpad.net/~bugbot|bugbot]] will switch it to the correct package (ex. [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-evdev|xserver-xorg-input-evdev]]). If the bug turns out to be a kernel bug or a bug in another package, bug triagers can assign the bug additionally to that package and mark the xserver-xorg-input-evdev task as invalid.

<<Anchor(generalinfo)>>

== General information ==

For all bug categories the following general information should be provided:

 1. What brand and model is your keyboard.<<BR>>How is your keyboard connected to your PC: DIN, PS/2, USB, bluetooth, etc.
 1. For a USB keyboard, enter the following command in a terminal: {{{
lsusb -v > ~/lsusb-v
}}}
  * Attach as separate attachment to your bug report ~/lsusb-v.

== In case your keyboard doesn't work at all ==

 1. Provide the [[#generalinfo|general information]].
 1. If you have a PS/2 keyboard make sure it was connected before booting Ubuntu. To complete the steps below you will need to connect a USB keyboard.
 1. If you have a USB keyboard, unplug and replug it to see if it starts working. If it doesn't, you should have connected a PS/2 keyboard before booting Ubuntu in addition to your USB keyboard to complete the steps below.
 1. Enter the following command in a terminal: {{{
dmesg > ~/dmesg }}}
 1. Attach as separate attachments to your bug report {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}}.

== In case your USB keyboard stops working after a while ==

For debugging this problem you either need a PS/2 keyboard or 2 computers in a network.<<BR>>If the second machine runs Windows you need to install putty.exe from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
 1. Provide the [[#generalinfo|general information]].
 1. If you don't have a PS/2 keyboard install the openssh-server package on the machine with the keyboard problem. If you have a PS/2 keyboard connect it addition to your USB keyboard before booting Ubuntu.
 1. Direct after logging in to GNOME, KDE or Xfce open a terminal and enter the following commands: {{{
dmesg > ~/dmesg_boot
cp /var/log/Xorg.0.log ~/Xorg.0.log }}}
 1. Wait until your USB keyboard stops working. Try if switching to a Virtual Terminal still works by pressing Ctrl-Alt-F1, are you able to login and enter commands? Try to unplug your USB keyboard and replug it to see if it starts working again.
 1. If replugging or the Virtual Terminal works then goto step 6. If it doesn't work you should use either the PS/2 keyboard or the second machine in the LAN to login to your machine of which the keyboard stopped working. If your second machine is Linux use the command ssh user@host, if it is Windows use putty.
 1. Type the following commands in the terminal: {{{
LANG=C
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 }}}
 1. Attach as separate attachments to your bug report {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}}.

== In case some keys of your keyboard don't work (as expected) ==

 1. Provide the [[#generalinfo|general information]].
 1. Open a terminal/console and enter the following commands: {{{
xprop -root | grep XKB > ~/xkb
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd > ~/gconf }}}
 1. Attach as separate attachments to your bug report {{{~/xkb}}} and {{{~/gconf}}}.
 1. Check the [[https://wiki.ubuntu.com/Hotkeys/Troubleshooting|hotkey]] debugging article for any more relevant information to provide.

----
CategoryBugSquad CategoryDebugging