Bug 284794 - Words crashes after close
Summary: Words crashes after close
Status: RESOLVED WORKSFORME
Alias: None
Product: calligrawords
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Calligra Words Bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2011-10-23 16:22 UTC by Adria
Modified: 2018-10-27 02:40 UTC (History)
0 users

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 Adria 2011-10-23 16:22:35 UTC
Application: calligrawords (2.4 Beta 3)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Every time I close a document with Calligra words, it crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Words (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f75c4292760 (LWP 25861))]

Thread 2 (Thread 0x7f75a3b03700 (LWP 31843)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f75a3b02b10 in ?? ()
#2  0x00007fff715217e7 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7f75c4292760 (LWP 25861)):
[KCrash Handler]
#6  0x00007f75b1f52890 in KoInlineObject::id() const () from /usr/lib/libkotext.so.8
#7  0x00007f75b1f4e45a in KoInlineTextObjectManager::removeInlineObject(KoInlineObject*) () from /usr/lib/libkotext.so.8
#8  0x00007f75b200bd5e in DeleteCommand::~DeleteCommand() () from /usr/lib/libkotext.so.8
#9  0x00007f75b200bdc9 in DeleteCommand::~DeleteCommand() () from /usr/lib/libkotext.so.8
#10 0x00007f75b16acd6f in KUndo2QStack::clear() () from /usr/lib/libkundo2.so.8
#11 0x00007f75b2591b71 in KoMainWindow::setRootDocument(KoDocument*) () from /usr/lib/libkomain.so.8
#12 0x00007f75b2592359 in KoMainWindow::closeEvent(QCloseEvent*) () from /usr/lib/libkomain.so.8
#13 0x00007f75c20f249e in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#14 0x00007f75c24afd7b in QMainWindow::event(QEvent*) () from /usr/lib/libQtGui.so.4
#15 0x00007f75c3d80848 in KXmlGuiWindow::event(QEvent*) () from /usr/lib/libkdeui.so.5
#16 0x00007f75c20a1ae4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0x00007f75c20a6951 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x00007f75c3c83bb6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0x00007f75c2ee889c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#20 0x00007f75c20ed04d in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /usr/lib/libQtGui.so.4
#21 0x00007f75c211f896 in QApplication::x11ClientMessage(QWidget*, _XEvent*, bool) () from /usr/lib/libQtGui.so.4
#22 0x00007f75c211dbf9 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4
#23 0x00007f75c2145282 in ?? () from /usr/lib/libQtGui.so.4
#24 0x00007f75be9817fd in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0x00007f75be981ff8 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0x00007f75be9821c9 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0x00007f75c2f13606 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0x00007f75c2144eee in ?? () from /usr/lib/libQtGui.so.4
#29 0x00007f75c2ee7a92 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x00007f75c2ee7c97 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0x00007f75c2eebeab in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#32 0x00007f75b2860ead in kdemain () from /usr/lib/libkdeinit4_calligrawords.so
#33 0x00000000004082a7 in _start ()

Reported using DrKonqi
Comment 1 Camilla Boemann 2011-10-23 21:03:04 UTC
I can not reproduce. Can you please add a new backtrace or describe more precisely what you did
Comment 2 Andrew Crouthamel 2018-09-22 01:55:03 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 02:40:30 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!