Comment 7 for bug 277623

Hm, no actually I was wrong, it's not crashing--it's just using, according to top, 20% cpu and 22% memory (on a laptop with 4g installed), and (I assume) failing to respond to anyone, since the various properties dialogs take a long time to come up, then eventually give the "unable to start settings manager gnome-settings-daemon" error when they do.

This happens after a gnome-settings-daemon has been running an hour or two, without the need for any suspend/resume.

Apologies, this is probably the wrong bug to be commenting on at this point!