> May just be a coincidence. I'm seeing this on my wife's machine after
> an update to Gnome-2.24.x from 2.22.x. No changes in disk drives here.
>
> If you're not against starting from a new desktop then try making a
> new user and seeing if that new user has the same problem. If it
> doesn't then try erasing (or moving) all the .gnome directories and
> possibly you'll be able to clean it up that way.
+1. Same thing here, updated to 2.24 and the settings daemon dies, then X. I
tried startx as root after rm -fr /root/.gno* and the settings daemon dies but
X lives (used root because I don't want to kill my user setup unless its really
required.. Prob should have just created a new user for that...meh)
/usr/libexec/gnome-settings-daemon --debug prints nothing
strace /usr/libexec/gnome-settings-daemon looks ok until
access("/usr/bin/bug-buddy", X_OK) = 0
getuid32() = 0
stat64("/usr/bin/bug-buddy", {st_mode=S_IFREG|0755, st_size=63932, ...}) = 0
stat64("/usr/bin/bug-buddy", {st_mode=S_IFREG|0755, st_size=63932, ...}) = 0
mmap2(NULL, 1052672, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7316000
rt_sigaction(SIGSEGV, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGSEGV, {0xb7f7b590, [], 0}, NULL, 8) = 0
rt_sigaction(SIGABRT, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGABRT, {0xb7f7b590, [], 0}, NULL, 8) = 0
rt_sigaction(SIGTRAP, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGTRAP, {0xb7f7b590, [], 0}, NULL, 8) = 0
rt_sigaction(SIGFPE, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGFPE, {0xb7f7b590, [], 0}, NULL, 8) = 0
rt_sigaction(SIGBUS, NULL, {SIG_DFL, [], 0}, 8) = 0
rt_sigaction(SIGBUS, {0xb7f7b590, [], 0}, NULL, 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0xb7594708) = 15813
exit_group(0) = ?
Any ideas? Already done a revdep-rebuild.
