Problem running evince locally and remotely via ssh

Bug #608928 reported by Samuel Leathers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: evince

I'm in a network user environment. Users are pulled from ldap and authenticated via Kerberos. Home directories live on an NFS server. I've tried with both my user as well as the user that reported the problem to me. Problem does not exist for local user accounts.

This is the error when ran locally:

yux10@whiterice:~$ evince

(evince:6591): EggSMClient-WARNING **: Failed to connect to the session
manager: None of the authentication protocols specified are supported

(evince:6591): Gtk-WARNING **: Attempting to read the recently used
resources file at `/astro/research/yux10/.recently-used.xbel', but the
parser failed: Failed to open file
'/astro/research/yux10/.recently-used.xbel': Permission denied.

** (evince:6591): WARNING **: Error creating last_settings file: Error
opening file '/astro/research/yux10/.gnome2/evince/last_settings': No
such file or directory

Segmentation fault

And this is remote. And just to mention, other X11 apps run fine, such as gedit, firefox and gv (Using firefox remotely to file this bug).

evince
X11 connection rejected because of wrong authentication.
Cannot parse arguments: Cannot open display:

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: evince 2.30.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Jul 22 16:56:02 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/tcsh
SourcePackage: evince

Revision history for this message
Samuel Leathers (saml) wrote :
Revision history for this message
Samuel Leathers (saml) wrote :

By modifying tunables/home HOMEDIRS I was able to fix the problem. I guess this can be closed now that I know what the problem is. I'll just add that file to my controlled svn repository of config files I maintain on all client machines.

Sam

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

Other bug subscribers

Remote bug watches

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