From noreply at ubuntu.com Tue Feb 26 07:04:00 2019 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 26 Feb 2019 07:04:00 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_anthonywong?= Message-ID: <20190226070400.22356.17107@mangaba.canonical.com> 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=42&rev2=43 * Scroll, tap, drag, press buttons, and create various other possible events on the Touchpad. Then, press CTRL+C to exit and execute: {{{ 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.o.log}}}. + * Add as separate attachments {{{~/evtest}}} and {{{~/Xorg.0.log}}} to the bug report. 1. If yes, execute at a terminal: {{{ cat /proc/bus/input/devices }}} One should see: {{{ @@ -71, +71 @@ * 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.o.log}}}. + * Add as separate attachments {{{~/evtest}}} and {{{~/Xorg.0.log}}} 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 From noreply at ubuntu.com Tue Feb 26 07:14:08 2019 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 26 Feb 2019 07:14:08 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_anthonywong?= Message-ID: <20190226071408.22306.3813@mangaba.canonical.com> 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=43&rev2=44 This is generally a case of a kernel ('''linux''') or '''xorg''' bug. - 1. Check by connecting an external mouse to see if that works. If it does, then one may be affected by the transition from [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics|xserver-xorg-input-synaptics]] to [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-libinput|libinput]]. Hence, one will want to check by uninstalling xserver-xorg-input-synaptics to see if this resolves the issue. If not, please see below: - * After reading [[DebuggingTouchpadDetection/evtest|this]] about how to enter VT and log evtest events, switch to a VT using Crtl+Alt+F2 and enter the following in your terminal: {{{ - sudo evtest /dev/input/eventX > ~/evtest}}} where the "X" in "eventX" is the event number found by typing in a terminal: {{{ - cat /proc/bus/input/devices}}} - * Scroll, tap, drag, press buttons, and create various other possible events on the Touchpad. Then, press CTRL+C to exit and execute: {{{ - 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. - 1. If yes, execute at a terminal: {{{ + 1. Execute at a terminal: {{{ cat /proc/bus/input/devices - }}} One should see: {{{ + }}} One should see a touchpad device, like: {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio2/input0 @@ -53, +45 @@ B: EV=b B: KEY=420 0 70000 0 0 0 0 0 0 0 0 B: ABS=11000003 }}} If you do not find something like this, then the bug is in the linux kernel. Please follow these steps: - 1. File the bug against the '''[[https://launchpad.net/ubuntu/+source/linux|linux]]''' package. + 1. File the bug against the '''[[https://launchpad.net/ubuntu/+source/linux|linux]]''' package by running {{{ubuntu-bug linux}}}. 1. Provide the [[#generalinfo|general information]]. 1. Enter the following commands in a terminal: {{{ - dmesg > ~/dmesg cat /proc/bus/input/devices > ~/devices }}} - 1. Attach as separate attachments to your bug report {{{~/dmesg}}}, {{{~/devices}}}, and your {{{/var/log/Xorg.0.log}}}. + 1. Attach {{{~/devices}}} as separate attachments to your bug report. + 1. If you see a touchpad device in {{{/proc/bus/input/devices}}}, check by connecting an external mouse to see if that works. If it does, then one may be affected by the transition from [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics|xserver-xorg-input-synaptics]] to [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-libinput|libinput]]. Hence, one will want to check by uninstalling xserver-xorg-input-synaptics to see if this resolves the issue. If not, please see below: + * After reading [[DebuggingTouchpadDetection/evtest|this]] about how to enter VT and log evtest events, switch to a VT using Crtl+Alt+F2 and enter the following in your terminal: {{{ + sudo evtest /dev/input/eventX > ~/evtest}}} where the "X" in "eventX" is the event number found by typing in a terminal: {{{ + cat /proc/bus/input/devices}}} + * Scroll, tap, drag, press buttons, and create various other possible events on the Touchpad. Then, press CTRL+C to exit and execute: {{{ + 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. + == In case your Touchpad stops working after a while == From noreply at ubuntu.com Tue Feb 26 08:09:18 2019 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 26 Feb 2019 08:09:18 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_anthonywong?= Message-ID: <20190226080918.26623.22391@mangaba.canonical.com> 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 }}} From noreply at ubuntu.com Tue Feb 26 08:28:36 2019 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 26 Feb 2019 08:28:36 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_anthonywong?= Message-ID: <20190226082836.26548.59352@mangaba.canonical.com> 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=45&rev2=46 Comment: Add libinput-tools = How to file the bug report = - Before filing a bug please check the list of known bugs at the end of this document. If your are unsure to which package the bug should be filed, or your problem is not listed in any of the categories, then please file your touchpad related bugs against '''xserver-xorg-input-synaptics'''. Please ensure you have xdiagnose installed, and you click Yes in order to include the necessary debugging information. If the bug turns out to be a bug related to the kernel ('''linux''') or any other package, bug triagers will assign your bug additionally to that package and mark the task related to xserver-xorg-input-synaptics, as invalid. + If your are unsure to which package the bug should be filed, or your problem is not listed in any of the categories, then please file your touchpad related bugs against '''xserver-xorg-input-libinput''' or '''xserver-xorg-input-synaptics''' (if it is installed). If the bug turns out to be a bug related to the kernel ('''linux''') or any other package, bug triagers will assign your bug additionally to that package and mark the task related to xserver-xorg-input-input/synaptics, as invalid. == General information before filing the bug == @@ -165, +165 @@ Name="ImPS/2 Generic Wheel Mouse"}}} In this case the bug must be a kernel issue. 1. Check whether xserver has detected the Touchpad correctly by executing at a terminal: {{{ xinput --list }}} You will see the same name of Touchpad as above. - 1. Check whether the synaptics module is correctly loaded in xserver or not via executing at a terminal: {{{ + 1. Check whether the libinput (or synaptics for older Ubuntu) module is correctly loaded in xserver or not via executing at a terminal: {{{ cat /var/log/Xorg.0.log | grep -i synaptics }}} 1. For problems such as scrolling area, touch area, button wrong mapping, and multitouch, try investigating with: {{{ evtest /dev/input/eventX @@ -173, +173 @@ xinput --list }}} For example: {{{ ↳ TouchPad id=6 [slave pointer (2)] }}} Then, type: {{{ xinput --list-props 6 }}} + 1. When debugging libinput, {{{libinput debug-events}}} would be helpful. The command is in the {{{libinput-tools}}} package. ---- CategoryBugSquad CategoryDebugging CategoryCleanup From noreply at ubuntu.com Tue Feb 26 08:35:16 2019 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 26 Feb 2019 08:35:16 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_anthonywong?= Message-ID: <20190226083516.26643.62714@mangaba.canonical.com> 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=46&rev2=47 Comment: more debugging tips Be sure to use the device id or name of your specific trackpad. You can list the devices on your computer using the "xinput" command. - = Some general work flow for Triagers = + = General work flow for Triagers and debugging tips = If features of Touchpad like tapping and scrolling do '''not''' work at all, the user will not see the '''Touchpad''' Tab in System -> Administration -> Mouse in the Main menu. This means that Touchpad is misdetected as PS/2 mouse. Here the following workflow must be followed. @@ -174, +174 @@ ↳ TouchPad id=6 [slave pointer (2)] }}} Then, type: {{{ xinput --list-props 6 }}} 1. When debugging libinput, {{{libinput debug-events}}} would be helpful. The command is in the {{{libinput-tools}}} package. + 1. If the Touchpad vendor is Synaptics, try loading {{{psmouse}}} kernel module with {{{synaptics_intertouch=0}}}. + 1. If the Touchpad vendor is Elantech, try loading {{{psmouse}}} kernel module with {{{elantech_smbus=0}}}. This option only exists since Cosmic (linux v4.18 kernel). ---- CategoryBugSquad CategoryDebugging CategoryCleanup