SUMMARY Opening PDF in Okular freezes Plasma completely STEPS TO REPRODUCE 1. Start Plasma in Wayland session 2. Open a PDF file by double-clicking it in Dolphin OBSERVED RESULT Plasma freezes completely (Switching to TTY1 and rebooting still works) EXPECTED RESULT Okular should start normally SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.10-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Happy to provide more info. Don't know what would be needed though. :)
Hmm... > 1. Start Plasma in Wayland session > > Graphics Platform: X11 These can't both be true. :) Are you actually in a Wayland session? How are you starting it? How do you know it's a Wayland session?
(In reply to Nate Graham from comment #1) > Hmm... > > > 1. Start Plasma in Wayland session > > > > Graphics Platform: X11 > These can't both be true. :) Are you actually in a Wayland session? How are > you starting it? How do you know it's a Wayland session? Ahaha, sorry for tthe confusion. That was just copied from the system info widget while I was back to using the X session. Of course the bug itself occurs in a Wayland session which I know for sure because I chose it in SDDM. ^^
Cool, in that case can you please get a wayland-debug log for Okular by running the following in a terminal? WAYLAND_DEBUG=1 okular path_to_the_file.pdf > ~/Desktop/okular.log The UI will still freeze, but hopefully the file will be created anyway, and then you can attach it after you recover from the freeze using your preferred method. Also, when you say Plasma freezes, is it really only Plasma? Or is it everything, including apps? If global keyboard shortcuts and already-open windows aren's responsive, then it's everything, not just Plasma.
Today's openSUSE Tumbleweed snapshot (20230215) seems to have fixed the issue. I can open PDFs just fine and the system remains usable. Let's consider this a system-specific hiccup and that it has already been fixed. Will report back with some logs if it ever happens again. :)
*** This bug has been marked as a duplicate of bug 465225 ***