Bug 255989

Summary:	ETM crash when adding an event with DAV or Open-XChange resources
Product:	[Applications] kdepim	Reporter:	Grégory Oestreicher <greg>
Component:	libkdepim	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	BT of the crash generated from DrKonqui

Description Grégory Oestreicher 2010-11-03 19:26:52 UTC

Created attachment 53103 [details]
BT of the crash generated from DrKonqui

Version:           unspecified (using Devel) 
OS:                Linux

It is possible to crash the EntityTreeModel (and Plasma) by creating an event in KOrganizer in a calendar managed by the DAV or Open-XChange resources. This happens every time with the same BT

Reproducible: Always

Steps to Reproduce:
Create a calendar with the DAV resource. It is possible to use one available at http://caldav-test.ioda.net/ if no other CalDAV test server is available. Create a new event from KOrganizer, whatever the content.

Actual Results:  
Plasma crashes with the attached BT, showing that this happens in the ETM.

Expected Results:  
Nothing should crash.

This crash does not happens with the iCal resource. Only the two listed here were tested. Their common point is that when an item is created both of them do not call changeCommitted() in itemAdded(), but must wait for the return of an upload job; changeCommitted() is then called after the job has successfully run (which it always did in the test cases).

Comment 1 Dario Andres 2010-12-12 19:14:35 UTC

[Comment from a bug triager]
The backtrace is mostly the same as the one in bug 252049.
Regards

Comment 2 Denis Kurz 2016-09-24 21:00:43 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 3 Denis Kurz 2017-01-07 21:47:42 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.