Description of problem: After unplugging and re-plugging my USB mouse, the speed settings are lost (and, I presume, reset to their default values) I use GNOME on the desktop. Version-Release number of selected component (if applicable): FC10 default How reproducible: Always Steps to Reproduce: 1. Unplug the usb mouse 2. Plug it back in 3. Actual results: Mouse speed is different from the one set before the unplugging took place Expected results: Mouse speed is the same Additional info:
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Do you have any file in /etc/hal/fdi/policy/ ? Could we get it attached as well, please? We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 325926 [details] xorg.conf
Created attachment 325929 [details] Xorg.0.log
/etc/hal/fdi/policy/ is empty. The settings return to normal after reboot (perhaps even after logout/login - haven't tried).
do you have the speed settings configured in the GNOME mouse configuration tool?
Yes, that's correct.
Ok, this is a gnome issue then. X sees a the "virtual core pointer" (i.e. the cursor) and all physical input devices as separate devices. gnome only ever sets the speed setting on the VCP, but X is smart enough to then apply the setting to all physical devices that are attached to the VCP. When you add a new device, it comes with the default settings. gnome doesn't yet listen to "new device" notifications, so it doesn't apply the setting again. This needs to be fixed in (upstream) gnome.
Created attachment 326524 [details] Listen for DeviceAdded (in addition to the DeviceEnabled it already listens for) I think this patch may fix the issue. I'm building it now, and would appreciate if someone affected would test it.
err, will be building shortly. I didn't properly apply the patch, and now cvs seems to be having a hickup so I can't fire off another build.
gnome-settings-daemon-2.24.1-6.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/gnome-settings-daemon-2.24.1-6.fc10
gnome-settings-daemon-2.24.1-7.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gnome-settings-daemon'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2008-11131
gnome-settings-daemon-2.24.1-7.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 469744 has been marked as a duplicate of this bug. ***
*** Bug 455679 has been marked as a duplicate of this bug. ***