DebuggingKeyboardDetection
5864
Comment:
|
← Revision 19 as of 2012-10-21 03:56:52 ⇥
5425
1) Please see ## wiki comments. 2) Misc. minor syntax fixes. 3) RM'd stale comments. 4) RM'd stale kernel team link. 5) Add hotkey link in key don't work (as expected)
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
[[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;">'''Contents'''[[BR]][[TableOfContents]]|| |
## 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>>|| |
Line 8: | Line 13: |
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: |
Problems with keyboard detection typically fall into one of these categories: |
Line 17: | Line 20: |
## Before filing a bug please check the list of [#knownbugs known bugs] at the end of this document. | 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. |
Line 19: | Line 22: |
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 can assign the bug additionally to that package and mark the xserver-xorg-input-keyboard task as invalid. |
<<Anchor(generalinfo)>> |
Line 22: | Line 24: |
[[Anchor(generalinfo)]] | |
Line 27: | Line 28: |
1. What brand and model is your keyboard.[[BR]]How is your keyboard connected to your PC: DIN, PS/2, USB, USB wireless, ... 1. For a USB keyboard enter the following command on a terminal/console: {{{ $ lsusb -v > ~/lsusb-v }}} 1. 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 }}} 1. Attach {{{~/lsusb-v}}}, {{{~/uname-a}}}, {{{~/version_signature}}} and {{{~/lspci-vvnn}}} to the bug report as separate attachments. |
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. |
Line 38: | Line 36: |
1. Provide the [#generalinfo general information]. | 1. Provide the [[#generalinfo|general information]]. |
Line 40: | Line 38: |
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: {{{ $ dmesg > ~/dmesg }}} 1. Attach {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments. |
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}}}. |
Line 47: | Line 45: |
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]. |
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]]. |
Line 52: | Line 49: |
$ dmesg > ~/dmesg_boot $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} |
dmesg > ~/dmesg_boot cp /var/log/Xorg.0.log ~/Xorg.0.log }}} |
Line 57: | Line 54: |
$ 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 {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}} to the bug report in separate attachments. |
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}}}. |
Line 66: | Line 63: |
1. Provide the [#generalinfo general information]. | 1. Provide the [[#generalinfo|general information]]. |
Line 68: | Line 65: |
$ 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. ##[[Anchor(knownbugs)]] ##= Known bugs = ##Description of known issues, how to recognise them and stock responses/actions. ##'''Open''' ##||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' || ##|| [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]. || ##'''Closed''' ##||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' || ##|| [https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896 #8896] ##|| This bug can be identified by ... || blabla || ## = Non-bugs = ## How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses. |
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. |
This page is potentially out of date as of Intrepid due to input-hotplug. Please remove this message if you update the page. |
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Introduction
Problems with keyboard detection typically fall into one of these categories:
- Your keyboard doesn't work at all.
- Your USB keyboard stops working after a while.
- Some keys of your keyboard don't work (as expected).
How to file a bug report
Keyboard related bugs should initially be filed against xorg, as bugbot will switch it to the correct package (ex. 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:
What brand and model is your keyboard.
How is your keyboard connected to your PC: DIN, PS/2, USB, bluetooth, etc.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
Provide the general information.
- 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.
- 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.
Enter the following command in a terminal:
dmesg > ~/dmesg
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.
If the second machine runs Windows you need to install putty.exe from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html.
Provide the general information.
- 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.
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
- 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.
- 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.
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
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)
Provide the general information.
Open a terminal/console and enter the following commands:
xprop -root | grep XKB > ~/xkb gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd > ~/gconf
Attach as separate attachments to your bug report ~/xkb and ~/gconf.
Check the hotkey debugging article for any more relevant information to provide.
DebuggingKeyboardDetection (last edited 2012-10-21 03:56:52 by penalvch)