Bug#582839: gconf2: many GConf errors when applications are started from the "screen" utility

[Josselin Mouette]

Le mardi 25 mai 2010 à 01:36 +0200, Vincent Lefevre a écrit :
> On 2010-05-24 21:23:26 +0200, Josselin Mouette wrote:
> > Le lundi 24 mai 2010 à 03:12 +0200, Vincent Lefevre a écrit : 
> > > In the "screen" session, I have:
> > > 
> > > DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ENas4H9v2w,guid=8f34077d53a0c20686fd4419004ed7d0
> > > 
> > > in my environment, while I have:
> > > 
> > > DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-8YWMhIOvpA,guid=10a6d6d450278bf513f5ec6b009b469f
> > > 
> > > otherwise. IMHO, any method based on the environment (except DISPLAY,
> > > which doesn't change in general) is broken because the environment
> > > isn't something global.
> > 
> > Huh? Of course it is not global, it is specific to your session.
> 
> What session? If this is the dbus session, it can change (e.g.
> because the X server has restarted), but the environment variable
> won't magically be updated. If needed, the data should be stored
> in a file depending on $DISPLAY.

The environment variable has precedence, but it is also stored in the
root window properties (which only needs $DISPLAY, thus).

Cheers,
-- 
 .''`.      Josselin Mouette
: :' :
`. `'   “A handshake with whitnesses is the same
  `-     as a signed contact.”  -- Jörg Schilling