Bug 338976 - loading "hangs" if file is on unaccessible remote mounted filesystem
Summary: loading "hangs" if file is on unaccessible remote mounted filesystem
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.17.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-10 12:47 UTC by Kevin H. Hobbs
Modified: 2023-02-12 03:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin H. Hobbs 2014-09-10 12:47:45 UTC
Okular hangs while stat-ing files in the history.

Often okular refuses to load for minutes then suddenly opens documents that I've long since forgotten about.

This happens when I start okular from the terminal, the KDE or fluxbox menu, or by clicking on a link to a .pdf document in firefox. 

It does not seem to have anything to do with the particular document I want to open and happens even when I start okular from a terminal without any specific file.

I ran 'strace okular' and it looks like it hangs at the stat system call for a file in the okular history.

Right now the particular file was on a remote cifs file system.

Clearing the history (once okular eventually loads) resolved the problem for now...
Comment 1 Albert Astals Cid 2014-09-11 08:28:32 UTC
Is it stating files that are no longer accessible?
Comment 2 Kevin H. Hobbs 2014-09-11 13:16:11 UTC
The whole cifs mounted file system in /mnt seems to have become inaccessible : so this is the kernel's problem. 

The only problem for okular is that there seems to be no way to tell it to load without statting every path it's ever seen.
Comment 3 Albert Astals Cid 2014-09-12 10:34:09 UTC
Ok, this will need someone to be able to reproduce that "strange" scenario first, may take a while
Comment 4 Andrew Crouthamel 2018-11-12 02:48:46 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-21 04:44:01 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Justin Zobel 2023-01-13 01:36:36 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2023-01-28 05:09:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-02-12 03:50:50 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!