#583068 Please fall back to X properties when DBUS_SESSION_BUS_ADDRESS is invalid

Package:
libdbus-1-3
Source:
dbus
Description:
simple interprocess messaging system (library)
Submitter:
Vincent Lefevre
Date:
2010-05-25 07:24:18 UTC
Severity:
normal
#583068#5
Date:
2010-05-24 01:12:27 UTC
From:
To:
When I start applications using GConf (such as gthumb and liferea)
from a "screen" window, I get many GConf errors:

** (gthumb:24754): WARNING **: GConf error:
  Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-ENas4H9v2w: Connection refused)

** (gthumb:24754): WARNING **: GConf error:
  Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-ENas4H9v2w: Connection refused)

** (gthumb:24754): WARNING **: GConf error:
  Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-ENas4H9v2w: Connection refused)

and so on. I don't know whether the culprit is gconf2 or dbus...

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.
#583068#10
Date:
2010-05-24 02:29:45 UTC
From:
To:
Also note that after a ssh, I don't get any error even though there
isn't a DBUS_SESSION_BUS_ADDRESS environment variable.

I think that the behavior under screen shouldn't differ from the
behavior under ssh.
#583068#15
Date:
2010-05-24 19:23:26 UTC
From:
To:
Le lundi 24 mai 2010 à 03:12 +0200, Vincent Lefevre a écrit :

The error message is bogus. In most cases this is a D-Bus error.

Huh? Of course it is not global, it is specific to your session.

Actually, just passing $DISPLAY should be enough.

Cheers,
#583068#20
Date:
2010-05-24 23:36:09 UTC
From:
To:
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.

$DISPLAY has the correct value, but I get the dbus errors.
#583068#25
Date:
2010-05-25 06:00:52 UTC
From:
To:
Le mardi 25 mai 2010 à 01:36 +0200, Vincent Lefevre a écrit :

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

Cheers,
#583068#30
Date:
2010-05-25 07:06:03 UTC
From:
To:
OK, so I think that if it is detected that the environment variable
is no longer valid, then $DISPLAY should be used instead, without
these annoying error messages (both in the terminal and as dialog
boxes).
#583068#35
Date:
2010-05-25 07:23:22 UTC
From:
To:
clone 582839 -1
retitle 582389 GConf error messages when D-Bus is unreachable are confusing
retitle -1 Please fall back to X properties when DBUS_SESSION_BUS_ADDRESS is invalid
reassign -1 libdbus-1-3
thanks

Le mardi 25 mai 2010 à 09:06 +0200, Vincent Lefevre a écrit :

This may indeed be done in libdbus. I don’t know how complicated that
would be.

Cheers,