Bug 210501 - Okular crashes when trying to open a PDF
Summary: Okular crashes when trying to open a PDF
Status: RESOLVED DUPLICATE of bug 210428
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-14 02:56 UTC by Robert
Modified: 2009-10-14 19:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert 2009-10-14 02:56:14 UTC
Application that crashed: okular
Version of the application: 0.9.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.26.8.tex3 i686

What I was doing when the application crashed:
First Okular would fail to open a PDF.  Then when I tried again, the program crashed.

 -- Backtrace:
Application: Okular (okular), signal: Segmentation fault
[KCrash Handler]
#9  0xb2df0af4 in Poppler::Page::formFields () from /usr/lib/libpoppler-qt4.so.3
#10 0xb5cf5846 in qt_plugin_query_verification_data () from /usr/lib/kde4/okularGenerator_poppler.so
#11 0xb5cfa60b in qt_plugin_query_verification_data () from /usr/lib/kde4/okularGenerator_poppler.so
#12 0xb5cfb581 in qt_plugin_query_verification_data () from /usr/lib/kde4/okularGenerator_poppler.so
#13 0xb5cfe07d in qt_plugin_instance () from /usr/lib/kde4/okularGenerator_poppler.so
#14 0xb47a5e70 in Okular::DocumentViewport::toString () from /usr/lib/libokularcore.so.1
#15 0xb47b319d in Okular::Document::openDocument () from /usr/lib/libokularcore.so.1
#16 0xb484c3f5 in qt_plugin_instance () from /usr/lib/kde4/okularpart.so
#17 0xb7f4e14e in KParts::ReadOnlyPart::openUrl () from /usr/lib/libkparts.so.4
#18 0xb483ea54 in qt_plugin_instance () from /usr/lib/kde4/okularpart.so
#19 0x0804f948 in _start ()
#20 0x0804fa66 in _start ()
#21 0x0805033c in _start ()
#22 0xb7321d26 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb7322a77 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb7327071 in QTimer::start () from /usr/lib/libQtCore.so.4
#25 0xb732719c in QTimer::start () from /usr/lib/libQtCore.so.4
#26 0xb731b8e3 in QObject::event () from /usr/lib/libQtCore.so.4
#27 0xb69007ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#28 0xb690830e in QApplication::notify () from /usr/lib/libQtGui.so.4
#29 0xb790e201 in KApplication::notify () from /usr/lib/libkdeui.so.5
#30 0xb730b41d in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#31 0xb733a051 in QEventDispatcherUNIX::registerTimer () from /usr/lib/libQtCore.so.4
#32 0xb73377ae in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#33 0xb61d632c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#34 0xb61d9d68 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#35 0xb61d9e8e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0xb7337708 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#37 0xb69a3b1a in QX11Info::copyX11Data () from /usr/lib/libQtGui.so.4
#38 0xb7309a5d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#39 0xb7309eb1 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#40 0xb730c38a in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#41 0xb6900664 in QApplication::exec () from /usr/lib/libQtGui.so.4
#42 0x0804e687 in _start ()
#43 0xb656ca36 in __libc_start_main () from /lib/i686/libc.so.6
#44 0x0804dab1 in _start ()

This bug may be a duplicate of or related to bug 210255

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-14 03:28:38 UTC
As bug 210428 / bug 210255, this is caused by some downstream issue (packaging?) on PcLinuxOS. Thanks

*** This bug has been marked as a duplicate of bug 210428 ***
Comment 2 Robert 2009-10-14 19:36:28 UTC
Yep, and it looks like an update I ran later that night fixed the issue.