Hello, Cristian! Cristian Ionescu-Idbohrn wrote: > On Mon, 3 Dec 2007, Cristian Ionescu-Idbohrn wrote: > >> I also noticed this in the process table: >> >> /usr/bin/dbus-launch --exit-with-session /usr/bin/seahorse-agent --execute >> sh ~/.xsession >> >> It may be that what pushes up gconf (seahorse dependencies show gconf2). >> It's not obvious to me what starts dbus-launch :( > > If I kill two more processes: > > /usr/bin/dbus-launch --exit-with-session /usr/bin/seahorse-agent --execute > sh ~/.xsession > /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session > > and restart gpodder, I get this message instead: > > ,---- > | Plugin Error > | Unable to activate plugin Media Player Keys > | > | /---\ > | | OK | > | \----/ > `---- > > and I see: > > /usr/lib/libgconf2-4/gconfd-2 20 > > up again. The whole thing is quite confusing right now.
Can you remove gconfd temporarily and see if the problem persists? If so, I suspect this might be a gconfd bug, or at least the gconfd maintainers should know why gconfd starts up when a pygtk application runs. gPodder doesn't require any Gnome-specific stuff and doesn't load any gnome/gconf-related things. It's only pure GTK/PyGTK, so I'm also puzzled as to why this happens. Thanks, Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
