https://bugs.kde.org/show_bug.cgi?id=416233
tomtom...@gmail.com changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=416233
--- Comment #6 from Albert Astals Cid ---
Oh i just realized you're using kind of an old okular version i think we may
have already fixed this. Could you try the flatpak version of okular?
https://flathub.org/apps/details/org.kde.okular
--
You are
https://bugs.kde.org/show_bug.cgi?id=416233
--- Comment #5 from tomtom...@gmail.com ---
Created attachment 125168
--> https://bugs.kde.org/attachment.cgi?id=125168=edit
valgrind output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416233
--- Comment #4 from Albert Astals Cid ---
Thanks :)
Can you please also run
valgrind okular
and attach the output it creates when doing the thing that crashes (may not
crash while run under valgrind) (be prepared for it to be very slow)
--
You are
https://bugs.kde.org/show_bug.cgi?id=416233
--- Comment #3 from tomtom...@gmail.com ---
Created attachment 125136
--> https://bugs.kde.org/attachment.cgi?id=125136=edit
backtrace when text markup annotation is used
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416233
--- Comment #2 from tomtom...@gmail.com ---
Created attachment 125135
--> https://bugs.kde.org/attachment.cgi?id=125135=edit
backtrace when typewriter annotation is used
Oh I wasn't aware of -dbgsym stuff. Here are full backtraces with different
https://bugs.kde.org/show_bug.cgi?id=416233
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org
Resolution|---
