Bug 67419

Summary: duplicate entries in tree view from moving objects, deleting causes crash
Product: [Applications] umbrello Reporter: Heather Krieg <hsk>
Component: generalAssignee: Umbrello Development Group <umbrello-devel>
Status: RESOLVED WORKSFORME    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: trace and system info for umbrello crash

Description Heather Krieg 2003-11-06 17:18:45 UTC 
Version:            (using KDE KDE 3.1.92)
Installed from:    Compiled From Sources
OS:          Linux

This may be related to Bug 59774.

There are a few problems I've seen with this, using KDE 3.1.92.

Create a class
Create a folder
Move the class in the tree view unsuccessfully (move it around and drop it back onto itself)

A bunch of copies of the class will appear in the tree view.  The "original" will have an icon, but the copies are just text.

Delete one of the copies.  
In one of my tests, this caused a crash.
If it doesn't, select one of the copies.
This does cause a crash.  (Most likely because the class no longer exists.)

Another bug:
Create a class
Create a folder
Move the class to the folder
The tree view disappears.
When I tried to close the file without saving the changes, umbrello crashed.
Comment 1 Oliver Kellogg 2003-11-06 23:12:02 UTC 
It's strange. When I was working on giving packages folder-like
qualities, I remember having seen what you describe -
but then I stopped seeing it and assumed that it fixed
itself somehow.
Just now I tried reproducing the behaviour, but without luck.
Any takers?
Comment 2 Heather Krieg 2003-11-10 21:54:41 UTC 
Created attachment 3136 [details]
trace and system info for umbrello crash

Here is the trace from the KDE crash report.  The file also has a list of some
of the packages installed on the machine.  If needed, I can also attach the
kdesdk config/build log in case there is something useful there.
Comment 3 Brian Thomas 2003-12-02 22:17:27 UTC 
I also remember seeing this bug, but it appears to be working for me. I believe this is fixed now.