Application: kpresenter (2.3.1) KDE Platform Version: 4.7.2 (4.7.2) "release 5" Qt Version: 4.7.4 Operating System: Linux 3.1.0-1.2-desktop x86_64 Distribution: "openSUSE 12.1 (x86_64)" -- Information about the crash: - How to make KPresenter crash: 1) From a file manager, open a saved presentation in KPresenter. 2) Edit it 3) Save it 4) Close it KPresenter will crash immediately when closing, and DrKonqui will pop up. There does not appear to be any problem with saving. Bug 262962 looks related, but I was unable to reproduce that. The crash can be reproduced every time. -- Backtrace: Application: KPresenter (kdeinit4), signal: Segmentation fault [KCrash Handler] #6 operator== (value=0, this=0x4545454545454551) at /usr/include/QtCore/qbasicatomic.h:70 #7 data (this=0x126da68) at /usr/include/QtCore/qsharedpointer_impl.h:575 #8 DeleteCommand::~DeleteCommand (this=0x15e1640, __in_chrg=<optimized out>) at /usr/src/debug/koffice-2.3.1/plugins/textshape/commands/DeleteCommand.cpp:312 #9 0x00007f1b7e4dec49 in DeleteCommand::~DeleteCommand (this=0x15e1640, __in_chrg=<optimized out>) at /usr/src/debug/koffice-2.3.1/plugins/textshape/commands/DeleteCommand.cpp:326 #10 0x00007f1b9d9b4e1f in QUndoStack::clear() () from /usr/lib64/libQtGui.so.4 #11 0x00007f1b8ad3e021 in KoMainWindow::setRootDocument (this=0x9860c0, doc=0x0) at /usr/src/debug/koffice-2.3.1/libs/main/KoMainWindow.cpp:497 #12 0x00007f1b8ad3e799 in closeEvent (e=0x7fffeda309c0, this=0x9860c0) at /usr/src/debug/koffice-2.3.1/libs/main/KoMainWindow.cpp:1055 #13 KoMainWindow::closeEvent (this=0x9860c0, e=0x7fffeda309c0) at /usr/src/debug/koffice-2.3.1/libs/main/KoMainWindow.cpp:1046 #14 0x00007f1b9d3b365e in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #15 0x00007f1b9d770fab in QMainWindow::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #16 0x00007f1b9f03f6b8 in KXmlGuiWindow::event (this=0x9860c0, ev=0x7fffeda309c0) at /usr/src/debug/kdelibs-4.7.2/kdeui/xmlgui/kxmlguiwindow.cpp:126 #17 0x00007f1b9d362be4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #18 0x00007f1b9d367a71 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #19 0x00007f1b9ef42e36 in KApplication::notify (this=0x7fffeda313d0, receiver=0x9860c0, event=0x7fffeda309c0) at /usr/src/debug/kdelibs-4.7.2/kdeui/kernel/kapplication.cpp:311 #20 0x00007f1b9e1b081c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #21 0x00007f1b9d3ae1bd in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /usr/lib64/libQtGui.so.4 #22 0x00007f1b9d3e06a6 in QApplication::x11ClientMessage(QWidget*, _XEvent*, bool) () from /usr/lib64/libQtGui.so.4 #23 0x00007f1b9d3dea44 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #24 0x00007f1b9d4062a2 in ?? () from /usr/lib64/libQtGui.so.4 #25 0x00007f1b999be58d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #26 0x00007f1b999bed88 in ?? () from /usr/lib64/libglib-2.0.so.0 #27 0x00007f1b999bef59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #28 0x00007f1b9e1db50f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #29 0x00007f1b9d405f2e in ?? () from /usr/lib64/libQtGui.so.4 #30 0x00007f1b9e1afa22 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #31 0x00007f1b9e1afc1f in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #32 0x00007f1b9e1b3de7 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #33 0x00007f1b8aff615d in kdemain (argc=<optimized out>, argv=0x70c500) at /usr/src/debug/koffice-2.3.1/kpresenter/part/main.cpp:44 #34 0x0000000000408897 in _start () This bug may be a duplicate of or related to bug 262962. Possible duplicates by query: bug 262962. Reported using DrKonqi
Couldn't reproduce the bug, possible duplicate to 262962. I must say that you probably were unable to reproduce the bug you think is a duplicate, because it has been fixed.
The problem is fixed and it works in the upcomming calligra 2.4 release. If possible try to use the 2.4 beta as it is a big improvement already. *** This bug has been marked as a duplicate of bug 262962 ***