In my case it is reproducible. On my system the bug is always there. As I understand it, xset m allows one to adjust the acceleration and threshold; whereas sensitivity should be the base ratio of mouse pointer dpi to mouse movement. Can the sensitivity be adjusted with xset? Could this be a driver issue?
In my case it is reproducible. On my system the bug is always there. As I understand it, xset m allows one to adjust the acceleration and threshold; whereas sensitivity should be the base ratio of mouse pointer dpi to mouse movement. Can the sensitivity be adjusted with xset? Could this be a driver issue?