Le mercredi 13 juillet 2005 à 12:52 +0100, Justin B Rye a écrit :
> > If firefox spawns gconf processes, I tend to say this is a bug in
> > firefox to begin with, as firefox doesn't use gconf.
I was wrong here, as mozilla-firefox-gnome-support uses it. The bug is
really in gconf2.
> Yes, fair eno
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
>>
Le lundi 11 juillet 2005 à 16:53 +0100, Justin B Rye a écrit :
> Just to confirm that the original reporter isn't some freakish
> one-off. Here on my domestic network, where most X logins on the
> public server are my flatmates logging into fvwm2, running firefox
> and then logging out, I routinel
Package: gconf2
Followup-For: Bug #311252
Just to confirm that the original reporter isn't some freakish
one-off. Here on my domestic network, where most X logins on the
public server are my flatmates logging into fvwm2, running firefox
and then logging out, I routinely found ghostly gconfd-2 pro
Package: gconf2
Version: 2.8.1-6
System: Debian Sarge
Kernel: 2.4.27-2-386
Description of the problem:
if users start gconfd-2(that belongs to gconf2) it doesn't stop when
the users logout; this could be a problem on systems with a lot of
users because the administrator has to kill by hand all th
5 matches
Mail list logo
