Ubuntu
evince package

GUI launch fails strangely when done from a secondary login, ssh -X

Bug #671565 reported by Christopher Barrington-Leigh
66
This bug affects 17 people
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Binary package hint: evince

Here's what I did:

ssh -X seconduser@localhost
evince myfile.pdf

ie, after logging in as a different user, I launch evince. It does not fully die (ie it stays in the foreground / I don't get my prompt back), but no window comes up and I get:

Failed to get bus connection: Command line `dbus-launch --autolaunch=<some hexy code here> --binary-syntax --close-stderr' exited with non-zero exit status 1: EOF in dbus-launch reading address from bus daemon\n

(where I've removed some hexy code in case it's private).

Other applications like xterm and acroread launch just fine.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: evince 2.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-23.36-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
Architecture: amd64
Date: Fri Nov 5 11:29:26 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.utf8
 SHELL=/bin/bash
SourcePackage: evince

Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :
Pedro Villavicencio (pedro)
Changed in evince (Ubuntu):
importance: Undecided → Low
Revision history for this message
Florian Rathgeber (florian-rathgeber) wrote :

I think this is related to bug #694627

I see the same error running evince on a remote host (on natty). Starting evince via dbus-launch is a workaround.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evince (Ubuntu):
status: New → Confirmed
Revision history for this message
PieroCampa (piero-campa) wrote :

Same here.
I just do:

    > xhost +SI:localuser:<secondUser>
    localuser:<secondUser> being added to access control list
    > su - <secondUser>
    > evince foo.pdf
    Failed to get bus connection: Command line `dbus-launch --autolaunch=8023f57b00b816370b52ae5c00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: EOF in dbus-launch reading address from bus daemon\n

and a Ctrl+C is needed to exit the application.
Running Ubuntu Oneiric (+LXDE) on Dell XPS 1640 laptop.

Revision history for this message
PieroCampa (piero-campa) wrote :

Furthermore, as I try to visualize the pdf residing in the home of the <secondUser> from my primary user account, it fails anyway:

    > sudo evince ~<secondUser>/foo.pdf
    No protocol specified
    No protocol specified
    No protocol specified
    No protocol specified
    Cannot parse arguments: Cannot open display:

I need to manually copy foo.pdf into my /home directory to be able to evince it.

NOTE: double-clicking directly on foo.dpf with my File Manager instead opens the file smoothly.

Revision history for this message
JfBucas (jfbucas) wrote :

If I start "okular" first, then I can run "evince xxxx.pdf" without any trouble.

Revision history for this message
Jeroen Baten (jbaten) wrote :

Same here. If I install Okular and start and stop it, after that Evince works fine. Strange.

Revision history for this message
steve cohen (steve-si9yrl01qsu4bt4tonx56g) wrote :

this bug also affects ubuntu gnome 13.04 and is solved by adding /bin/dbus-daemon Uxr, to the usr.bin.evince stanza

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.