Bug 184976 - The application Okular (okular) crashed and caused the signal 6 (SIGABRT).
Summary: The application Okular (okular) crashed and caused the signal 6 (SIGABRT).
Status: RESOLVED DUPLICATE of bug 180291
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-19 22:29 UTC by nr.12345
Modified: 2009-03-30 18:12 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 nr.12345 2009-02-19 22:29:32 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

Anwendung: Okular (okular), Signal SIGABRT
0x00007faaa2a366e1 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7faaa618d6f0 (LWP 6553)):
[KCrash Handler]
#5  0x00007faaa29c1015 in raise () from /lib/libc.so.6
#6  0x00007faaa29c2b83 in abort () from /lib/libc.so.6
#7  0x00007faaa40626b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007faaa40627fd in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007faa9bb7c204 in ?? () from /usr/lib/kde4/okularpart.so
#10 0x00007faa9bb7d076 in ?? () from /usr/lib/kde4/okularpart.so
#11 0x00007faaa36c730f in QWidget::event () from /usr/lib/libQtGui.so.4
#12 0x00007faa9bb770ca in ?? () from /usr/lib/kde4/okularpart.so
#13 0x00007faaa3674c3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#14 0x00007faaa367d22a in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0x00007faaa4f675db in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0x00007faaa4152d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#17 0x00007faaa367c5c8 in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#18 0x00007faaa36e0be9 in ?? () from /usr/lib/libQtGui.so.4
#19 0x00007faaa36df607 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#20 0x00007faaa37072c4 in ?? () from /usr/lib/libQtGui.so.4
#21 0x00007faa9f7e5d3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0x00007faa9f7e950d in ?? () from /usr/lib/libglib-2.0.so.0
#23 0x00007faa9f7e96cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0x00007faaa417b15f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#25 0x00007faaa3706a6f in ?? () from /usr/lib/libQtGui.so.4
#26 0x00007faaa4151682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#27 0x00007faaa415180d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#28 0x00007faaa4153cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#29 0x0000000000407df4 in _start ()
Comment 1 Dario Andres 2009-02-19 23:00:26 UTC
What were you doing when the application crashed?
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here?
You need to install the "kdegraphics-dbg" package
Thanks :)
Comment 2 nr.12345 2009-02-21 22:57:41 UTC
sorry, i can bad english. I hope, you can me understand what i mean.
ok, i have install the "kdegraphics-dbg" package. i can the bug reproduce.
i have a pdf-document, when i this open, open a window with a retrieval for the "Präsentationsmodus" (Ctrl-Shift-P). i make ok, and a new -emty- Window opend with a blue cirle in the right up  angle. when i click in this cirle, chrashed okular with follow report:

Anwendung: Okular (okular), Signal SIGABRT
0x00007fc961e6c6e1 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7fc9655c26f0 (LWP 6373)):
[KCrash Handler]
#5  0x00007fc961df7015 in raise () from /lib/libc.so.6
#6  0x00007fc961df8b83 in abort () from /lib/libc.so.6
#7  0x00007fc9634986b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007fc9634987fd in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007fc95afad347 in PresentationWidget::routeMouseDrawingEvent (this=0xf5ed80, e=0x7fff6d5eff50) at /usr/include/qt4/QtCore/qvector.h:325
#10 0x00007fc95afb2ef1 in PresentationWidget::mousePressEvent (this=0x18e5, e=0x7fff6d5eff50) at /build/buildd/kdegraphics-4.2.0/okular/ui/presentationwidget.cpp:445
#11 0x00007fc962afd30f in QWidget::event () from /usr/lib/libQtGui.so.4
#12 0x00007fc95afad0ca in PresentationWidget::event (this=0xf5ed80, e=0x18e5) at /build/buildd/kdegraphics-4.2.0/okular/ui/presentationwidget.cpp:393
#13 0x00007fc962aaac3d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#14 0x00007fc962ab322a in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0x00007fc96439d5db in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0x00007fc963588d61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#17 0x00007fc962ab25c8 in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#18 0x00007fc962b16be9 in ?? () from /usr/lib/libQtGui.so.4
#19 0x00007fc962b15607 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#20 0x00007fc962b3d2c4 in ?? () from /usr/lib/libQtGui.so.4
#21 0x00007fc95ec1bd3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0x00007fc95ec1f50d in ?? () from /usr/lib/libglib-2.0.so.0
#23 0x00007fc95ec1f6cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0x00007fc9635b115f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#25 0x00007fc962b3ca6f in ?? () from /usr/lib/libQtGui.so.4
#26 0x00007fc963587682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#27 0x00007fc96358780d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#28 0x00007fc963589cbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#29 0x0000000000407df4 in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdegraphics-4.2.0/okular/shell/main.cpp:81
Comment 3 Pino Toscano 2009-03-30 18:05:12 UTC
Might be a duplicate of bug #180291.
Worth check again after KDE 4.2.2.
Comment 4 Pino Toscano 2009-03-30 18:12:34 UTC
At a second look, it seems it really is.

In case you should still have the same problem once KDE 4.2.2 is released, please reopen this bug.

*** This bug has been marked as a duplicate of bug 180291 ***