Bug 76168

Summary: program crashed cause to invalid xmi file
Product: [Applications] umbrello Reporter: maor <maorva>
Component: generalAssignee: Umbrello Development Group <umbrello-devel>
Status: RESOLVED NOT A BUG    
Severity: crash    
Priority: NOR    
Version: 1.2   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: the corrupt file from the crashing.
unloadable XMI resulting from a crash

Description maor 2004-02-26 09:22:23 UTC
Version:           1.2 (using KDE KDE 3.2.0)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.3.2 20031022 (Gentoo Linux 3.3.2-r2, propolice)
OS:          Linux (i686) release 2.6.3-mm3

while editing some sequence diagram, the program crashed cause to the xmi file to be unusable while traying to load the file, got an error messege: there was a problem loading file.
Comment 1 maor 2004-02-26 09:23:58 UTC
Created attachment 4894 [details]
the corrupt file from the crashing.
Comment 2 YeHaa 2004-03-02 09:46:36 UTC
Created attachment 4973 [details]
unloadable XMI resulting from a crash

I have the same problem. I edited a class-diagram, the program crashed, and now
I cannot load the file anymore. Really frustrating, since umbrello creates no
backups while saving.
Comment 3 Jonathan Riddell 2004-03-12 10:07:38 UTC
The second file (from Jan Schnackenberg) seems to load fine in current CVS.

The first file seems to cause Umbrello to freeze.

This kind of report is unfortunatly very difficult to solve since the cause is not clear so I shall have to close it as invalid.  If you have any more information please do attach it.

Appologies for the lack of a solution.
Comment 4 Jean-Loup Rebours 2004-11-08 00:59:33 UTC
It happened to me several times to try and edit a file, have umbrello corrupt it and then completely erase it (I opened the xmi file in Kwrite and it turned out blank though the original was 7 complex class diagrams)
Comment 5 Jonathan Riddell 2004-11-08 01:17:13 UTC
Jean: which version of Umbrello were you using?