Bug 110512

Summary:	Disabling followed by enabling a remote resource in Resource View under Calendar crashes Korganize
Product:	[Applications] korganizer	Reporter:	Jon Sporring <sporring>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	christophe
Priority:	NOR
Version First Reported In:	3.4.1
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jon Sporring 2005-08-10 16:34:48 UTC

Version:           3.4.1 (using KDE 3.4.1, Gentoo)
Compiler:          gcc version 3.3.5-20050130 (Gentoo Linux 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)
OS:                Linux (i686) release 2.6.11-gentoo-r11

I don't think this one has been reported amongst the many remote source causes crash reports:

I have put my full calendar on a web-site in ics format, with the intent that other people could read my schedule.  However, loading it as a remote source through the Resource view, crashes korganize after activating the remote source and the deactivating again.  This is repeatable on a different machine with the same system and versions.  Further, Korganize cannot be restarted again without immediate crashing!  To get Korganize to run againg I've had to remove the remote source by hand from .kde/share/config/kresources/calendar/stdrc.

I've also found a workaround:  If I Archive Old Entries, in effect making the calendar considerably smaller, then I don't experience the above problem.  That would hint at a memory allocation problem?

Best, Jon

Comment 1 Bram Schoenmakers 2005-09-02 00:46:05 UTC

Can you please provide us a backtrace?

Comment 2 Anders Berg 2005-11-24 13:30:54 UTC

I've experienced a crash in the same situation (no backtrace, sorry, will send if it happens again). What happened to me was that the remote file was *DELETED*. Completely. Wow. Thanks for backups, but as you know most people don't make such, and for a shared calendar it'd be a disaster.

I figure it could be something with concurrency; upload when download isn't finished or such. Probably the sync procedure has to be thoroughly checked, since it seems to be a major source of problems.

Having said all this, I'd also like to express my thanks for the work put in by all OS coders in the project!

greets
/Anders

Comment 3 Reinhold Kainhofer 2006-11-02 19:01:15 UTC

Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.

Comment 4 Christophe Marin 2008-11-02 14:57:38 UTC

No backtrace was provided since 2005-09-02. Closing.