When launching the epiphany web browser from Suse Linux Enterprise Desktop 10
Menu (SLAB), the Ubuntu Side Panel (USP) or when chosing 'Execute epiphany' from
the choices on deskbar-applet that come up when searching 'epiphany' on Ubuntu
6.06, the following error occurs:
'Startup failed because of the following error:
Failed to connect to socket /tmp/dbus-RXk6a6qq6u: Connection refused'
Running dbus-launch epiphany starts the program, but if the browser is already
open at the time the new instance seems to think it has crashed (offering to
recover the already open session) so it is not an acceptable work around.
On the same system, epiphany launches fine from the Gnome Menu, terminal, or
from panel launchers. Since the error occurs through different methods of
launching, it seems the problem is with d-bus.
The problem is unlikely to be with dbus. It's probably that due to how some of
these apps (slab, usp, etc.) were started up, they don't have the right
DBUS_SESSION_BUS_ADDRESS inherited from their parent process. Exactly how this
is intended to work varies a bit by distribution (and can also be affected if
you used dbus-launch manually or something like that).
You can look at the environment of your apps with something like
"ps ewwwww" and everything in your login session should have the same
DBUS_SESSION_BUS_ADDRESS. If anything has a different (or missing) address,
that is your problem.
Is this still reproducible in any current distributions?
(In reply to comment #2)
> Is this still reproducible in any current distributions?
3 years later, I'm going to assume "no".