Hi, Le dimanche 19 août 2007 à 20:48 +0200, Sven Arvidsson a écrit : > On Tue, 2007-05-29 at 18:13 +0200, Josselin Mouette wrote: > > Le lundi 28 mai 2007 à 12:30 +0200, Sjoerd Simons a écrit : > > > > That's what I supposed, but is there any way to have things work > > > > correctly? > > > > Further more, I see seahorse-agent is now started by dbus: > > > > /usr/bin/dbus-launch --exit-with-session /usr/bin/seahorse-agent > > > > --execute x-session-manager > > > > > > > > I guess this can help? > > > > > > Good point. If it was the other way around stuff would just work.. So > > > either > > > seahorses xsession should be later or dbus-launch's should be earlier. > > > > > > I guess moving dbus-launch from 75 to 60 and seahorse from 60 to 65 > > > would be > > > the nicest solution.. > > > > I'm not sure this is going to work, because seahorse itself is using > > dbus, so it needs to be started after dbus. > > > > It's kind of an egg-and-chicken issue. > > Hi, > > I haven't looked at this in detail, so I could be wrong, but isn't this > related to this bug recently fixed in Ubuntu? > https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/62163 > > and the upstream bug; http://bugzilla.gnome.org/show_bug.cgi?id=360475
It is indeed related, as removing 'use-session-dbus' from /etc/X11/Xsession.options does fix the issue. Cheers, Julien
