| Summary: | kOrganizer 5.4.1: Importing event from ics file twice will add it twice to backend storage with same UID, causing erratic UI behaviour | ||
|---|---|---|---|
| Product: | [Applications] korganizer | Reporter: | Gunter Ohrner <kdebugs> |
| Component: | import/export | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 5.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Gunter Ohrner
2017-01-06 11:44:02 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... 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! 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. 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! 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! |