Bug 443932 - Startup blocks on stat()ing files on unaccessible servers
Startup blocks on stat()ing files on unaccessible servers
Product: Fedora
Classification: Fedora
Component: evince (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Kristian Høgsberg
Fedora Extras Quality Assurance
Depends On:
Blocks: 735966
  Show dependency treegraph
Reported: 2008-04-24 04:04 EDT by Pawel Salek
Modified: 2011-09-06 06:25 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 735966 (view as bug list)
Last Closed: 2009-07-14 11:55:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pawel Salek 2008-04-24 04:04:59 EDT
Description of problem:
Evince apparently keeps a list of recently open files and stat()s them on
startup. This becomes a problem if one of these files resides on a server that
is unavailable any more. This blocks the startup, the evince window never appears.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Open a file on a automounted NFS file system (evince /net/tmp-server/s.pdf)
2. Close evince. Disconnect tmp-server
3. Try opening a file on a local filesystem (evince /tmp/s.pdf) - the window
will never appear.
Actual results:
evince will hang with following strace:
stat("/home/pawsa/cv.pdf", {st_mode=S_IFREG|0664, st_size=92689, ...}) = 0
stat("/net/tmp-server/home/aa.pdf", ^C <unfinished ...>

(the last stat never finishes and needs to be interrupted).

Expected results:
Evince should just show the requested file!

Additional info:
This is a showstopper unless somebody tells me how to clean up the list of
recently accessed files. There is apparently no command line flag to disable
these stat() calls.
Comment 1 Bug Zapper 2008-05-14 06:03:32 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 2 Bug Zapper 2009-06-09 20:24:00 EDT
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Bug Zapper 2009-07-14 11:55:43 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.