After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 555670 - slow startup with recently opened files on not available nfs server
slow startup with recently opened files on not available nfs server
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: general
2.22.x
Other All
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-09 13:01 UTC by fischi
Modified: 2012-06-27 04:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description fischi 2008-10-09 13:01:11 UTC 
Please describe the problem:
If you have recently opened documents on a nfs server ( I use autofs ) which is currently unavailable evince takes a long time to startup (~30s).

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?
yes.

Other information:
I started evince with strace and it waited for every file on autofs/nfs a few seconds.

I think evince should not sheck those files on startup.
Comment 1 Nickolay V. Shmyrev 2008-10-09 22:42:52 UTC 
Hm, this probably is a gio bug.
Comment 2 CJ van den Berg 2009-06-08 11:25:20 UTC 
The same thing happens if you have gtk bookmarks to locations that are not currently available.
Comment 3 José Aliste 2012-06-27 04:20:40 UTC 
This is actually fixed by commit df46a24a7d52b217182f01be995721255941128e