Bug 226242

Summary:	Kontact freezes after adding event to calendar through Akonadi Google Connector
Product:	[Applications] kontact	Reporter:	Anshul Jain <anshulajain>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	cfeck, kdenis, nicolas, rainer.kastl, tassilo, vkrause
Priority:	NOR
Version First Reported In:	4.4.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Log from Konsole

Description Anshul Jain 2010-02-11 05:41:54 UTC

Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    openSUSE RPMs

Running Kontact on Opensuse 11.2 updated to 4.4.0 final release. I also have the akonadi-googledata connector installed to communicate with Google Calendar. Kontact freezes permanently after adding/deleting a resources. Steps are:-

1. Open Kontact and ensure that the akonadi-googledata resource is installed
2. Add a new event
3. Now delete this event
4. Kontact freezes and the sidebar (where Kmail, Kaddressbook etc are present) is unbrowsable.

I have Nepomuk disabled as well. Attached is the output from the konsole when this happens.

Comment 1 Anshul Jain 2010-02-11 05:43:01 UTC

Created attachment 40654 [details]
Log from Konsole

Comment 2 Doualot Nicolas 2010-03-04 23:19:22 UTC

Same problem here.

When adding an event to a webdav ics calendar file, kontact window freeze.
When deleting events no freeze.

Comment 3 Tassilo Horn 2010-03-26 08:28:25 UTC

Quite similar problem here using 4.4.1.  I don't use akonadi-googledata or webdav, but a normal akonadi calendar resource.

But it only happens, if I had the summary view open before.  Does the same apply to you, too?  If so, then check out bug #226636.

Comment 4 Tassilo Horn 2010-03-30 13:01:26 UTC

Bug 221445 is also related, or maybe this bug is a duplicate of it.

Comment 5 Christoph Feck 2013-09-12 21:39:10 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)