Bug 384023 - IncidenceEditor sometimes clings to last remaining category
Summary: IncidenceEditor sometimes clings to last remaining category
Status: RESOLVED DUPLICATE of bug 431297
Alias: None
Product: korganizer
Classification: Applications
Component: incidence editors (show other bugs)
Version: 5.9.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-25 20:26 UTC by Denis Kurz
Modified: 2021-01-28 01:43 UTC (History)
3 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 Denis Kurz 2017-08-25 20:26:17 UTC
When de-selecting the last remaining category of an event and then trying to save, instead of saving, IncidenceEditor pops a dialog about some Akonadi exception.



Dialog 1: [incidencechanger.cpp:427 in akonadi-calendar]
Error while trying to modify calendar item. Error was: Akonadi::Exception: No objects specified
[OK]



Clicking OK leads to Dialog 2: [incidencedialog.cpp:490 in incidenceeditor]
Unable to store the incidence in the calendar. Try again?

Reason: Akonadi::Exception: No objects specified
[Yes] [No]



Yes loops back to dialog 1, No lets me control IncidenceDialog again, but without saving the item with no categories. A click on Abort in IncidenceDialog, and it asks me to discard changes. If I do, and reopen it for the same event, the category is still set.

Strangly, the issue does not occur on all my events, but on most. On some few, the dialog lets me remove all categories. I could not find any pattern, though.

Setting an arbitrary non-empty set of categories works for every event, only the empty set has this issue.

Version is 5.6.0, which is currently not in bugzilla (although underway).
Comment 1 Boian Berberov 2017-09-22 09:18:10 UTC
Occurs exactly as described above on openSUSE Tumbleweed, Korganizer 5.6.1, except I can never remove all categories.
Comment 2 Denis Kurz 2018-10-31 17:46:19 UTC
Still valid in 18.08.2.
Comment 3 gjditchfield 2021-01-28 01:43:19 UTC

*** This bug has been marked as a duplicate of bug 431297 ***