[Bug 85521] Re: gconfd-2 doesn't stop for previous user logged into GNOME

[Ivailo Stoyanov]

I'm glad that I still haven't rebooted since then to get rid of the
annoying situation and the observed anomaly still eats almost all of my
CPU cycles, so here is the requested info.

First of all, I am unable to do successfully "(gdb) attach <PID>" as
described in the wiki -- I get "no permission". Is it safe to run the
gdb commands from the wiki as root?

"sudo strace -p 5771" was more straightforward and resulted in a
continuously scrolling (> 3000 lines until a CTRL+C) message:

--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
sigreturn()                             = ? (mask now [])
Process 5771 detached

HTH!

-- 
gconfd-2 doesn't stop for previous user logged into GNOME
https://launchpad.net/bugs/85521