Bug 217254

Summary:	epiphany refuses to start over a network connection
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal>
Component:	epiphany	Assignee:	Christopher Aillon <caillon>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-11-26 01:10:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Jaegermann 2006-11-26 00:23:47 UTC

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):
epiphany-2.16.0-5.fc6

Comment 1 Christopher Aillon 2006-11-26 01:10:04 UTC

epiphany --private-instance

Comment 2 Michal Jaegermann 2006-11-26 01:23:26 UTC

Thanks! I did look at 'epiphany --help' and 'man epiphany' but both
these sources say:

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

or
       --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.