Bug 374629 - kOrganizer 5.4.1: Importing event from ics file twice will add it twice to backend storage with same UID, causing erratic UI behaviour
Summary: kOrganizer 5.4.1: Importing event from ics file twice will add it twice to ba...
Status: RESOLVED WORKSFORME
Alias: None
Product: korganizer
Classification: Applications
Component: import/export (show other bugs)
Version: 5.4.0
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-06 11:44 UTC by Gunter Ohrner
Modified: 2022-11-30 05:16 UTC (History)
0 users

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 Gunter Ohrner 2017-01-06 11:44:02 UTC
I'm using kOrganizer with an iCal file as backend storage.

If a have an iCal file with an event and import it twice, it will actually be added twice to the backend storage file with the same UID (the UID provided by the imported file).

This should probably not happen, as the UID should be unique and a re-import should be treated more like a kind of "update" request, I guess?

This behaviour also leads to strange UI behaviour:

* Import an event once, assig a label to it and a coloring.
  It will be displayed fine. Now import this event again. Label and coloring
  will be gone, but the event will only be displayed once.

  The event will be contained twice in the backend iCal file.

* After doing the above, delete the event in kOrganizer. It will be removed from
  the view.

  However, only one instance of this event will be deleted from the backing
  store iCal file and one instance will remain. I've yet to check if this will
  cause the event to re-appear after restarting kOrganizer / logging out and
  back in...
Comment 1 Gunter Ohrner 2017-01-06 11:46:25 UTC
(In reply to Gunter Ohrner from comment #0)
> * After doing the above, delete the event in kOrganizer. It will be removed
>   from the view.
> 
>   However, only one instance of this event will be deleted from the backing
>   store iCal file and one instance will remain. I've yet to check if this
>   will cause the event to re-appear after restarting kOrganizer / logging
>   out and back in...

In fact, it does - it's actually sufficient to close and reopen kOrganizer and the event will re-appear...
Comment 2 Justin Zobel 2022-10-30 00:37:28 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Gunter Ohrner 2022-10-31 07:57:20 UTC
Due to too many bugs in kMail / kOrganizer some years ago I stopped using it and
switched to Thunderbird.
I was not happy to have to make that choice, but since then at least I didn't lose
access to my mails any more because some maintenance update does not work at
all - as it happened more than once with kMail unfortunately. :-(

So I cannot re-test.
Comment 4 Bug Janitor Service 2022-11-15 05:15:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2022-11-30 05:16:37 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!