Bug 217254 - epiphany refuses to start over a network connection
epiphany refuses to start over a network connection
Product: Fedora
Classification: Fedora
Component: epiphany (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
Depends On:
  Show dependency treegraph
Reported: 2006-11-25 19:23 EST by Michal Jaegermann
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-11-25 20:10:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Jaegermann 2006-11-25 19:23:47 EST
Description of problem:

Login to a remote such that a display is really happening on a local
machine and try to start epiphany.  This results in the following:

** (epiphany:27361): WARNING **: Unable to connect to session bus: Unable to
determine the address of the message bus (try 'man dbus-launch' and 'man
dbus-daemon' for help)

Doh!  There is no "seesion bus" as there is no session on a remote.

If that would be only WARNING that would be not so bad, but this
is followed by a display of an alert which says more or less the
same thing, plus an irrelevant in the context "advice", and dismissing
that alert terminates an attempt.

Is epiphany truly so misdesigned that it cannot run without
a "session bus" possibly with some functionality, relevant only
in a local session, missing? Luckily at least some other browsers
do not suffer from that disease and yes - there are situations
when this functionality is really needed.

Version-Release number of selected component (if applicable):
Comment 1 Christopher Aillon 2006-11-25 20:10:04 EST
epiphany --private-instance
Comment 2 Michal Jaegermann 2006-11-25 20:23:26 EST
Thanks! I did look at 'epiphany --help' and 'man epiphany' but both
these sources say:

  -p, --private-instance         Start a private instance

              Start a private instance

and that is it.  I have to confess that I would never guess that
'--private-instance' mens "do not try to connect to a session bus".
Maybe documentation could make that a tad more explicit?  This
indeed works.

Note You need to log in before you can comment on or make changes to this bug.