On Friday, 10 February 2023 07:46:36 CET Borden wrote: > which may be more productive. What would be even more productive is the following: - log in remotely before doing another test and open a screen/tmux session (or open several distinct remote logins) and start: - htop - tail -f ~/.xsession-errors - journalctl --user -b -f - any other program which may be useful IYO Then start okular from Konsole, but give it a lower priority with `nice` (and `ionice`). Possibly useful to `tee` the Konsole output to a file too. If it behaves so bad again, you should be able to kill okular (f.e.). And then file a bug report with a sample PDF as Alex suggested and provide any info you obtained which may help to solve this issue. You didn't specify which Debian and Okular version you had this issue with. In case of Testing or Sid, the "/topic" from #debian-next comes to mind: "testing → bookworm | you may need to debug sometimes | ..."
Attachment:
signature.asc
Description: This is a digitally signed message part.