Bug 301510 - Color assignment from korganizer lost upon editing/replacing calendar ics file using outside tool
Summary: Color assignment from korganizer lost upon editing/replacing calendar ics fil...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: ICal file resource (show other bugs)
Version: 1.7.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-09 14:53 UTC by m.h.vankerkwijk
Modified: 2017-01-07 21:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m.h.vankerkwijk 2012-06-09 14:53:45 UTC
I synchronize my calendar files between home and office using unison, and for any calendar file that is changed, the color assignment is lost. This behavior can be reproduced generally by replacing/editing an .ics file outside of korganizer.

Reproducible: Always

Steps to Reproduce:
1. Add a trial event in a calendar file using korganizer
2. Edit that calendar file with an outside tool, removing the trial event
3. Overwrite calendar file with the edited version.
Actual Results:  
Upon replacing a largish .ics file, one sees in korganizer how first all entries belonging to that file are  removed (rather slowly, even though I have a fast workstation), and then how they are added back in with a different colour.

Expected Results:  
Korganizer should show the replaced calendar with the color assignment that belonged to that file.

I checked in .kde/share/config/korganizerrc, and noticed that the many times I have by now corrected the color assignments has led to a very long list of "akonadi:?collection\x3d...=....", so it looks like that akonadi starts a new collection whenever a file is changed, and that korganizer, not surprisingly, doesn't know that really this collection reflects the same file, just with updated content.
Comment 1 auxsvr 2012-10-21 11:36:43 UTC
In my case, the owncloud resource is set as default, and every time kontact starts, it is either deselected and with random colour, or completely missing, in which case I have to restart kontact. This on KDE 4.9.2 on openSUSE 12.1.
Comment 2 Stefan Huber 2014-01-28 12:53:14 UTC
I guess, if the feature from bug #328862 would be implemented, this could resolve this issue in an elegant way.
Comment 3 Denis Kurz 2016-09-24 20:43:32 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 21:31:10 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.