okular crashed with SIGSEGV in Poppler::convertAnnotColor()

[Lenar]

Binary package hint: okular

Can provide offending pdf file privately.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/okular
Package: okular 4:4.1.96-0ubuntu1
ProcCmdline: /usr/bin/okular /home/music/other/InDesign\ CS3\ for\ Dummies.pdf -icon okular -caption Okular
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdegraphics
StacktraceTop:
 Poppler::convertAnnotColor ()
 Poppler::Page::annotations ()
 ?? () from /usr/lib/kde4/okularGenerator_poppler.so
 ?? () from /usr/lib/kde4/okularGenerator_poppler.so
 ?? () from /usr/lib/kde4/okularGenerator_poppler.so
Title: okular crashed with SIGSEGV in Poppler::convertAnnotColor()
Uname: Linux 2.6.28-4-generic x86_64
UserGroups: audio cdrom dialout floppy music plugdev scard uml-net video work

[Luka Renko (lure)]

You can get problematic PDF from:
http://www.qtrac.eu/C++-GUI-Programming-with-Qt-4-1st-ed.zip

[Albert Astals Cid (aacid)]

I can't reproduce the crash and also the gdb backtrace looks damn strange, can you please run
valgring okular path_to_file
and attach the results here?

[Albert Astals Cid (aacid)]

The other possibility i can think of is that you ran out of memory, is that possible?

[Luka Renko (lure)]

I have tried it now on a clean KDE desktop (just Plasma, no apps beside some tray icons) on machine with 2 GB RAM. /proc/meminfo before test showed that I have 680 MB free memory + 800 MB occupied by cache (therefore available), which I suspect should be plenty even for 53 MB PDF.

Okular crashes almost instantly - I just get a main window for 0.1 sec (sometimes seen just as flicker), so I would say memory is not the issue here.

I would also like to point out that another Ubuntu/Jaunty (KDE 4.2 rc) user confirmed the bug in #kubuntu-devel, while two other users running Ubuntu/Intrepid (one with standard KDE 4.1.x and one with KDE 4.2.60 from SVN) reported that file opens OK for them. Therefore I suspect the difference is really in version of the poppler library (0.8.7 vs 0.10.3), which is also indicated by the stack trace.

I have also looked into poppler packages in Ubuntu, and they do not include any distro specific patches that could cause this (only patch is to fix bug 5667).

[Albert Astals Cid (aacid)]

It might be a problem in Ubuntu, i got Harald Sitter to rebuild Jaunty's okular package, please try the new package when available and report if it fixes the problem for you.

[Lenar (lenar)]

Binary package hint: okular

Can provide offending pdf file privately.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/okular
Package: okular 4:4.1.96-0ubuntu1
ProcCmdline: /usr/bin/okular /home/music/other/InDesign\ CS3\ for\ Dummies.pdf -icon okular -caption Okular
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdegraphics
StacktraceTop:
 Poppler::convertAnnotColor ()
 Poppler::Page::annotations ()
 ?? () from /usr/lib/kde4/okularGenerator_poppler.so
 ?? () from /usr/lib/kde4/okularGenerator_poppler.so
 ?? () from /usr/lib/kde4/okularGenerator_poppler.so
Title: okular crashed with SIGSEGV in Poppler::convertAnnotColor()
Uname: Linux 2.6.28-4-generic x86_64
UserGroups: audio cdrom dialout floppy music plugdev scard uml-net video work

[Apport retracing service (apport)]

StacktraceTop:Poppler::Page::annotations (this=0x21ad1e0)
PDFGenerator::addAnnotations (
PDFGenerator::loadPages (this=0x209a920,
PDFGenerator::init (this=0x209a920,
PDFGenerator::loadDocument (this=0x209a920,

[Connor Imes (ckimes)]

This bug has also been filed on Launchpad at https://bugs.launchpad.net/poppler/+bug/320269
Thank you.

[Albert Astals Cid (aacid)]

Has anyone retried after the okular rebuild? Did it get fixed?

[Greg Grossmeier (greg.grossmeier)]

The original reporter to the Launchpad bug (referenced above) stated that the build in Jaunty (4:4.2.0-0ubuntu1) fixes the issue.

Unless someone else can reproduce this bug with the latest build, I'm marking it as Fixed.

[Lenar (lenar)]

With latest okular (4:4.2.0-0ubuntu1) this doesn't happen anymore with the same PDF.
Maybe it's OK now.

[Greg Grossmeier (greg.grossmeier)]

Lenar,

If you can't reproduce the problem in the Jaunty version that is great!

Marking Fix Released and informing upstream of that the new build fixes the issue.

[Luka Renko (lure)]

Yes, this is fixed with new KDE 4.2 packages, so I can confirm it was just rebuild issue.