On Fri, Nov 02, 2007 at 03:25:06PM +0100, Josselin Mouette wrote: > environment, not the opposite. > > > > And it would be a good idea to also do the former. > > > > The former is a bad workaround for programs that use dbus (and especially > > dbus > > activation) in the wrong way. > > How do you think this should be done? > > BTW, it would be nice if you could discuss this with the upstream > developers, because currently they have no plans on doing otherwise.
Basically the only environment variables you can expect when you've been started by dbus is DBUS_* and the various early set environment variables (LANG, PATH, etc).. When you've been started by a session daemon for an X session, you can expect DISPLAY to be set correctly too.. For everything else you will need some other way to recover them. In seahorse's case, it should implement some D-Bus api to recover the socket paths that you'd normally get from the GPG_AGENT_INFO and SSH_AUTH_SOCK environment variables. Sjoerd -- Death is nature's way of telling you to slow down. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
