Bug 179284

Summary:	SIGSEGV when trying to save autosave.xmi
Product:	[Applications] umbrello	Reporter:	Duane Berry <d.m.berry>
Component:	general	Assignee:	Umbrello Development Group <umbrello-devel>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	andresbajotierra, cfeck, ralf.habacker
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Other
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Duane Berry 2009-01-01 15:05:16 UTC

Version:           2.1.2 (using KDE 4.1.2)
Compiler:          Compliation done by KDE 4 Mac (mac.kde.org) using KDE 4.1.2 target is Power Mac G5, OS-X 10.4 (Tiger)
OS:                OS X
Installed from:    Unlisted Binary Package

With Autosave on Umbrello crashes with the 'unable to save autosave.xmi' message.  

Application: Umbrello UML Modeller (umbrello), signal SIGSEGV
Attaching to process 342.
Reading symbols for shared libraries . done
Reading symbols for shared libraries .................................................................................................................................................... done
[KCrash handler]
#4  0x90b932a0 in FileIDTree_GetAndLockSharedUniverse ()
#5  0x013310b0 in QMetaObject::changeGuard ()
#6  0x0131c16c in QCoreApplicationPrivate::sendThroughObjectEventFilters ()
#7  0x00000003 in ?? ()
#8  0x02b5041c in QAbstractScrollArea::event ()
#9  0x00000003 in ?? ()
#10 0x6c696361 in ?? ()

**> Turning the autosave off prevents this error.

Attempting to save manually then generates the following:

Could not start process Cannot talk to klauncher: The name org.kde.klauncher was not provided by any .service files.


The diagram being created consisted of two classes with one implementation connection.

Comment 1 Dario Andres 2009-09-28 01:20:36 UTC

- Did the situation improved with an updated KDE ?
Thanks

Comment 2 Christoph Feck 2013-09-12 21:35:14 UTC

This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), 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 CONFIRMED)