I would probably try running
strace okular | grep openat
to see all the files it's trying to read and see if any aren't managed by your package manager and move those.
But the latest reply by felixernst in the kde discuss also looks helpful.
KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
I would probably try running
strace okular | grep openat
to see all the files it's trying to read and see if any aren't managed by your package manager and move those.
But the latest reply by felixernst in the kde discuss also looks helpful.
Oooh! Now that's a new idea! Thank you!
... uh, any tips on how to filter/process the output? There's like a bazillion lines going on about breeze-dark icons etc...
Oof yeah, some programs really love to touch a lot of stuff making strace kind of annoying to use. I usually end up chaining more grep -v
pipes on the end as I find files I'm not interested in seeing e.g.
strace okular | grep openat | grep -v breeze-dark | grep -v icon
Might help to first save it to a file so you don't have to keep relaunching okular as you add more inverse greps
strace okular | tee some-file
^C
cat some-file | grep -v ...
@418teapot @dwawlyn BTW strace has some built-in filtering, e.g. strace --trace=openat instead of grepping for openat. Might make it a little easier.
on my system I also have
~/.local/share/okular
but idk if clearing it is useful
Thanks! But a few people already said that, and mv ~/.local/share/okular/ ~/.local/share/okular.bak
didn't have any effect.