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
>  kernel:             2.6.35-23-generic
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+bug/669467/+subscribe
>