Slowest mouse speed still to fast for high DPI mouse

[dejangex]

Using a laser mouse (1000 DPI) , pointer speed still fast with lowest mouse speed settings

Architecture: amd64
DistroRelease: Ubuntu 9.10
Program: gnome-mouse-properties

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 4037 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfcff8000 irq 22'
   Mixer name : 'Realtek ALC1200'
   Components : 'HDA:10ec0888,104382fe,00100101'
   Controls : 40
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfe9fc000 irq 17'
   Mixer name : 'Nvidia ID d'
   Components : 'HDA:10de000d,10de0101,00100100'
   Controls : 0
   Simple ctrls : 0
Card1.Amixer.values:

DistroRelease: Ubuntu 10.04
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
LiveMediaBuild: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Regression: No
RelatedPackageVersions: linux-firmware 1.34.1
Reproducible: Yes
RfKill:

Tags: lucid needs-upstream-testing
Uname: Linux 2.6.32-24-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/04/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q
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.:bvr2002:bd03/04/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Vish (vish)]

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue, in the default Ubuntu 9.10 install, that affects many people and is quick and easy to fix. So this bug can't be addressed as part of this project.

- This is a bug and not a papercut.
For further information about papercuts criteria, please read https://wiki.ubuntu.com/PaperCut.

Don't worry though, this bug has been marked as "Invalid" only in the papercuts project.

This bug does not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers.
Kindly re-assign the bug to the package . You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Martin Meyer (elreydetodo)]

I am also affected by this problem. I just replaced a POS wheel mouse that moved nicely with a Logitech M705 laser mouse. The laser sensor naturally reports movement data a lot more often per inch of real mouse movement than the wheel mouse did. The mouse driver should have taken that into account when deciding how to translate mouse movement data into cursor movement.

FYI I have tried turning mouse sensitivity and acceleration down all the way in gnome-mouse-properties. This is not sufficient to make the mouse comfortable usable. It moves FAR too fast for my liking. I've also tried 'xset mouse 0 0' (which I know should have done the same thing) just to be sure g-m-p was doing what I thought it was. No change.

I think it might be a shortcoming in the evdev driver: is the driver even aware of the resolution of your optical mouse's sensor? If not then a bug should be filed against evdev. If it is, maybe there needs to be quirk data for my mouse model.

[Fabio Marconi (fabiomarconi)]

Hello
Is this problem present with the latest updated Karmic's or Lucid's packages?
Thanks in advance
Fabio

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[mannheim (kronheim)]

This bug is still present in Lucid (Logitech laser mouse).

[Fabio Marconi (fabiomarconi)]

Hello
can you please attach this mouse and run in a terminal
apport-collect 480786
Thanks
Fabio

[Fabio Marconi (fabiomarconi)]

Assign to linux as i think that this mouse is detected as another type.

[mannheim (kronheim)]

I can't do "apport-collect 480786" because apport-collect gives me an error message:

'You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed.
Please create a new report using "apport-bug".'

[mannheim (kronheim)]

The mouse is detected as a "Logitech USB Receiver" as far as I understand it (which is not much). I believe that several different models of mice from Logitech all share the same type of receiver. So perhaps linux does not know which Logitech mouse is being used with the Logitech receiver.

[mannheim (kronheim)]

I cannot run "apport-collect 480786" succesfully. The program apport tells me I cannot do this because the bug is closed and I am not the owner of the bug.

[Jeremy Foshee (jeremyfoshee)]

Hi dejangex,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 480746

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[dejangex (dejangex)]

I cannot run "apport-collect 480786" successfully. The program apport tells me I cannot do this because the bug is closed and I am not the owner of the bug even though I am.

This also affects the 10.04 LTS release. The mouse I'm using is http://www.newegg.com/Product/Product.aspx?Item=N82E16826104242

[Fabio Marconi (fabiomarconi)]

Please run in aterminal
apport-collect -p linux 480746
Thanks
Fabio

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[dejangex (dejangex)]

apport information

[Fabio Marconi (fabiomarconi)]

[ 3.144983] usb 6-2: configuration #1 chosen from 1 choice
[ 3.163806] usbcore: registered new interface driver hiddev
[ 3.179093] input: Logitech USB Laser Mouse as /devices/pci0000:00/0000:00:1d.0/usb6/6-2/6-2:1.0/input/input4
[ 3.179167] generic-usb 0003:046D:C061.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB Laser Mouse] on usb-0000:00:1d.0-2/input0
[ 3.179185] usbcore: registered new interface driver usbhid
[ 3.179187] usbhid: v2.6:USB HID core driver

Bus 006 Device 002: ID 046d:c061 Logitech, Inc.
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[Fabio Marconi (fabiomarconi)]

Hello dejangex
Can you please test a live session of the newest Natty to see if this bug is already fixed in the latest kernel or Xorg ?
download the image here:
http://cdimage.ubuntu.com/daily-live/current/
and create a usb key with startup disk creator.
Thanks
Fabio

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.