Version: 1.5.71 (using KDE 3.5.6, Kubuntu (feisty) 4:3.5.6-0ubuntu14.1) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.20-16-386 Crashes when I create a message in sequence diagram. I will attach the file. To reproduce: 1) load js.xml 2) go to 'sequence user add product store' 3) Try f(x) from ChooserStore to PojoStoreAvailable Crashes in 1.5.71
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)