<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Some mouse DPI data" href="https://bugs.freedesktop.org/show_bug.cgi?id=87037#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Some mouse DPI data" href="https://bugs.freedesktop.org/show_bug.cgi?id=87037">bug 87037</a> from <a class="email" href="mailto:zbyszek@in.waw.pl" title="Zbigniew Jedrzejewski-Szmek <zbyszek@in.waw.pl>"> Zbigniew Jedrzejewski-Szmek</a> <pre>> mouse:unknown bus type:v0002p0006:name:ImExPS/2 Logitech Wheel Mouse: > MOUSE_DPI=400@250 Actually we can support this without any ambiguity: mouse:*:*:name:ImExPS/2 Logitech Wheel Mouse: MOUSE_DPI=400@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@166 The receiver is too generic. Here I have mouse:usb:v046dpc52b:name:Logitech Unifying Device. Wireless PID: MOUSE_DPI=1000@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] <a href="https://julien.danjou.info/blog/2012/logitech-unifying-upower">https://julien.danjou.info/blog/2012/logitech-unifying-upower</a> [2] <a href="http://cgit.freedesktop.org/upower/commit/?id=95184593504bca5240ecd296db98954decd2c5a5">http://cgit.freedesktop.org/upower/commit/?id=95184593504bca5240ecd296db98954decd2c5a5</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>