Bug#311252: Sarge: gconfd-2 isn't stopped when users logout
Justin B Rye
Justin B Rye <firstname.lastname@example.org>, email@example.com
Wed Jul 13 11:52:32 UTC 2005
Josselin Mouette wrote:
> Le lundi 11 juillet 2005 à 16:53 +0100, Justin B Rye a écrit :
>> It was also often possible to get this sort of effect by invoking
>> various other minor apps such as gthumb or ggv; sometimes gconfd-2
>> would just exit automatically, sometimes it would require a
>> "gconftool-2 --shutdown", and sometimes it would ignore even that.
>> I spent a while looking for repeatable recipes, but never found any
>> pattern to it other than that firefox tended to cause trouble.
> If firefox spawns gconf processes, I tend to say this is a bug in
> firefox to begin with, as firefox doesn't use gconf.
Yes, fair enough! I'll start looking into the possibility of a
"reportbug mozilla-firefox" then. Unless you want to - I'm not
exactly an expert on when gconfd is or isn't appropriate, since I've
never really understood its function in the first place.
Meanwhile, though, it's also possible to get other apps to leave
behind ghostly gconfd processes. For instance, if I simply run
ssh the-host-with-the-gnome-install ghex2 # (then close it tidily)
...I find next time I log in on that machine that there's still a
gconfd-2 process running. 100% repeatable, and if I follow this up
with ggv, I get two ghosts. I have yet to find a way of getting
three, but getting one is trivial.
Anything I can usefully do to debug this?
Ankh kak! (Ancient Egyptian blessing)
More information about the Pkg-gnome-maintainers