[systemd-bugs] [Bug 87037] Some mouse DPI data
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Dec 8 11:17:27 PST 2014
https://bugs.freedesktop.org/show_bug.cgi?id=87037
--- Comment #4 from Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> ---
> mouse:unknown bus type:v0002p0006:name:ImExPS/2 Logitech Wheel Mouse:
> MOUSE_DPI=400 at 250
Actually we can support this without any ambiguity:
mouse:*:*:name:ImExPS/2 Logitech Wheel Mouse:
MOUSE_DPI=400 at 250
Quite a lot of people still have those around (I have a few), and they become
annoyingly slow when set to the default 1000 DPI.
OTOH, this one is problematic:
> mouse:usb:v046dpc52b:name:Logitech Unifying Device. Wireless PID:4008:
> MOUSE_DPI=800 at 166
The receiver is too generic. Here I have
mouse:usb:v046dpc52b:name:Logitech Unifying Device. Wireless PID:
MOUSE_DPI=1000 at 125
from a M505/B605 mouse.
Would it be possible to match on the actual device that is connected to the
receiver? I see that upower has special support for LG devices [1,2]. Maybe it
could export the label of the device as an udev attribute and we could key of
that then?
[1] https://julien.danjou.info/blog/2012/logitech-unifying-upower
[2]
http://cgit.freedesktop.org/upower/commit/?id=95184593504bca5240ecd296db98954decd2c5a5
--
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141208/8632611d/attachment.html>
More information about the systemd-bugs
mailing list