L> Nope, it should start with the user session. That's a very likely L> culprit for the whole problem. I should have thought of that question L> before.
OK, but please note how I run transmission, above in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497978#15 L> So I should probably file an upstream bug to either add a fallback to a L> more desktop-environment-agnostic way of running a browser or at least L> warn the user that since gconf is not running it's can't locate the L> right browser to run, making it at least fail with some sign of life L> instead of just doing nothing. I hate/fear all that gnome stuff, and hope transmission just can be one process group... L> simply try starting gconfd manually and check L> transmission again. If it works, my latest assumption is right. $ dlocate gconfd libgconf2-4: /usr/lib/libgconf2-4/gconfd-2 $ man gconfd No manual entry for gconfd $ apropos gconfd $ /usr/lib/libgconf2-4/gconfd-2 --help $ /usr/lib/libgconf2-4/gconfd-2 I don't think it does much, and $ less /usr/share/doc/gconf2*/* is too foggy for me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
