https://bugs.kde.org/show_bug.cgi?id=415261
Albert Astals Cid changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=415261
--- Comment #8 from Alex Dănilă ---
You are right. Sorry for all this noise, I used to remember to check this stuff
before reporting bugs (I often use KDE from Unstable to get newer versions of
software).
$ dpkg -s okular | grep '^Version:'
Version:
https://bugs.kde.org/show_bug.cgi?id=415261
--- Comment #7 from Tobias Deiminger ---
The new backtrace again shows a seemingly impossible call stack
(DjVuGenerator::generateDocumentInfo should not be reachable via
TOC::notifySetup).
This kind of error could happen if okular loads a binary
https://bugs.kde.org/show_bug.cgi?id=415261
--- Comment #6 from Alex Dănilă ---
Created attachment 124901
--> https://bugs.kde.org/attachment.cgi?id=124901=edit
valgrind output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415261
Alex Dănilă changed:
What|Removed |Added
CC||nuor...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=415261
--- Comment #4 from Albert Astals Cid ---
also maybe run okular throught valgrind and tell us the trace it gives you
valgrind okular filepath.djvu
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415261
--- Comment #3 from Tobias Deiminger ---
Can't reproduce a crash when opening your file. Tried with latest okular, and
with packaged okular on Debian bullseye.
Can you try opening the file in djview4 instead of okular? If a crash happens
there too, it
https://bugs.kde.org/show_bug.cgi?id=415261
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=415261
Tobias Deiminger changed:
What|Removed |Added
CC||haxti...@posteo.de
--- Comment #1 from
