Bug 105189 - can't change sensor resolution to 800 cpi with Logitech Dual Optical mouse
Summary: can't change sensor resolution to 800 cpi with Logitech Dual Optical mouse
Status: RESOLVED WORKSFORME
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: kcmmouse (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Marie Loise Nolden
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-06 15:56 UTC by Alexander van Loon
Modified: 2005-07-06 21:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander van Loon 2005-05-06 15:56:02 UTC
Version:            (using KDE 3.4.0, Debian Package 4:3.4.0-0ubuntu3 (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-8ubuntu2)
OS:                Linux (i686) release 2.6.10-5-386

I did a fresh install of the Kubuntu Linux distribution - http://www.kubuntu.org/ - version 5.04. I use a Logitech Dual Optical mouse, which is capable of a resolution of 800 cpi. Unfortunately it doesn't work, I took a screenshot: http://www.xs4all.nl/~vanlonen/kde_logitech.jpg

"You have a Logitech Mouse connected, and libusb was found at compile time, but it was not possible to access this mouse. This is probably caused by a permission problem - you should consult the manual on how to fix this."

Let me clarify, the mouse does work, but it's resolution can't be changed to 800 cpi.

If I wanted to use my Dual Optical on Linux at 800 cpi I always had to use the program logitech_applet. It's really cool that KDE should be able to do this for me as well, so I hope this will be fixed soon. Or is this a Kubuntu specific bug, and should I post this in their bugzilla?
Comment 1 Alexander van Loon 2005-07-06 21:53:58 UTC
Recently I checked this again and this time I could set my Dual Optical to 800 cpi. I'm sure it works, because when I set it to 800 cpi I immediatly noticed the increased sensitivity. I'm not sure what the solution was, maybe it could have been fixed because I've upgraded some packages/installed KDE 3.4.1 in the meanwhile.

Because it works for me now, I marked this bug as RESOLVED.