Evince does not start in LTSP environments

[Markus Kienast]

Binary package hint: evince

As simple as that. Evince does not start in LTSP environments.

When I start it from the console, I get this:
elias@xserver:/data/home/elias$ evince '/home/elias/Desktop/claim/s560p.pdf'
(evince:20545): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported

Cannot parse arguments: Anzeige kann nicht geöffnet werden:

"Anzeige kann nicht geöffnet werden:" translates to "Display can not be opened".

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: evince 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic-pae 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic-pae i686
Architecture: i386
Date: Sun May 2 18:16:17 2010
ProcEnviron:
 LANGUAGE=de_AT:de
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SourcePackage: evince

[Jukka Kommeri (jkommeri-iki)]

Was there a solution for this problem? I just installed a LTSP environment on Lucid and have the same problem.

[sordna (sordna)]

I'm getting a similar error in my non-LTSP lucid xubuntu but the following thread provided a solution:
http://ubuntuforums.org/showthread.php?t=1312025

Copying the relevant bit for you to try:

From: zoro98020 Re: evince issues after upgrade to 9.10 karmic koala
OK, seems to be something to do with AppArmor.

In /etc/apparmor.d I have among other things:
disable/
-rw-r--r-- 1 root root 2052 2009-11-11 01:03 usr.bin.evince
-rw-r--r-- 1 root root 4866 2009-10-28 08:50 usr.bin.firefox-3.5

In dir disable I find:
lrwxrwxrwx 1 root root 35 2009-10-31 10:36 usr.bin.firefox-3.5 -> /etc/apparmor.d/usr.bin.firefox-3.5

I added evince to disable
lrwxrwxrwx 1 root root 30 2009-11-27 09:37 usr.bin.evince -> /etc/apparmor.d/usr.bin.evince

restart AppArmor:
/etc/init.d/apparmor restart

Does it solve the problem in the LTSP environment? It did in my xubuntu desktop.

[FP (fabrice-pardo)]

A workaround is to give your non-standard home path (/data/home) to apparmor config
 sudo dpkg-reconfigure apparmor

[Samuel Leathers (saml)]

After studying apparmor, I would say this really isn't a bug but a feature. The only bug would be adding documentation for how to use apparmor with non-standard home directories:

create a file /etc/apparmor.d/tunables/home.d/custom

with the contents:

@{HOMEDIRS}+=<YOUR_HOME_DIR_PREFIX>

note: custom could be any name, because by default, it sources all files in that directory

for example, I have a little more complex environment, where I have a base /astro that's an auto-mount from ldap, and then users type/username, so for my tunable file I use the following line:

@{HOMEDIRS}+=/astro/*/

Where a users home directory would be for example /astro/staff/abc123

Sam