shortcut keys=stuck left mouse button, microsoft desktop 5000

Bug #669467 reported by Pedro Palmeiro
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xserver-xorg-input-evdev (Ubuntu)
Expired
High
Unassigned

Bug Description

Ubuntu 10.10 (64bit) with Microsoft Wireless Comfort Desktop 5000 (keyboard+mouse): when any of the shortcut keys are pressed (Volume Up, Mute, etc) the left mouse button becomes stuck on. Only disconnection of the USB receiver returns it to normal.
Does not happen on 10.04, Windows or with other (wired...) keyboards I tested.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-23.36-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.12 Fri Oct 8 11:17:08 PDT 2010
 GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: amd64
Date: Mon Nov 1 14:07:49 2010
DkmsStatus:
 nvidia-current, 260.19.12, 2.6.35-22-generic, x86_64: installed
 nvidia-current, 260.19.12, 2.6.35-23-generic, x86_64: installed
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: System manufacturer P5E
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=2bf1db29-0ab5-444c-a87e-0764caeec348 ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 02/19/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5E
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/19/2009:svnSystemmanufacturer:pnP5E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5E
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-23-generic

Revision history for this message
Pedro Palmeiro (pedromgpalmeiro) wrote :
Revision history for this message
stovalo (geert-vanloo) wrote :

Same problem with my keyboard (Medion, chicony KR 0420) wireless keyboard and mouse with usb receiver. When I touch one of the special key's like volume, next or previous page, volume wheel, the left mouse button stops working. This even happens at startup on de login screen. Same behaviour when I start Maverick x64 from a live CD or DVD. No problem with a live CD of 10.04.
When I do it on my desktop and then move my mouse, a bleu selection frame, like for selecting multiple items on the desktop, appears, whithout pressing any mouse button. This frame disappears on pressing the esc button, but the left mouse klik stops working. Unplugging the usb-receiver and plugging it back in solves the problem, untill I touch one of these keys again. On startup, I also get the "unable to enumerate usb on port 2" failure, but this doesn't prevent further normal startup.

Revision history for this message
Book 'em Dano (heymrdjd) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. When you experience the problem can you attach the kern.log and sys.log located in /var/log/. Please include the information requested at https://wiki.ubuntu.com/DebuggingMouseDetection and https://wiki.ubuntu.com/DebuggingKeyboardDetection as separate attachments.

Changed in ubuntu:
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Pedro Palmeiro (pedromgpalmeiro) wrote : Re: [Bug 669467] Re: shortcut keys=stuck left mouse button, microsoft desktop 5000
Download full text (3.3 KiB)

Sorry for the delay, I switched machines and had to reinstall.
I followed the debugging procedures for the mouse and keyboard.
May I call your attention to the xev_log_with_comments file, it shows that a
mouse event is indeed received when the bug occurs.

On 12 November 2010 13:29, Book 'em Dano <email address hidden> wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. When you experience the problem can you attach the
> kern.log and sys.log located in /var/log/. Please include the
> information requested at https://wiki.ubuntu.com/DebuggingMouseDetection
> and https://wiki.ubuntu.com/DebuggingKeyboardDetection as separate
> attachments.
>
> ** Changed in: ubuntu
> Importance: Undecided => High
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> --
> shortcut keys=stuck left mouse button, microsoft desktop 5000
> https://bugs.launchpad.net/bugs/669467
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: Incomplete
>
> Bug description:
> Ubuntu 10.10 (64bit) with Microsoft Wireless Comfort Desktop 5000
> (keyboard+mouse): when any of the shortcut keys are pressed (Volume Up,
> Mute, etc) the left mouse button becomes stuck on. Only disconnection of the
> USB receiver returns it to normal.
> Does not happen on 10.04, Windows or with other (wired...) keyboards I
> tested.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: xorg 1:7.5+6ubuntu3
> ProcVersionSignature: Ubuntu 2.6.35-23.36-generic 2.6.35.7
> Uname: Linux 2.6.35-23-generic x86_64
> NonfreeKernelModules: nvidia
> .proc.driver.nvidia.version:
> NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.12 Fri Oct 8
> 11:17:08 PDT 2010
> GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
> Architecture: amd64
> Date: Mon Nov 1 14:07:49 2010
> DkmsStatus:
> nvidia-current, 260.19.12, 2.6.35-22-generic, x86_64: installed
> nvidia-current, 260.19.12, 2.6.35-23-generic, x86_64: installed
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> MachineType: System manufacturer P5E
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic
> root=UUID=2bf1db29-0ab5-444c-a87e-0764caeec348 ro quiet splash
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: xorg
> Symptom: display
> dmi.bios.date: 02/19/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 1201
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: P5E
> dmi.board.vendor: ASUSTeK Computer INC.
> dmi.board.version: Rev 1.xx
> dmi.chassis.asset.tag: Asset-1234567890
> dmi.chassis.type: 3
> dmi.chassis.vendor: Chassis Manufacture
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/19/2009:svnSystemmanufacturer:pnP5E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
> dmi.product.name: P5E
> dmi.product.version: System Version
> dmi.sys.vendor: System manufacturer
> glxinfo: Error: [Errno 2] No such file or directory
> system:
> distro: Ubuntu
> codename: maverick
> architecture: x86_64
> ...

Read more...

Revision history for this message
Book 'em Dano (heymrdjd) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to let them handle it from here. Thanks for taking the time to make Ubuntu better!

affects: ubuntu → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is almost certainly a kernel bug, but assigning to -evdev for now in case someone wants to look at it from the X side.]

affects: xorg (Ubuntu) → xserver-xorg-input-evdev (Ubuntu)
Revision history for this message
bugbot (bugbot) wrote :

Hey Pedro,

Hi, have you had a chance to test if this bug is still present in natty?

If it does (and if you're the original reporter), please boot into natty
and run the command:

  apport-collect <bug-number>

which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)

Changed in xserver-xorg-input-evdev (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Pedro Palmeiro (pedromgpalmeiro) wrote :
Download full text (3.3 KiB)

Ubuntu is currently not my everyday OS, so I cannot point when was this
resolved, but as of now, neither Maverick or Natty display the issue.
So regarding the Microsoft Comfort Desktop 5000, I believe this is fixed.

Best regards
Pedro

On 28 April 2011 05:17, bugbot <email address hidden> wrote:

> Hey Pedro,
>
>
> Hi, have you had a chance to test if this bug is still present in natty?
>
> If it does (and if you're the original reporter), please boot into natty
> and run the command:
>
> apport-collect <bug-number>
>
> which will update the bug with fresh logs and tag the bug as affecting
> natty. (It is best to run this right after reproducing the problem.)
>
>
> ** Changed in: xserver-xorg-input-evdev (Ubuntu)
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/669467
>
> Title:
> shortcut keys=stuck left mouse button, microsoft desktop 5000
>
> Status in “xserver-xorg-input-evdev” package in Ubuntu:
> Incomplete
>
> Bug description:
> Ubuntu 10.10 (64bit) with Microsoft Wireless Comfort Desktop 5000
> (keyboard+mouse): when any of the shortcut keys are pressed (Volume Up,
> Mute, etc) the left mouse button becomes stuck on. Only disconnection of the
> USB receiver returns it to normal.
> Does not happen on 10.04, Windows or with other (wired...) keyboards I
> tested.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: xorg 1:7.5+6ubuntu3
> ProcVersionSignature: Ubuntu 2.6.35-23.36-generic 2.6.35.7
> Uname: Linux 2.6.35-23-generic x86_64
> NonfreeKernelModules: nvidia
> .proc.driver.nvidia.version:
> NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.12 Fri Oct 8
> 11:17:08 PDT 2010
> GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
> Architecture: amd64
> Date: Mon Nov 1 14:07:49 2010
> DkmsStatus:
> nvidia-current, 260.19.12, 2.6.35-22-generic, x86_64: installed
> nvidia-current, 260.19.12, 2.6.35-23-generic, x86_64: installed
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007)
> MachineType: System manufacturer P5E
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic
> root=UUID=2bf1db29-0ab5-444c-a87e-0764caeec348 ro quiet splash
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: xorg
> Symptom: display
> dmi.bios.date: 02/19/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 1201
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: P5E
> dmi.board.vendor: ASUSTeK Computer INC.
> dmi.board.version: Rev 1.xx
> dmi.chassis.asset.tag: Asset-1234567890
> dmi.chassis.type: 3
> dmi.chassis.vendor: Chassis Manufacture
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr1201:bd02/19/2009:svnSystemmanufacturer:pnP5E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
> dmi.product.name: P5E
> dmi.product.version: System Version
> dmi.sys.vendor: System manufacturer
> glxinfo: Error: [Errno 2] No such file or directory
> system:
> distro: Ubuntu
> codename: ...

Read more...

Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xserver-xorg-input-evdev (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.