Document from https://arxiv.org/pdf/1604.04228v1 (ca 10MByte) Okular crashes with SIGABRT, when using poppler-0.46.0 (confirmed by 3 others on irc) Document is displayed when using poppler-0.45 according to report on irc (gdb) run --nocrashhandler ~/Downloads/1604.04228v1.pdf Starting program: /usr/bin/okular --nocrashhandler ~/Downloads/1604.04228v1.pdf [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Program received signal SIGABRT, Aborted. 0x00007ffff4e181f7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 55 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 0x00007ffff4e181f7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x00007ffff4e1964a in __GI_abort () at abort.c:89 #2 0x00007fffe5548758 in Object::dictLookup (recursion=0, this=0x7fffffffce40, this=0x7fffffffce40, obj=0x7fffffffce50, key=0xf43c48 "Title") at /var/tmp/portage/app-text/poppler-0.46.0/work/poppler-0.46.0/poppler/Object.h:335 #3 PDFDoc::getDocInfoStringEntry (this=<optimized out>, key=0xf43c48 "Title") at /var/tmp/portage/app-text/poppler-0.46.0/work/poppler-0.46.0/poppler/PDFDoc.cc:654 #4 0x00007fffe58c5ddf in Poppler::Document::info (this=0xea13d0, type=...) at /var/tmp/portage/app-text/poppler-0.46.0/work/poppler-0.46.0/qt4/src/poppler-document.cc:288 #5 0x00007fffe5b03483 in PDFGenerator::metaData (this=0xe39220, key=..., option=...) at /var/tmp/portage/kde-apps/okular-16.04.3/work/okular-16.04.3/generators/poppler/generator_pdf.cpp:1155 #6 0x00007fffe7feb91f in Okular::Document::metaData (this=0xa9a6a0, key=..., option=...) at /var/tmp/portage/kde-apps/okular-16.04.3/work/okular-16.04.3/core/document.cpp:3026 #7 0x00007fffe830a9df in Okular::Part::setWindowTitleFromDocument (this=0x7462c0) at /var/tmp/portage/kde-apps/okular-16.04.3/work/okular-16.04.3/part.cpp:1076 #8 0x00007fffe831b365 in Okular::Part::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=0x7fffffffd1a0, _c=<optimized out>) at /var/tmp/portage/kde-apps/okular-16.04.3/work/okular-16.04.3_build/part.moc:253 #9 0x00007ffff58f741c in QMetaObject::activate (sender=sender@entry=0x7462c0, m=m@entry=0x7ffff7dd6dc0 <KParts::ReadOnlyPart::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at /var/tmp/portage/dev-qt/qtcore-4.8.7-r2/work/qt-everywhere-opensource-src-4.8.7/src/corelib/kernel/qobject.cpp:3567 #10 0x00007ffff7ba5e33 in KParts::ReadOnlyPart::completed (this=this@entry=0x7462c0) at /var/tmp/portage/kde-base/kdelibs-4.14.22/work/kdelibs-4.14.22_build/kparts/part.moc:252 #11 0x00007ffff7ba6e65 in KParts::ReadOnlyPartPrivate::openLocalFile (this=this@entry=0x746620) at /var/tmp/portage/kde-base/kdelibs-4.14.22/work/kdelibs-4.14.22/kparts/part.cpp:594 #12 0x00007ffff7ba91f6 in KParts::ReadOnlyPart::openUrl (this=this@entry=0x7462c0, url=...) at /var/tmp/portage/kde-base/kdelibs-4.14.22/work/kdelibs-4.14.22/kparts/part.cpp:555 #13 0x00007fffe830e9ab in Okular::Part::openUrl (this=0x7462c0, _url=...) at /var/tmp/portage/kde-apps/okular-16.04.3/work/okular-16.04.3/part.cpp:1528 #14 0x000000000040f194 in Shell::openUrl (this=this@entry=0x700b40, url=..., serializedOptions=...) at /var/tmp/portage/kde-apps/okular-16.04.3/work/okular-16.04.3/shell/shell.cpp:240 #15 0x000000000040f3dc in Shell::openDocument (this=this@entry=0x700b40, url=..., serializedOptions=...) at /var/tmp/portage/kde-apps/okular-16.04.3/work/okular-16.04.3/shell/shell.cpp:186 #16 0x000000000040a2bc in Okular::main (paths=..., serializedOptions=...) at /var/tmp/portage/kde-apps/okular-16.04.3/work/okular-16.04.3/shell/okular_main.cpp:169 #17 0x0000000000409b9a in main (argc=<optimized out>, argv=<optimized out>) at /var/tmp/portage/kde-apps/okular-16.04.3/work/okular-16.04.3/shell/main.cpp:51 (gdb) More information on request...
Fixed, sorry for the regression :/
*** Bug 97335 has been marked as a duplicate of this bug. ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.