[Ubuntu Wiki] Update of "DebuggingTouchpadDetection" by anthonywong

[Ubuntu Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "DebuggingTouchpadDetection" page has been changed by anthonywong:
http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=44&rev2=45

Comment:
debug runtime suspend

    * Press Crtl+Alt+F7 to switch back to X.
    * Add as separate attachments {{{~/evtest}}} and {{{~/Xorg.0.log}}} to the bug report.
  
- 
  == In case your Touchpad stops working after a while ==
  
- This is generally a case of a kernel ('''linux''') or '''xorg''' bug. In this case, '''in the description field, specify the steps to make the touchpad stop working''' (e.g. hit a key, drag an icon, etc.). Now connect an external mouse to see if it works or not.
+ This is generally a case of a kernel ('''linux''') or '''xorg''' bug. In this case, '''in the description field, specify the steps to make the touchpad stop working''' (e.g. hit a key, drag an icon, after X seconds of inactivity, etc.).
  
-  1. If no, then you should file the bug against '''HAL''' and follow these steps:
+  1. If your Touchpad stops working after it has been left unused for awhile, it may be runtime suspended. Disable runtime suspend of the Touchpad device and check if the issue persists.
+     1. Look for your Touchpad device in {{{/proc/bus/input/devices}}}.
+     1. The line starts with {{{S:}}} is the path of the Touchpad device, the full path will be something like {{{/sys/devices/platform/i8042/serio1/input/input5/power/control}}}.
+     1. Disable runtime suspend by running {{{echo on | sudo tee /sys/devices/platform/i8042/serio1/input/input5/power/control}}} (replace the path with the one for your Touchpad device.
+     1. If the problem disappears, report as such to your bug report. If the problem persists, read on.
-   * After reading [[DebuggingTouchpadDetection/evtest|this]] on how to enter VT and log evtest events, switch to a VT using Crtl+Alt+F2 and enter following in your terminal: {{{
+  1. After reading [[DebuggingTouchpadDetection/evtest|this]] on how to enter VT and log evtest events, switch to a VT using Crtl+Alt+F2 and enter following in your terminal: {{{
  sudo evtest /dev/input/eventX > ~/evtest }}}
+   * Perform the action that makes the Touchpad fails. Then, press CTRL+C to exit. 
-   * Scroll, tap, drag, press buttons, and create various other possible events on the Touchpad. Then, press CTRL+C to exit. {{{
- cp /var/log/Xorg.0.log ~/Xorg.0.log }}}
    * Press Crtl+Alt+F7 to switch back to X.
-   * Add as separate attachments {{{~/evtest}}} and {{{~/Xorg.0.log}}} to the bug report.
+   * Add as separate attachments {{{~/evtest}}} to the bug report.
-  1. Execute at a terminal: {{{
- cat /proc/bus/input/devices }}} One should see something like this: {{{
- I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
- N: Name="SynPS/2 Synaptics TouchPad"
- P: Phys=isa0060/serio2/input0
- S: Sysfs=/devices/platform/i8042/serio2/input/input8
- U: Uniq=
- H: Handlers=mouse2 event8
- B: EV=b
- B: KEY=420 0 70000 0 0 0 0 0 0 0 0
- B: ABS=11000003 }}} If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in the kernel itself and you should follow these steps:
-    1. Provide the [[#generalinfo|general information]].
-    1. Directly after logging in to GNOME, KDE, or Xfce open a terminal and enter the following commands: {{{
+  1. Directly after logging in to GNOME, KDE, or Xfce open a terminal and enter the following commands: {{{
  cat /proc/bus/input/devices > ~/devices
  dmesg > ~/dmesg_boot
  cp /var/log/Xorg.0.log ~/Xorg.0.log }}}
-    1. Wait until your touchpad stops working.
+  1. Wait until your touchpad stops working.
-    1. Open a Virtual Terminal by pressing Ctrl-Alt-F1.
-    1. Enter the following commands: {{{
+  1. Enter the following commands: {{{
- 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 {{{~/devices}}}, {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}}.
+  1. Attach {{{~/devices}}}, {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}} as separate attachments to your bug report.
  
  == In case Touchpad features like scrolling, tapping, etc. do not work at all. ==
  
- Common symptom is absence of the ''''Touchpad'''' tab in System -> Preferences -> Mouse.
+ Common symptom is absence of the ''''Touchpad'''' tab/device shown in Control Center.
  
- This may be a wrong detection by '''xserver''' or the '''kernel''' itself. So, xserver-xorg-input-synaptics has nothing to do with it. Please note in the case of filing a bug against the kernel ('''linux'''), you should not mark the bug a duplicate of another. Even if you can find a closely related bug and you have a strong feeling that the bug should be duplicate. This is a policy of the Ubuntu Kernel Team and it helps them to handle bugs better. For more on this, please see [[https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue|here]].
+ Your touchpad may be wrongly recognized as a mouse. So xserver-xorg-input-synaptics has nothing to do with it. Please note in the case of filing a bug against the kernel ('''linux'''), you should not mark the bug a duplicate of another. Even if you can find a closely related bug and you have a strong feeling that the bug should be duplicate. This is a policy of the Ubuntu Kernel Team and it helps them to handle bugs better.
  
  Please execute at a terminal: {{{
  cat /proc/bus/input/devices > ~/devices }}}
+ If the output includes the name of your Touchpad (e.g. Name="SynPS/2 Synaptics TouchPad"), then the linux kernel has detected it right.
- If the output includes the name of your Touchpad (e.g. Name="SynPS/2 Synaptics TouchPad"), then the linux kernel has detected it right. In this case, please don't report the bug against the kernel, rather report it against '''HAL'''. For more information on reporting bugs against HAL, refer DebuggingHal
- ## Isn't HAL deprecated?! 20121018 https://launchpad.net/~penalvch
  In any case, attach as separate attachments to your bug report the results of the following commands: {{{
  cat /proc/bus/input/devices > ~/devices
  xinput --list > ~/xinput 
  cat /var/log/Xorg.0.log > Xorg.0.log }}}
- 
- '''IMPORTANT:''' Please do not file bug against the [[https://launchpad.net/ubuntu/+source/linux|linux]] package unless you know it should. If you are unsure, file it against xserver-xorg-input-synaptics, and somebody will change it to linux if applicable.
  
  == In case at least one of the Touchpad features work, but does not work correctly and as expected ==
  Examples of this are jumpy cursor, scrolling problems, Touchpad area is misdetected, circular scrolling, and buttons not correctly mapped. Please attach the following files as separate attachments to your bug report:
@@ -128, +113 @@

   * After reading [[DebuggingTouchpadDetection/evtest|this]] for help on how to enter VT and log evtest events, switch to a VT using Crtl+Alt+F2 and enter the following in a terminal: {{{
  sudo evtest /dev/input/eventX > ~/evtest
  }}}
-   * Add identifier, Scroll, tap, drag, press buttons, and create various other possible events on the Touchpad. Then, press CTRL+C to exit.
+   * Perform the action that does not work on the Touchpad. Then, press CTRL+C to exit.
    * Press Crtl+Alt+F7 to switch back to X.
   * After reading [[DebuggingTouchpadDetection/xev|this]] on reporting xev logs, execute the following in a terminal, and perform the relevant actions: {{{
  xev > ~/xev.log }}}