Public bug reported:

Binary package hint: evince

I'm running Ubuntu 8.10 with Evince 2.24.1-0ubuntu1.  I also have autofs
setup to automount filesystems from both my home and my work.

If I open a PDF from a filesystem at home, for example
/mnt/caseserver/home/mlcase/InterestPaid.pdf, an entry for this file
gets created in .recently-used.xbel gets created to log this recently
opened file.

Now suppose I go to work and attempt to open Evince.  It traverses
.recently-used.xbel and apparently attempts to probe each PDF that is
named in that file.  The home filesystem is not available, and evince
fails to start.

>From an strace:
open("/home/mlcase/.recently-used.xbel", O_RDONLY|O_LARGEFILE) = 17
...
stat64("/tmp/kuehlmann01transformationbased.pdf", {st_mode=S_IFREG|0400, 
st_size=170785, ...}) = 0
stat64("/mnt/caseserver/home/mlcase/InterestPaid.pdf",

The stat64 call never comes back, even after waiting for up to 1 hour.
I can work around this by removing .recently-used.xbel, but this issue
really needs to be fixed.  Why do the recent PDF files be stat'd?  If
it's really necessary, this operation should at least be done under a
timeout.

A quick search on Google turns up the related Evince bugs 243250 and
210313, but the bugs never seem to have been resolved.

** Affects: evince (Ubuntu)
     Importance: Undecided
         Status: New

-- 
evince fails to start with strange .recently-used.xbel entries
https://bugs.launchpad.net/bugs/319274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to