Bug 481129 - When adding an ICAL calendar file to korganizer the resource first fails to work then duplicates in the GUI …
Summary: When adding an ICAL calendar file to korganizer the resource first fails to w...
Status: REPORTED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 5.22.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-02-09 17:12 UTC by Flossy Cat
Modified: 2024-02-09 17:12 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 Flossy Cat 2024-02-09 17:12:54 UTC
SUMMARY
When adding an ICAL calendar file (as opposed to an ICAL calendar directory) to korganizer the resource first fails to work then duplicates in the GUI into a functional and a non-functional twin.


STEPS TO REPRODUCE
1. Start »kalarm« to produce an empty ICS file (correct VCALENDAR data structures without VEVENTS or VTODOS produced by KDE library »libkcal«) (Reason for this see https://bugs.kde.org/show_bug.cgi?id=481024)
2. optional: completely stop »kalarm« to prevent any interaction of the 2 programms
3. within »korganizer« settings create a new ICS file calendar with path /home/XXXXX/.local/share/kalarm/calendar.ics and optionally a choosen name
4. the calendar will be created and displayed in the »korganizer« GUI but your name choice will be ignored and something like "akonadi_ical_resource_5" will be displayed.
5. monitor the calendar file "/home/XXXXX/.local/share/kalarm/calendar.ics" for changes with the tool set of your choice.
6. with »korganizer« add events and/or todos to this new calendar – you wont see changes in the ICS file.
5. Restart the calendar within »korganizer« settings (calendar tab) – while the number of calendars in the calendar tab stays the same, in the »korganizer« GUI the calendar suddenly duplicates: one with your choosen name, one still with "akonadi_ical_resource_5" or the like.
7. with »korganizer« add events and/or todos to the calendar with your choosen name – they are written to the ICS file.
8. with »korganizer« add events and/or todos to the calendar with the "akonadi_ical_resource_5"-style name – they will not find their way into the ICS file (but are display in the calendar!).
9. delete the dysfunctional "akonadi_ical_resource_5"-style named calendar – both vanish …

OBSERVED RESULT
Described in detail in the steps above.

The same behavior is observed invariant of the following:

* The ICS file is an RFC 5545 conformant empty VCALENDAR file – i.e. the file is NOT empty, but contains a proper VCALENDAR structure without events or todos like so:

BEGIN:VCALENDAR
PRODID:-//K Desktop Environment//NONSGML libkcal 4.3//EN
VERSION:2.0
X-KDE-ICAL-IMPLEMENTATION-VERSION:1.0
X-KDE-KALARM-VERSION:2.7.0
…
END:VCALENDAR

* or the file contains proper events or todos.

* The file is or is not opened in parallel by »kalarm«. 

EXPECTED RESULT
A single calendar is added which works correctly and displays its given name correctly. 
(preferably directly or at least after a restart of the calendar).

SOFTWARE/OS VERSIONS
[copied from System Information]
Operating System: openSUSE Leap 15.5
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.14.21-150500.55.44-default (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-10210U CPU @ 1.60GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

ADDITIONAL INFORMATION
As a seasoned computer engineer I might help with changes if brought up to speed …

POSSIBLE DUPLICATE
The bug report https://bugs.kde.org/show_bug.cgi?id=452588 – but the path to error state is more convoluted than in my case.