DebuggingMouseDetection

Differences between revisions 16 and 20 (spanning 4 versions)
⇤ ← Revision 16 as of 2010-09-24 10:15:36 →
Size: 5161
Editor: cpe-125
Comment:
← Revision 20 as of 2012-10-19 04:49:12 → ⇥
Size: 5028
Editor: penalvch
Comment: Reworded to "Attach as separate attachments to your bug report..." due to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1019998 . 2) chgd terminal/console to just terminal.
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
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.		 Mouse related bugs should initially be filed via the command:
{{{ubuntu-bug xorg}}}

If the bug turns out to be a kernel bug or a bug in another package, bug triagers can re-assign the bug.
Line 26: Line 28:
 1. For a USB mouse 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 seperate attachments.		  1. For a USB mouse enter the following command on a terminal: {{{
lsusb -v > ~/lsusb-v }}}
 1. Open a terminal 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 as separate attachments to your bug report {{{~/lsusb-v}}}, {{{~/uname-a}}}, {{{~/version_signature}}} and {{{~/lspci-vvnn}}}.
Line 38: Line 40:
 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.		  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 44: Line 46:
 1. Test if your mouse works in a second computer, or test a second mouse in your computer. Several issues are related to your specific Bios/hardware configuration, try to disable ACPI.  1. Test if your mouse works in a second computer, or test a second mouse in your computer. Several issues are related to the specific hardware/Bios configuration, try to disable ACPI.
Line 47: 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 52: 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 63: Line 65:
$ 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.		 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 as separate attachments to your bug report {{{/var/log/Xorg.0.log}}} and {{{~/xmodmap-pp}}}.

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 via the command: ubuntu-bug xorg

If the bug turns out to be a kernel bug or a bug in another package, bug triagers can re-assign the bug.

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: 

    lsusb -v > ~/lsusb-v

  3. Open a terminal 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 as separate attachments to your bug report ~/lsusb-v, ~/uname-a, ~/version_signature and ~/lspci-vvnn.

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: 

    dmesg > ~/dmesg

  4. Attach as separate attachments to your bug report ~/dmesg and your /var/log/Xorg.0.log.

In case your mouse stops working after a while

  1. Test if your mouse works in a second computer, or test a second mouse in your computer. Several issues are related to the specific hardware/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 as separate attachments to your bug report ~/dmesg_boot, ~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff.

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 as separate attachments to your bug report /var/log/Xorg.0.log and ~/xmodmap-pp.

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