I have run into the same problem with a linked /tmp directory, and this
work-around worked for me.
I have /tmp linked because of an SSD+HD configuration, which isn't all
that uncommon. This really shouldn't break out-of-the-box like this. At
the very least, these work-around instructions should
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evince (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032812
Title:
** Attachment added: evince-crash.txt
https://bugs.launchpad.net/bugs/1032812/+attachment/3247012/+files/evince-crash.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032812
Title:
evince
This looks to be a result of the AppArmor profile:
Aug 3 12:22:50 cpbl-thinkpad kernel: [ 3642.457504] type=1400
audit(1344010970.542:28): apparmor=DENIED operation=mknod parent=1
profile=/usr/bin/evince name=/altos/tmp/gtkprint_ppd_RWE5HW pid=4689
comm=evince requested_mask=c denied_mask=c
Thanks! for your detective work.
TMPDIR is still /tmp, but
ls -la /tmp
lrwxrwxrwx 1 root root 10 Aug 2 16:07 tmp - /altos/tmp/
Yes, your solution works. Thank you!!
So, is the crashing experience a bug? Maybe I leave that for you to
decide.
--
You received this bug notification
