Same, still seeing it with exact symptoms and resolution (albeit archaic
and untrustworthy, not to mention an eyebrow raiser to an employer as
stated above).
Ubuntu 13.04 (64-bit)
Microsoft Wireless Mobile Mouse 3500 (x3 different ones do the same thing.
Purple, Black & Red in case you care)
AMD
This bug is still there in 11.11, can someone reopen this issue, or do we have
to file a new copy?
4+ years in existence, and just not getting any attention...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-mouse in Ubuntu.
h
Come on people, this is the symptom using M$ Wireless mouse 1000 as well
even in natty...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-mouse in Ubuntu.
https://bugs.launchpad.net/bugs/670578
Title:
Explorer Mouse v1.0 mod
Since the hardware is no longer available for doing troubleshooting
with, we'll have to close the bug for now. However please feel free to
reopen if you or anyone else has the same HW and can reproduce this
issue using the latest development version of Ubuntu and is willing to
do some troubleshoot
"Hi, have you had a chance to test if this bug is still present in
natty?"
Unfortunetly no, the mouse was destroyed by my children shortly after
making this report.
It's a shame too, I loved that mouse.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscri
Hey 16777216,
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
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to r
Here is the receiver :
Bus 002 Device 004: ID 045e:071d Microsoft Corp.
Microsoft 6000 Series.
Fine once I've unplugged and plugged it back in.
This has been happening for a while actually - but I rarely reboot my
machine, so I've not been that fussed. Be nice if it was solved though!
Let me kn
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13 04:29:19
PDT 2010
GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: amd64
DistroRelease: Ubuntu 10.10
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (2
Not a very desirable fix, however. Try building systems for people and
telling them that they "just have to unplug and replug" their usb
receiver ever time they want to use their PC. Looking back, this has
been an issue since at least 7.04
--
Explorer Mouse v1.0 model:1362 has hyper sensitive scr
Unplugging the receiver then plugging it back in does fix the issue
until reboot.
--
Explorer Mouse v1.0 model:1362 has hyper sensitive scroll wheel.
https://bugs.launchpad.net/bugs/670578
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg
** Tags added: maverick
--
Explorer Mouse v1.0 model:1362 has hyper sensitive scroll wheel.
https://bugs.launchpad.net/bugs/670578
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-mouse in ubuntu.
_
p...@alpha-linux:~$ apport-collect 670578
Traceback (most recent call last):
File "/usr/share/apport/apport-kde", line 27, in
from PyKDE4.kdecore import (ki18n, KAboutData, KCmdLineArgs,
RuntimeError: the sip module implements API v8.0 but the PyKDE4.kdecore module
requires API v7.1
p...@al
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command, as it will automatically gather
debugging information, in a terminal:
apport-collect 670578
When reporting bugs in the future please use apport by using 'ubuntu-bug' and
the
13 matches
Mail list logo
