DebuggingKeyboardDetection

Differences between revisions 1 and 15 (spanning 14 versions)
Revision 1 as of 2007-08-09 14:57:10
Size: 5046
Editor: 86-39-13-141
Comment:
Revision 15 as of 2011-08-28 01:18:22
Size: 5846
Editor: p5496C329
Comment: According to Bug #835503 changed name of package to file a bug against
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
||<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;">'''Contents'''[[BR]][[TableOfContents]]|| ||'''This page is potentially out of date as of Intrepid due to input-hotplug'''. Please remove this message if you update the page.||


<<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>>||
Line 16: Line 20:
Keyboard related bugs should initially be filed against '''xserver-xorg-input-keyboard'''.
If the bug turns out to be a kernel bug or a bug in another package, bug triagers will assign the bug additionally to that package and mark the xserver-xorg-input-keyboard task as invalid.
Keyboard related bugs should initially be filed against '''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.
Line 19: Line 23:
[[Anchor(generalinfo)]] <<Anchor(generalinfo)>>
Line 24: Line 28:
 1. How is your keyboard connected to your PC: DIN, PS/2, USB, USB wireless, ...  1. What brand and model is your keyboard.<<BR>>How is your keyboard connected to your PC: DIN, PS/2, USB, USB wireless, ...
Line 29: Line 33:
$ cat /proc/version_signature > ~/version $ cat /proc/version_signature > ~/version_signature
Line 31: Line 35:
 1. Attach {{{~/lsusb-v}}}, {{{~/uname-a}}}, {{{~/version}}} and {{{~/lspci-vvnn}}} to the bug report as seperate attachments.  1. Attach {{{~/lsusb-v}}}, {{{~/uname-a}}}, {{{~/version_signature}}} and {{{~/lspci-vvnn}}} to the bug report as separate attachments.
Line 35: Line 39:
 1. Provide the [#generalinfo general information].
 1. If you have a PS/2 keyboard make sure it was connected before booting Ubuntu.[[BR]]For debugging you will need 2 computers in the same network. The second machine can be a Windows machine, in that case you need to install putty.exe from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
 1. If you have a USB keyboard unplug it an plug it in again to see if it starts working again.
 1. Enter the following commands in a terminal/console: {{{
 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 it an 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/console: {{{
Line 40: Line 44:
 1. Attach {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in seperate attachments.  1. Attach {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments.
Line 42: Line 46:
== In case your mouse stops working after a while == == In case your USB keyboard stops working after a while ==
Line 44: Line 48:
 1. Provide the [#generalinfo general information].
 1. Direct after GNOME, KDE or Xfce login open a terminal and enter the following commands: {{{
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: {{{
Line 48: Line 55:
 2. Wait until your mouse stops working. If you have a USB mouse unplug it an plug it in again to see if your mouse starts working again.
 3. Open a Virtual Terminal by pressing Ctrl-Alt-F1.
 4. Enter the following commands: {{{
 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: {{{
Line 56: Line 63:
 5. Attach {{{dmesg_boot}}}, {{{dmesg_diff}}}, {{{Xorg.0.log}}} and {{{Xorg.0.log_diff}}} to the bug report in separate attachments.  1. Attach {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}} to the bug report in separate attachments.
Line 58: Line 65:
== In case some mouse buttons/scrollwheel don't work (as expected) == == In case some keys of your keyboard don't work (as expected) ==
Line 60: Line 67:
 1. Provide the [#generalinfo general information].
 1. Open a terminal and enter the following commands: {{{
$ xmodmap -pp > ~/xmodmap-pp
$ xev | grep -i button }}} Put the mouse cursor into the rectangle and push your mouse buttons. Mention in the bug report which button number is reported, e.g. left = 1, scrollwheel up = 4, horizontal scrollwheel left = 6, thumb button = 8, pinkie button = 9, ...
 1. Attach your {{{/var/log/Xorg.0.log}}} and {{{~/xmodmap-pp}}} to the bug report in seperate attachments.
 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 {{{~/xkb}}} and {{{~/gconf}}} to the bug report in separate attachments.
Line 73: Line 80:
##|| [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/9068 #9068] || Serial mouse isn't autodetected || If you want your serial mouse to be autodetected in future versions of Ubuntu, please help by following the steps described here: https://lists.ubuntu.com/archives/ubuntu-devel/2006-February/015020.html and attach the requested information to [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/9068 bug #9068]. || ##|| [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/9068 #9068] || Back and Forward keys don't work || If you want your serial mouse to be autodetected in future versions of Ubuntu, please help by following the steps described here: https://lists.ubuntu.com/archives/ubuntu-devel/2006-February/015020.html and attach the requested information to [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/9068 bug #9068]. ||
Line 83: Line 90:
= Also see =

 * DebuggingProcedures
Line 88: Line 91:
CategoryBugSquad CategoryBugSquad CategoryDebugging

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

Debugging Central

This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.

Introduction

If you have a laptop and the hotkeys don't work please follow the steps described here: LaptopTestingTeam/HotkeyResearch.

Problems with keyboard detection typically fall into one off these categories:

  1. Your keyboard doesn't work at all.
  2. Your USB keyboard stops working after a while.
  3. Some keys of your keyboard don't work (as expected).

How to file a bug report

Keyboard related bugs should initially be filed against 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.

General information

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

  1. What brand and model is your keyboard.
    How is your keyboard connected to your PC: DIN, PS/2, USB, USB wireless, ...

  2. For a USB keyboard enter the following command on a terminal/console:

    $ lsusb -v > ~/lsusb-v 
  3. Open a terminal/console and enter the following commands (minimal information as described in KernelTeamBugPolicies):

    $ uname -a > ~/uname-a
    $ cat /proc/version_signature > ~/version_signature
    $ sudo lspci -vvnn > ~/lspci-vvnn 
  4. Attach ~/lsusb-v, ~/uname-a, ~/version_signature and ~/lspci-vvnn to the bug report as separate attachments.

In case your keyboard doesn't work at all

  1. Provide the general information.

  2. 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.
  3. If you have a USB keyboard unplug it an 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.
  4. Enter the following command in a terminal/console:

    $ dmesg > ~/dmesg 
  5. Attach ~/dmesg and your /var/log/Xorg.0.log to the bug report in separate attachments.

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.
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 general information.

  2. 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.
  3. 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 
  4. 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.
  5. 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.
  6. 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 
  7. Attach ~/dmesg_boot, ~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff to the bug report in separate attachments.

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

  1. Provide the general information.

  2. Open a terminal/console and enter the following commands:

    $ xprop -root | grep XKB > ~/xkb
    $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd > ~/gconf 
  3. Attach ~/xkb and ~/gconf to the bug report in separate attachments.


CategoryBugSquad CategoryDebugging

DebuggingKeyboardDetection (last edited 2012-10-21 03:56:52 by penalvch)