DebuggingMouseDetection

Differences between revisions 3 and 15 (spanning 12 versions)
⇤ ← Revision 3 as of 2007-08-09 13:03:07 →
Size: 3794
Editor: 86-39-13-141
Comment:
← Revision 15 as of 2010-09-24 10:14:17 → ⇥
Size: 5111
Editor: cpe-125
Comment:
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]]|| <<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 5: Line 6:
This procedure is only meant for external mouse detection problem, if you have a laptop and your touchpad is not detected please follow the steps described here: DebuggingTouchpadDetection. If you have a laptop and your touchpad is not detected please follow the steps described here: DebuggingTouchpadDetection.
Line 8: Line 9:
 1. Your mouse is not detected at all.  1. Your mouse doesn't work at all.
Line 10: Line 11:
 1. Some mouse buttons don't work (as expected).

## 1. Hardware specific bugs - The developers may not have access to the hardware that triggers this bug. Certain log files and command outputs can help
## 1. Package selection - Help to find the right package (may be specific to category -- a bug filed as ubiquity may in fact be a casper d-i bug, an xorg bug may be an xorg-driver bug, etc.)		  1. Some mouse buttons or scrollwheels don't work (as expected).
Line 17: Line 15:
## Useful for bug-filers and as a boiler-plate advice for triagers. Before filing a bug please check the list of [[#knownbugs|known bugs]] at the end of this document.
Line 19: Line 18:
If the bug turns out to be a kernel bug, bug triagers will assign the bug additionally to linux-source-2.6.x and mark the xserver-xorg-input-mouse task as invalid. 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-mouse task as invalid.
Line 21: Line 20:
<<Anchor(generalinfo)>>
Line 25: Line 25:
 1. How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, ...[[BR]]What mechanism does your mouse use: ball mouse, optical, trackball, ...[[BR]]How many physical buttons and scrollwheels does you mouse have?  1. What brand and model is your mouse.<<BR>>How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, ...<<BR>>What mechanism does your mouse use: ball mouse, optical, trackball, ...<<BR>>How many physical buttons and scrollwheels does you mouse have?
Line 27: Line 27:
 $ lsusb -v > ~/lsusb-v.log }}}
 1. Open a terminal/console and enter the following commands: {{{
 $ uname -a > ~/uname-a.log
 $ cat /proc/version_signature > ~/version.log
 $ dmesg > ~/dmesg.log
 $ sudo lspci -vvnn > ~/lspci-vvnn.log }}}
 1. Attach {{{~/lsusb-v.log}}}, {{{~/uname-a.log}}}, {{{~/version.log}}} and {{{~/dmesg.log}}} and {{{~/lspci-vvnn.log}}} to the bug report.		 $ 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 seperate attachments.
Line 35: Line 34:
== In case your mouse is not detected at all == == In case your mouse doesn't work at all ==
Line 37: Line 36:
 1. Unplug you USB mouse and enter the following command in a terminal/console:
  {{{$ tail -f /var/log/messages | tee messages.txt}}}
 1. Now plug in your USB mouse, you should see some messages appearing.
 1. Press Ctrl-C to stop the logging and attach messages.txt to the bug report.
 1. Enter the following command in a terminal/console:
  {{{$ sudo lsusb > lsusb.txt}}}
 1. Attach lsusb-v.txt to the bug report.		  1. Provide the [[#generalinfo|general information]].
 1. If you have a PS/2 mouse make sure it was connected before booting Ubuntu, if you have a USB mouse unplug it and replug it to see if it starts working.
 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 seperate attachments.
Line 45: Line 42:
== In case your mouse stops working after a while ==

 1. Test if your mouse works in a second computer. Several issues are related to your specific Bios configuration, try to disable ACPI.
 1. Provide the [[#generalinfo|general information]].
 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 mouse stops working. If you have a USB mouse unplug it an replug it to see if it starts working again.
 1. Open a Virtual Terminal by pressing Ctrl-Alt-F1.
 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 {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}} to the bug report in separate attachments.

== In case some mouse buttons or scrollwheels don't work (as expected) ==

 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.

<<Anchor(knownbugs)>>
Line 51: Line 74:
##|| [https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896 #8896] || This bug can be identified by ... || Mark as duplicate of 8896 with the comment "Thank you for reporting. This issue has already been reported as bug #8896. Marking as Duplicate." || || [[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]]. ||
Line 53: Line 76:
'''Closed'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
##|| [https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896 #8896] || This bug can be identified by ... || Mark as duplicate of 8896 with the comment "Thank you for reporting. This issue has already been reported as bug #8896. Marking as Duplicate." ||		 ##'''Closed'''
##||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
##|| [https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896 #8896] ##|| This bug can be identified by ... || blabla ||
Line 61: Line 84:
= Also see =

 * DebuggingProcedures
Line 66: Line 85:
CategoryBugSquad CategoryBugSquad CategoryDebugging

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 your touchpad is not detected please follow the steps described here: DebuggingTouchpadDetection.

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

  1. Your mouse doesn't work at all.
  2. Your mouse stops working after a while.
  3. Some mouse buttons or scrollwheels don't work (as expected).

How to file a bug report

Before filing a bug please check the list of known bugs at the end of this document.

Mouse related bugs should initially be filed against xserver-xorg-input-mouse. 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-mouse task as invalid.

General information

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

  1. What brand and model is your mouse.
    How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, ...
    What mechanism does your mouse use: ball mouse, optical, trackball, ...
    How many physical buttons and scrollwheels does you mouse have?

  2. For a USB mouse 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 seperate attachments.

In case your mouse doesn't work at all

  1. Provide the general information.

  2. If you have a PS/2 mouse make sure it was connected before booting Ubuntu, if you have a USB mouse unplug it and replug it to see if it starts working.

  3. Enter the following command in a terminal/console: 

    $ dmesg > ~/dmesg

  4. Attach ~/dmesg and your /var/log/Xorg.0.log to the bug report in seperate attachments.

In case your mouse stops working after a while

  1. Test if your mouse works in a second computer. Several issues are related to your specific Bios configuration, try to disable ACPI.

  2. Provide the general information.

  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 mouse stops working. If you have a USB mouse unplug it an replug it to see if it starts working again.
  5. Open a Virtual Terminal by pressing Ctrl-Alt-F1.

  6. 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

  7. Attach ~/dmesg_boot, ~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff to the bug report in separate attachments.

In case some mouse buttons or scrollwheels don't work (as expected)

  1. Provide the general information.

  2. 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, ...

  3. Attach your /var/log/Xorg.0.log and ~/xmodmap-pp to the bug report in seperate attachments.

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Bug#

Description

Action

#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 bug #9068.

CategoryBugSquad CategoryDebugging