Lately my USB wireless mouse (Logitech NX80) started to misbehave and I noticed that HAL and X report it is using WheelEmulation although I neither need (two wheels present) nor have it set. In my lay thinking I'm connecting these two. Reproducable: * since it started, always, but it produces the bug at rather random intervals Steps of reproduction: 1) have mouse set up in a .fdi file 2) plug it in 3) move it around or scroll the VWheel Results: * when mouse is moved, it won't move the cursor for a few seconds * when the VWheel is scrolled, it won't scroll for a few seconds * (other) buttons and the HWheel work normally though Expected results: * both the movement and the VWheel should work properly again
Created attachment 20537 [details] 'lshal' output when mouse is plugged in
Created attachment 20538 [details] 'hal-device' output when the mouse is plugged in
Created attachment 20539 [details] Xorg.0.log after the mouse is plugged in
EmulateWheel is always off by default. Although it initialises the default settings (that's what you can see in the log) it doesn't actually turn it on, so the line is superfluous. If you run evtest on the device, does the wheel work normally? Did it work normally before, and if so, which version of evdev broke it?
This is highly odd. Today (after a reboot) I cannot reproduce the error anymore. Although Xorg.0.log still shows EmulateWheel as in the already posted log file. Nevertheless I'm attaching the 'evtest' output of the (currently) working mouse.
Created attachment 20575 [details] 'evtest' output of the relevant mouse
> --- Comment #5 from Matija Šuklje <matija.suklje@rutka.net> 2008-11-25 07:23:17 PST --- > This is highly odd. Today (after a reboot) I cannot reproduce the error > anymore. Although Xorg.0.log still shows EmulateWheel as in the already posted > log file. the line in the log file you're referring to (I assume it's (**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200) is just the default settings for the wheel emulation. Unless you turn it on _in addition to these settings_ it doesn't take into effect. Anyway, if it works for you now it might have just been some configuration issue. Please continue to monitor the behaviour and if the bug doesn't occur again in say - 4-7 days - please close this bug as INVALID or WORKSFORME.
Will do.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.