FS#76165 - [libical] some manually added calendars disappear with the last update

Attached to Project: Arch Linux
Opened by Torus (T0t0) - Monday, 10 October 2022, 22:40 GMT
Last edited by Antonio Rojas (arojas) - Monday, 17 October 2022, 21:13 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Antonio Rojas (arojas)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

The version 3.0.15-1 of 'libical' breaks local date additions with the 'pantheon-calendar'.
'~/.local/share/evolution/calendar/system/calendar.ics' is unreadable.

Additional info:
* package version(s): 3.0.15-1 > bad 3.0.14-3 > ok
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:

Upgrade to the latest version.
This task depends upon

Closed by  Antonio Rojas (arojas)
Monday, 17 October 2022, 21:13 GMT
Reason for closing:  Fixed
Additional comments about closing:  libical 3.0.16
Comment by Martin Diehl (MartinDiehl) - Tuesday, 11 October 2022, 13:22 GMT
There are also issues in combination with evolution, reported upstream to libical https://github.com/libical/libical/issues/610 and evolution https://gitlab.gnome.org/GNOME/evolution/-/issues/2070
Comment by Nicky726 (Nicky726) - Friday, 14 October 2022, 10:29 GMT
The issue with libical=3.0.15 also affects local callendar in Korganizer/Kontact/Akonadi. There, however, callendar did not dissappear from the apliaction, as it is cached by Akonadi (I think), and also new events were created in this cached copy, only the local file did not update, which I did not notice at first. The other hint for the issue is an error message "Cound not open ical file" when akonadi is started visible in console output and Akonadi Console application.

Fortunately, the cached callendar can be exported to ical file when using libical=3.0.15. This file still cannot be opend with libical=3.0.15, however it contains all the events and can be opened with libical=3.0.14.
Comment by Darrell (0strodamus) - Friday, 14 October 2022, 23:44 GMT
I have noticed that libical-3.0.15 is also causing orage to reset ~/.local/share/orage/orage{.ics,_persistent_alarms.txt} to defaults. I know this program was dropped by Arch a long time ago and I'm only posting as an extra data point, not for support.
Comment by Branimir Amidzic (ambra) - Sunday, 16 October 2022, 18:18 GMT
KAlarm also has problems with libical-3.0.15.
See https://bugs.kde.org/show_bug.cgi?id=460442
Comment by Branimir Amidzic (ambra) - Monday, 17 October 2022, 20:16 GMT
I have just tested libical 3.0.15-2, and the problem is still present for KAlarm. Can you please check?
Comment by Toolybird (Toolybird) - Monday, 17 October 2022, 20:16 GMT
Dupe  FS#76227 
Comment by Martin Diehl (MartinDiehl) - Monday, 17 October 2022, 20:22 GMT
The developer proposes to revert two changes (2ca167a and ca3e2ad, see https://github.com/libical/libical/issues/610). The current PKGBUILD reverts only one. Reverting the other helps to solve my issues on evolution. Note: The patch generated by GitHub does not work because it is for changes that are not in 3.0.15. Attached is what works for me.
   PKGBUILD (1.9 KiB)
   ca3e2ad983771b90da259994b7a6d... (1.4 KiB)
Comment by Daniel Apolinario (dapolinario) - Monday, 17 October 2022, 21:02 GMT
New version released: 3.0.16 (https://github.com/libical/libical/releases/tag/v3.0.16).

Loading...