Bug 141277 - linking a note to an actor on a use case diagram makes crash
Summary: linking a note to an actor on a use case diagram makes crash
Status: RESOLVED DUPLICATE of bug 140693
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-06 15:32 UTC by Nicolas Dumoulin
Modified: 2007-02-07 09:15 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 Nicolas Dumoulin 2007-02-06 15:32:54 UTC
Version:           1.5.6 (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages

Tested on an empty user account.

I open umbrello, create a new use case diagram by the "Diagram" menu.

First, the canvas is frozen and I can't add anyone element. I select the default "class diagram" in the tree on the left, and the re-select the use case diagram previously created. Now, I can add an actor and a note. If I try to add an association between the actor and the note, umbrello always crashes.

Partial backtrace :
(no debugging symbols found)
[KCrash handler]
#6  0x0810aea9 in UMLObject::setUMLPackage ()
#7  0x081d7660 in ToolBarStateAssociation::addAssociationInViewAndDoc ()
#8  0x081d78a7 in ToolBarStateAssociation::setSecondWidget ()
#9  0x08111664 in ToolBarState::mouseRelease ()
#10 0xb7869fcf in QScrollView::viewportMouseReleaseEvent ()
   from /usr/lib/libqt-mt.so.3
#11 0xb786b566 in QScrollView::eventFilter () from /usr/lib/libqt-mt.so.3
#12 0xb7733f04 in QObject::activate_filters () from /usr/lib/libqt-mt.so.3
#13 0xb7733f82 in QObject::event () from /usr/lib/libqt-mt.so.3
#14 0xb776b65b in QWidget::event () from /usr/lib/libqt-mt.so.3
#15 0xb76cbb88 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#16 0xb76cdd46 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#17 0xb7e5bc82 in KApplication::notify () from /usr/lib/libkdecore.so.4
#18 0xb765e3fd in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#19 0xb765d062 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3
#20 0xb765b14c in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#21 0xb7672320 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#22 0xb76e625e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#23 0xb76e606e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#24 0xb76cd731 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#25 0x081beb17 in main ()
Comment 1 Oliver Kellogg 2007-02-06 18:59:06 UTC
Hmm, this is being reported often enough to warrant an interim
1.5.61 release which I plan to make within the next few days.

*** This bug has been marked as a duplicate of 140693 ***
Comment 2 Nicolas Dumoulin 2007-02-07 09:15:53 UTC
Sorry for the duplicate

Thank you for your attention, and the fix :-)