Application that crashed: okular Version of the application: 0.9.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.32-3-686 i686 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: I updated a PDF document (with PDFLateX, in Kile) while it was already opened in Okular. when PDFLateX was done, Okular refreshed automatically and crashed. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #6 QMap<int, Okular::PagePrivate::PixmapObject>::findNode (this=0x84e5e68, id=3, width=989, height=1398) at /usr/include/qt4/QtCore/qmap.h:431 #7 QMap<int, Okular::PagePrivate::PixmapObject>::constFind (this=0x84e5e68, id=3, width=989, height=1398) at /usr/include/qt4/QtCore/qmap.h:559 #8 Okular::Page::hasPixmap (this=0x84e5e68, id=3, width=989, height=1398) at ../../okular/core/page.cpp:203 #9 0xb41a6d52 in Okular::DocumentPrivate::sendGeneratorRequest (this=0x81fb810) at ../../okular/core/document.cpp:837 #10 0xb41ac900 in Okular::Document::qt_metacall (this=0x81e1d20, _c=QMetaObject::InvokeMetaMethod, _id=23, _a=0xbfeb0188) at ./document.moc:145 #11 0xb6eba303 in QMetaObject::activate (sender=0x84e4090, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #12 0xb6ebaf42 in QMetaObject::activate (sender=0x84e4090, m=0xb6f95d88, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #13 0xb6ec0007 in QSingleShotTimer::timeout (this=0x84e4090) at .moc/release-shared/qtimer.moc:76 #14 0xb6ec012c in QSingleShotTimer::timerEvent (this=0x84e4090) at kernel/qtimer.cpp:298 #15 0xb6eb539f in QObject::event (this=0x84e4090, e=0xbfeb062c) at kernel/qobject.cpp:1074 #16 0xb64e4a94 in QApplicationPrivate::notify_helper (this=0x815e558, receiver=0x84e4090, e=0xbfeb062c) at kernel/qapplication.cpp:4065 #17 0xb64ecbee in QApplication::notify (this=0xbfeb0988, receiver=0x84e4090, e=0xbfeb062c) at kernel/qapplication.cpp:3605 #18 0xb7429e2a in KApplication::notify (this=0xbfeb0988, receiver=0x84e4090, event=0xbfeb062c) at ../../kdeui/kernel/kapplication.cpp:302 #19 0xb6ea51eb in QCoreApplication::notifyInternal (this=0xbfeb0988, receiver=0x84e4090, event=0xbfeb062c) at kernel/qcoreapplication.cpp:610 #20 0xb6ed3e21 in QCoreApplication::sendEvent (this=0x816127c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #21 QTimerInfoList::activateTimers (this=0x816127c) at kernel/qeventdispatcher_unix.cpp:580 #22 0xb6ed0317 in timerSourceDispatch (source=0x81612b8) at kernel/qeventdispatcher_glib.cpp:184 #23 idleTimerSourceDispatch (source=0x81612b8) at kernel/qeventdispatcher_glib.cpp:231 #24 0xb5c4db38 in g_main_dispatch (context=0x8160858) at /build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:1960 #25 IA__g_main_context_dispatch (context=0x8160858) at /build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:2513 #26 0xb5c513d0 in g_main_context_iterate (context=0x8160858, block=<value optimized out>, dispatch=1, self=0x815df50) at /build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:2591 #27 0xb5c51503 in IA__g_main_context_iteration (context=0x8160858, may_block=1) at /build/buildd-glib2.0_2.22.4-1-i386-jRfNZE/glib2.0-2.22.4/glib/gmain.c:2654 #28 0xb6ed0041 in QEventDispatcherGlib::processEvents (this=0x8148d28, flags=...) at kernel/qeventdispatcher_glib.cpp:407 #29 0xb6584305 in QGuiEventDispatcherGlib::processEvents (this=0x8148d28, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #30 0xb6ea383a in QEventLoop::processEvents (this=0xbfeb08a0, flags=...) at kernel/qeventloop.cpp:149 #31 0xb6ea3c82 in QEventLoop::exec (this=0xbfeb08a0, flags=...) at kernel/qeventloop.cpp:201 #32 0xb6ea60d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #33 0xb64e4917 in QApplication::exec () at kernel/qapplication.cpp:3525 #34 0x0804ef79 in main (argc=2, argv=0xbfeb0b54) at ../../../okular/shell/main.cpp:81 This bug may be a duplicate of or related to bug 228404 Reported using DrKonqi
May be duplicate of https://bugs.kde.org/show_bug.cgi?id=218895
Please update to KDE 4.4.2 and see if it still happens for you, if it still does please open a new bug *** This bug has been marked as a duplicate of bug 218895 ***