Red Hat Bugzilla – Bug 455679
gnome-mouse-properties lose mouse sensetivity
Last modified: 2009-04-25 11:42:23 EDT
after setting mouse sensetivity do suspend/resume your machine. as result you
lose sensetivity for pointer (control value in dialog preserve).
same for connect/disconnect mouse - you lose settings for device (dialog value
I did not change other mouse settings, but I can confirm that gnome-mouse-properties looses the "Left-handed/Right-handed Mouse Orientation" setting ; the value is erroneously preserved in the dialogue window.
Experiencing this since F10-Beta, on at least two workstations, and up to current control-center-220.127.116.11-9.fc10.x86_64 .
This not only happens after a suspend/resume or hibernate cycle (100% reproducable), but also seems to occur after an undefined amount of time in screensaver.
This leads to several reassignments a day, which IMO seriously detriments user experience (after all, the mouse is a primary input device) ; I hope this gets fixed before F10-Final (with thousands of left-handed users).
Unfortunately those won't get fixed for F10-Final. We've missed that boat. Could potentially get fixed in an F10 update though.
My guess is this is fallout from evdev. When we suspend-resume the input device gets forgotten and readded as a hotplug event and so the pointer mapping is getting reset.
We probably need to be listening for new devices in gnome-settings-daemon and update the pointer mapping on them, and I bet we aren't.
Just a guess.
I suspect gnome-settings-daemon hasn't survived suspend/resume cycle -- I have same problem. Looks like duplicate of bug 466599 to me.
WRT comment #3 : I also experience this problem after an extended (say 30 minutes) screensaver period : i.e. no suspend/resume cycle involved.
is gnome-settings-daemon still running?
My guess is this is related to using evdev for devices. on resume the existing devices probably generate new hotplug events and get seen as new devices so their old settings aren't applied. There's another bug about that somewhere, I believe, that we should probably dupe this one to.
When resuming from a hibernation, /usr/libexec/gnome-settings-daemon is still running.
I also wonder whether/how gnome-screensaver can invoke the loss of settings. How could one trace or monitor at what time a certain settings gets accessed ? Would putting an strace on gnome-settings-daemon be reasonable ? If yes, with what parameters ?
i don't think that would work. I think the issue is gnome-settings-daemon isn't listening for "new device" events and applying the existing settings to new devices. I think it would be hard to decode what's going on from an strace.
Not sure why gnome-screensaver alone causes the problem.
Killing and restarting gnome-settings-daemon restores mouse settings.
the issue from comment #1 (mouse left/right hand settings lost after suspend/resume) seems to be resolved.
confirm. connect/disconnect mouse also work
bug 474758 is the one. It's fixed in gnome-settings-daemon-2.24.1-7.fc10
*** This bug has been marked as a duplicate of bug 474758 ***