<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Logitech M500 behavior" href="https://bugs.freedesktop.org/show_bug.cgi?id=96225#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - Logitech M500 behavior" href="https://bugs.freedesktop.org/show_bug.cgi?id=96225">bug 96225</a> from <a class="email" href="mailto:jeremy9856@gmail.com" title="Paviluf <jeremy9856@gmail.com>"> Paviluf</a> <pre>(In reply to Peter Hutterer from <a href="show_bug.cgi?id=96225#c12">comment #12</a>) > ok, the systemd patch got merged so the DPI information should be correct > now. Thank you very much but I think we maybe have made a mistake. The 1200dpi value I got was due to an "old" hwdb. I just saw that the mouse dpi was recently set to 1000dpi@125 <a href="https://github.com/whot/systemd/commit/62f6eed416e3f4a473e3f2b39dc5457284e34f58">https://github.com/whot/systemd/commit/62f6eed416e3f4a473e3f2b39dc5457284e34f58</a> and after some more research I always found that the M500 is a 1000dpi mouse and advertised as such : <a href="https://secure.logitech.com/en-us/product/corded-mouse-m500">https://secure.logitech.com/en-us/product/corded-mouse-m500</a> <a href="http://www.logitech.fr/fr-fr/product/corded-mouse-m500">http://www.logitech.fr/fr-fr/product/corded-mouse-m500</a> ... There is only one and only one link that say it's a 1100dpi mouse and furthermore it says max: 1100dpi : <a href="http://support.logitech.com/en_us/product/corded-mouse-m500">http://support.logitech.com/en_us/product/corded-mouse-m500</a> I also find it more pleasant to use at 1000dpi even if the pointer acceleration is not optimal for now as you said. I don't know how precise is mouse-dpi-tool but maybe we should revert back the patch ? What do you think ? By the way the title of the patch is wrong it's the M500 mouse not the MX500 ;-) > The next problem is that it's still not good enough according to <a href="show_bug.cgi?id=96225#c9">comment 9</a>, > so that's another bug about pointer acceleration not being good enough. > unfortunately I still have (at least) one big feature on my slate before I > can look at pointer acceleration, so this won't be looked at until after > libinput 1.4, sorry. At 1000dpi@125 the pointer acceleration is good enough for now, so it's not really a problem.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>