gnome-settings-daemon leaks memory

Please attach /var/log/Xorg.0.log and the output of lshal.

same problem with gnome-settings-daemon_2.24.0-0ubuntu3.1

same for me (at the moment 1.3 GB).

Please try gnome-settings-daemon ~wgrant3 (NOT ~wgrant2) from https://launchpad.net/~wgrant/+archive. It should be there in about 6 minutes.

gnome-settings-daemon ~wgrant3 works fine!
Thanks!

Argh, so some of my code is at fault :(

At least it narrows it down.

OK, try ~wgrant4.

~wgrant4 does not work, still present the leak of memory, and the layout of keyboard is changed from Italian to US

I can confirm this problem. It's been taking down my work machine when it hits a bit over a gig. It appears to be exacerbated when I run System > Preferences > Mouse, giving me the error that gnome-settings-daemon cannot be started.

I'd like lshal output, /var/log/Xorg.0.log and ~/.xsession-errors from everybody with this problem, please.

yes,on my ubuntu 810 HP laptop, version 2.24.0-0ubuntu3.1 of gnome-setting-daemon is problematic(100% cpu usage,fail to start with gnome-sappereance-properties.and some shortcuts of keyboard didn't work any more),when i down grade it to 2.24.0-0ubuntu3.0, it's working well.....
hope it fixed in next update..

On my laptop gnome-settings-daemon had 100% cpu usage. My /var/log/Xorg.0.log was a 118Mb file containing:

(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
 No such file or directory.
Error opening /dev/input/wacom : No such file or directory

I've removed wacom references from /etc/X11/xorg.conf and now cpu usage is back to normal.

This workaround worked for me too.

Please post the relevant section of your xorg.conf, so I can reproduce and fix it.

I can confirm. Since I have a wacom tablet myself and the same lines in my xorg.conf caused the memory leak and high CPU usage of gnome-settings-daemon (20%) and Xorg (60%).

Thanks, I've been able to reproduce and hopefully fix the problem. ~wgrant6 should be in my PPA in about 10 minutes; please try that.

Having seen the same 510MB log file as the others with the same lines, I updated to ~wgrant6, which appears to have fixed the issue.

My x.org.conf had a lot of pointer device sections (I'm not sure where they came from); after I removed them, I no longer saw the problem. good-xorg.conf (after the change) and bad-xorg.conf (before the change) attached.

I also tried going back to the "bad" xorg.conf, installing ~wgrant6, and rebooting, and found that also served to fix the memory leak/cpu usage problem.

An intrepid-proposed debdiff is coming shortly. Here's a description of the problem and its fix:

==
The problem was broken X input devices defined in xorg.conf - in particular, tablet entries without the corresponding serial device actually existing.

The touchpad setting code in gnome-settings-daemon looked for DevicePresence notifications, and checked if they were of the DeviceAdded type. If they were, it proceeded to reconfigure all input devices. Setting the touchpad properties requires opening each device, and checking if it has the right properties. When X sees a device open request for the non-existent tablet, it revives the X device to look for the serial device, which triggers another DeviceAdded event. g-s-d notices this. Rinse. Repeat. Chaos ensues.

The fix for this was to dig through the xserver code and work out that I should be looking for DeviceEnabled rather than DeviceAdded. The device for the missing tablet never finishes initialising, so never fires a DeviceEnabled.

Since the Synaptics touchpad driver now reports itself as being of type XI_TOUCHPAD rather than XI_MOUSE, I also added further checks to not even bother opening a device if it isn't an XI_TOUCHPAD.

Accepted into intrepid-proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

2.24.0-0ubuntu3.2 copied to jaunty.

:)

Updated from intrepid-proposed... all ok. Thanks ^^.

working fine for me, too.

Copied to intrepid-updates.