Summary: | Crashes when I create a message in sequence diagram | ||
---|---|---|---|
Product: | [Applications] umbrello | Reporter: | Brett <brettelliott> |
Component: | general | Assignee: | Umbrello Development Group <umbrello-devel> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | crash | CC: | cfeck, ralf.habacker |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | xmi file to reproduce |
Description
Brett
2007-10-05 09:54:20 UTC
Created attachment 21755 [details]
xmi file to reproduce
I can reproduce this using the attached .xmi file and Umbrello 1.5.8 (Ubuntu 7.10). I get the following output: kbuildsycoca running... umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect UMLOperation::modified() to (null)::setMessageText() umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: WARNING: returning 0 at UMLListView::findView umbrello: ERROR: ObjectWidget::messageAdded(reset) : duplicate entry ! umbrello: ERROR: ObjectWidget::messageAdded(add) : duplicate entry ! Segmentation fault (core dumped) This crash report is at least 4 years old and there were no further comments or status updates since then. Therefore we believe that this crash is already fixed in KDE 4 or the backtrace is no longer applicable to KDE 4. If the crash still happens with a recent KDE version (4.7.4 or 4.8), 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 NEW) |