[okular] [Bug 514660] New: okular hangs for 30 seconds if previously opened files are not available (because fs is unmounted)

Tilman Keskinöz bugzilla_noreply at kde.org
Thu Jan 15 17:55:25 GMT 2026


https://bugs.kde.org/show_bug.cgi?id=514660

            Bug ID: 514660
           Summary: okular hangs for 30  seconds if previously opened
                    files are not available (because fs is unmounted)
    Classification: Applications
           Product: okular
      Version First 25.11.90
       Reported In:
          Platform: Debian unstable
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: okular-devel at kde.org
          Reporter: tilman at arved.at
  Target Milestone: ---

SUMMARY

If I am at home, I can nfs mount a directory with scanned documents from my
nas. 

fstab entry:
nas.local:/volume1/shared   /home/arved/nas/shared    nfs   
rw,relatime,noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=1min
  0   0

If I am not at home, of course this volume is not mounted, as nas.local does
not resolve.

Unfortunately upon opening okular it tries to open the recently opened
documents. It fails to open the documents that don't exists and retries before
finally giving up and showing the UI.

STEPS TO REPRODUCE
1.  NFS mount directory and open foo.pdf from this directory.
2. Shut down your laptop move somewhere else where the nfs mount does not
resolve.
3. type "okular bar.pdf " in a local directory.

OBSERVED RESULT

No GUI is shown for 30 seconds.

strace output reveals what okular is trying to do:

access("/home/arved/nas/shared/scanner/E79221D1X112433_01012019_000313_000282.pdf",
F_OK) = -1 ENODEV (No such device)
access("/home/arved/nas/shared/scanner/E79221D1X112433_01052019_213837_000293.pdf",
F_OK) = -1 ENODEV (No such device)

It tries to open every file twice. At least this could be speed up by trying
only once, because it is unlikely the file becomes available a few seconds
after first attempt fails.

EXPECTED RESULT

okular opens instantly. If the old files really need to be read, this could be
done in a background thread after the UI is shown to the user. Or a dialog
could be shown "Trying to open last opened files" etc. 

The end-user should need to run strace to figure out why okular takes such a
long time to start.

SOFTWARE/OS VERSIONS

Operating System: Debian GNU/Linux 13
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.20.0
Qt Version: 6.9.2
Kernel Version: 6.17.13+deb14-amd64 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics
Memory: 32 GiB of RAM (29.1 GiB usable)
Graphics Processor: AMD Radeon Graphics


ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Okular-devel mailing list