Bug 159387 - creates duplicate diagrams after a crash, crashes when you try to close
Summary: creates duplicate diagrams after a crash, crashes when you try to close
Status: RESOLVED UNMAINTAINED
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-16 02:21 UTC by Johnny
Modified: 2014-05-23 18:23 UTC (History)
2 users (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 Johnny 2008-03-16 02:21:30 UTC
Version:           1.5.8 (using 3.5.9-5.fc7 Fedora, Fedora release 7 (Moonshine))
Compiler:          Target: x86_64-redhat-linux
OS:                Linux (x86_64) release 2.6.22

I tried to undo a change by using <ctrl-z> (Open Office keystroke for undo - habitual I'm afraid) and umbrello crashed. Upon re-opening I found there were a bunch of duplicated use case and er diagrams (5-10 dupes). 

To reproduce: Make a diagram select something on the page, press delete and then  <ctrl-z> to attempt to undo.

After the crash I reopen it, tidy it up (deleting the duplicates) and when I try to close the 'project' (so I can start a new one) umbrello crashes, hopefully this backtrace is usefull (I can give you a sample file if you want, it's not a critical project I'm learning the UML using Umbrello).

backtrace info

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47195568243456 (LWP 2974)]
[KCrash handler]
#5  0x0000003132eb3030 in typeinfo for QDomElement ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#6  0x0000000000536cea in UMLDoc::saveToXMI ()
#7  0x0000000000522f83 in UMLDoc::addToUndoStack ()
#8  0x0000000000581905 in UMLDoc::newDocument ()
#9  0x0000000000581dab in UMLApp::slotFileNew ()
#10 0x0000000000581e7e in UMLApp::slotFileClose ()
#11 0x0000000000599bc8 in UMLApp::qt_invoke ()
#12 0x0000003132763979 in QObject::activate_signal ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#13 0x0000003132764660 in QObject::activate_signal ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#14 0x00000032b66d6d6d in KAction::slotPopupActivated ()
   from /usr/lib64/libkdeui.so.4
#15 0x00000032b66d7013 in KAction::qt_invoke () from /usr/lib64/libkdeui.so.4
#16 0x0000003132763979 in QObject::activate_signal ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#17 0x0000003132a9b074 in QSignal::signal ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#18 0x000000313277ed65 in QSignal::activate ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#19 0x000000313286a52a in QPopupMenu::mouseReleaseEvent ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#20 0x000000313279a989 in QWidget::event ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#21 0x0000003132702945 in QApplication::internalNotify ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#22 0x0000003132703e00 in QApplication::notify ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#23 0x00000032b57dbf28 in KApplication::notify ()
   from /usr/lib64/libkdecore.so.4
#24 0x00000031326a23e7 in QETWidget::translateMouseEvent ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#25 0x00000031326a0f15 in QApplication::x11ProcessEvent ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#26 0x00000031326b0e74 in QEventLoop::processEvents ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#27 0x000000313271a0d1 in QEventLoop::enterLoop ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#28 0x0000003132719fb2 in QEventLoop::exec ()
   from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
#29 0x000000000059a691 in main ()
Comment 1 Johnny 2008-03-16 02:24:40 UTC
let me know if you would like the file that I was having the problems with - thanks
Comment 2 Christoph Feck 2013-09-12 21:35:05 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)