460442 – Unable to use KAlarm because "no writable active calendar is enabled"

Bug 460442 - Unable to use KAlarm because "no writable active calendar is enabled"

Summary: Unable to use KAlarm because "no writable active calendar is enabled"

Status:	RESOLVED UPSTREAM

Alias:	None

Product:	kalarm
Classification:	Applications
Component:	general (show other bugs)
Version:	3.5.2
Platform:	Arch Linux Linux

Importance:	NOR major
Target Milestone:	---
Assignee:	David Jarvie

URL:
Keywords:

Duplicates (1):	460389 (view as bug list)
Depends on:
Blocks:

Reported:	2022-10-14 17:39 UTC by Rafal
Modified:	2022-10-18 07:33 UTC (History)
CC List:	3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
The alert that is shown on every startup (24.34 KB, image/png) 2022-10-14 17:39 UTC, Rafal	Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description Rafal 2022-10-14 17:39:30 UTC

Created attachment 152820 [details]
The alert that is shown on every startup

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Create a calendar file
2.  Add your alarms, notifications and reminders
3.  Save everything
4. Restart your machine

OBSERVED RESULT
The `calendar.ics` file is broken after every restart.

EXPECTED RESULT
KAlarm should work as usual (all reminders/alarms should work and be persisted from the previous session)




SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 6.0.1-arch2-1 (64-bit)
Graphics Platform: X11

ADDITIONAL INFORMATION

console output:

$ kalarm
parse error from icalcomponent_new_from_string. string= "BEGIN:VCALENDAR\r\nPRODID:-//K Desktop Environment//NONSGML KAlarm 3.5.1//EN\r\nVERSION:2.0\r\nX-KDE-ICAL-IMPLEMENTATION-VERSION:1.0\r\nX-KDE-KALARM-VERSION:2.7.0\r\nBEGIN:VTIMEZONE\r\nTZID:Europe/Warsaw\r\nBEGIN:DAYLIGHT\r\nTZNAME:CEST\r\nTZOFFSETFROM:+0000\r\nTZOFFSETTO:+0200\r\nDTSTART:19770403T000000\r\nRDATE:19770403T000000\r\nEND:DAYLIGHT\r\nBEGIN:STANDARD\r\nTZNAME:CET\r\nTZOFFSETFROM:+0200\r\nTZOFFSETTO:+0100\r\nDTSTART:19790930T020000\r\nRRULE:FREQ=YEARLY;UNTIL=19880925T030000;BYDAY=-1SU;BYMONTH=9\r\nEND:STANDARD\r\nBEGIN:STANDARD\r\nTZNAME:CET\r\nTZOFFSETFROM:+0200\r\nTZOFFSETTO:+0100\r\nDTSTART:19961027T030000\r\nRRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10\r\nEND:STANDARD\r\nBEGIN:STANDARD\r\nTZNAME:CET\r\nTZOFFSETFROM:+0200\r\nTZOFFSETTO:+0100\r\nDTSTART:19770925T020000\r\nRDATE:19770925T020000\r\nRDATE:19781001T020000\r\nRDATE:19870927T020000\r\nRDATE:19890924T030000\r\nRDATE:19900930T030000\r\nRDATE:19910929T030000\r\nRDATE:19920927T030000\r\nRDATE:19930926T030000\r\nRDATE:19940925T030000\r\nRDATE:19950924T030000\r\nEND:STANDARD\r\nBEGIN:DAYLIGHT\r\nTZNAME:CEST\r\nTZOFFSETFROM:+0100\r\nTZOFFSETTO:+0200\r\nDTSTART:19880327T020000\r\nRRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3\r\nEND:DAYLIGHT\r\nBEGIN:DAYLIGHT\r\nTZNAME:CEST\r\nTZOFFSETFROM:+0100\r\nTZOFFSETTO:+0200\r\nDTSTART:19780402T010000\r\nRDATE:19780402T010000\r\nRDATE:19790401T010000\r\nRDATE:19800406T010000\r\nRDATE:19810329T010000\r\nRDATE:19820328T010000\r\nRDATE:19830327T010000\r\nRDATE:19840325T010000\r\nRDATE:19850331T010000\r\nRDATE:19860330T010000\r\nRDATE:19870329T010000\r\nEND:DAYLIGHT\r\nEND:VTIMEZONE\r\nBEGIN:VEVENT\r\nDTSTAMP:20221010T152628Z\r\nX-KDE-KALARM-FLAGS:EXHOLIDAYS;WORKTIME;LATECANCEL;5\r\nX-KDE-KALARM-NEXTRECUR:20221011T170000\r\nX-KDE-KALARM-TYPE:ACTIVE\r\nCREATED:20221010T152628Z\r\nUID:f65ebbdd-0b0d-4463-b9fb-34017eb2accd\r\nLAST-MODIFIED:20221010T152628Z\r\nSUMMARY:Daily Hours Report\r\nRRULE:FREQ=DAILY;BYDAY=MO,TU,WE,TH,FR\r\nDURATION:PT0S\r\nDTSTART;TZID=Europe/Warsaw:20221011T170000\r\nTRANSP:TRANSPARENT\r\nBEGIN:VALARM\r\nDESCRIPTION:Add your hours to Primetric\r\nACTION:DISPLAY\r\nTRIGGER:PT0S\r\nX-KDE-KALARM-FONTCOLOR:#441a1f;#fcfcfc;\r\nX-KDE-KCALCORE-ENABLED:TRUE\r\nEND:VALARM\r\nBEGIN:VALARM\r\nACTION:AUDIO\r\nTRIGGER:PT0S\r\nX-KDE-KCALCORE-ENABLED:TRUE\r\nEND:VALARM\r\nBEGIN:VALARM\r\nATTACH:firefox\r\nDESCRIPTION:https://app.primetric.com\r\nACTION:PROCEDURE\r\nTRIGGER:PT0S\r\nX-KDE-KALARM-TYPE:POST\r\nX-KDE-KCALCORE-ENABLED:TRUE\r\nEND:VALARM\r\nEND:VEVENT\r\nEND:VCALENDAR"
kf.calendarcore: "/home/rwyszomirski/.local/share/kalarm/calendar.ics"  is not a valid iCalendar file
parse error from icalcomponent_new_from_string. string= "BEGIN:VCALENDAR\r\nPRODID:-//K Desktop Environment//NONSGML KAlarm 3.5.1//EN\r\nVERSION:2.0\r\nX-KDE-ICAL-IMPLEMENTATION-VERSION:1.0\r\nX-KDE-KALARM-VERSION:2.7.0\r\nBEGIN:VTIMEZONE\r\nTZID:Europe/Warsaw\r\nBEGIN:DAYLIGHT\r\nTZNAME:CEST\r\nTZOFFSETFROM:+0000\r\nTZOFFSETTO:+0200\r\nDTSTART:19770403T000000\r\nRDATE:19770403T000000\r\nEND:DAYLIGHT\r\nBEGIN:STANDARD\r\nTZNAME:CET\r\nTZOFFSETFROM:+0200\r\nTZOFFSETTO:+0100\r\nDTSTART:19790930T020000\r\nRRULE:FREQ=YEARLY;UNTIL=19880925T030000;BYDAY=-1SU;BYMONTH=9\r\nEND:STANDARD\r\nBEGIN:STANDARD\r\nTZNAME:CET\r\nTZOFFSETFROM:+0200\r\nTZOFFSETTO:+0100\r\nDTSTART:19961027T030000\r\nRRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10\r\nEND:STANDARD\r\nBEGIN:STANDARD\r\nTZNAME:CET\r\nTZOFFSETFROM:+0200\r\nTZOFFSETTO:+0100\r\nDTSTART:19770925T020000\r\nRDATE:19770925T020000\r\nRDATE:19781001T020000\r\nRDATE:19870927T020000\r\nRDATE:19890924T030000\r\nRDATE:19900930T030000\r\nRDATE:19910929T030000\r\nRDATE:19920927T030000\r\nRDATE:19930926T030000\r\nRDATE:19940925T030000\r\nRDATE:19950924T030000\r\nEND:STANDARD\r\nBEGIN:DAYLIGHT\r\nTZNAME:CEST\r\nTZOFFSETFROM:+0100\r\nTZOFFSETTO:+0200\r\nDTSTART:19880327T020000\r\nRRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3\r\nEND:DAYLIGHT\r\nBEGIN:DAYLIGHT\r\nTZNAME:CEST\r\nTZOFFSETFROM:+0100\r\nTZOFFSETTO:+0200\r\nDTSTART:19780402T010000\r\nRDATE:19780402T010000\r\nRDATE:19790401T010000\r\nRDATE:19800406T010000\r\nRDATE:19810329T010000\r\nRDATE:19820328T010000\r\nRDATE:19830327T010000\r\nRDATE:19840325T010000\r\nRDATE:19850331T010000\r\nRDATE:19860330T010000\r\nRDATE:19870329T010000\r\nEND:DAYLIGHT\r\nEND:VTIMEZONE\r\nBEGIN:VEVENT\r\nDTSTAMP:20221010T152628Z\r\nX-KDE-KALARM-FLAGS:EXHOLIDAYS;WORKTIME;LATECANCEL;5\r\nX-KDE-KALARM-NEXTRECUR:20221011T170000\r\nX-KDE-KALARM-TYPE:ACTIVE\r\nCREATED:20221010T152628Z\r\nUID:f65ebbdd-0b0d-4463-b9fb-34017eb2accd\r\nLAST-MODIFIED:20221010T152628Z\r\nSUMMARY:Daily Hours Report\r\nRRULE:FREQ=DAILY;BYDAY=MO,TU,WE,TH,FR\r\nDURATION:PT0S\r\nDTSTART;TZID=Europe/Warsaw:20221011T170000\r\nTRANSP:TRANSPARENT\r\nBEGIN:VALARM\r\nDESCRIPTION:Add your hours to Primetric\r\nACTION:DISPLAY\r\nTRIGGER:PT0S\r\nX-KDE-KALARM-FONTCOLOR:#441a1f;#fcfcfc;\r\nX-KDE-KCALCORE-ENABLED:TRUE\r\nEND:VALARM\r\nBEGIN:VALARM\r\nACTION:AUDIO\r\nTRIGGER:PT0S\r\nX-KDE-KCALCORE-ENABLED:TRUE\r\nEND:VALARM\r\nBEGIN:VALARM\r\nATTACH:firefox\r\nDESCRIPTION:https://app.primetric.com\r\nACTION:PROCEDURE\r\nTRIGGER:PT0S\r\nX-KDE-KALARM-TYPE:POST\r\nX-KDE-KCALCORE-ENABLED:TRUE\r\nEND:VALARM\r\nEND:VEVENT\r\nEND:VCALENDAR"
kf.calendarcore: "/home/rwyszomirski/.local/share/kalarm/calendar.ics"  is not a valid iCalendar file
kf.calendarcore: Error parsing vCalendar file: pop on empty Object Stack
 at line 104
org.kde.pim.kalarm: KAlarmApp::checkWritableCalendar: No writable active calendar

Comment 1 David Jarvie 2022-10-15 19:23:12 UTC

I don't get this issue on my system, which is an up to date KDE Neon development installation. I extracted the calendar file contents from your report to create a calendar file, and that also works correctly in KAlarm for me.

None of the code in KAlarm relating to calendar reading/writing has changed recently. Since KAlarm works for me using the current version of libkf5calendarcore, the KDE library which it uses to access calendar data, it could be that libical, the 3rd party library used by libkf5calendarcore to access iCalendar data, is responsible for what you see.

This bug seems to be specific to ArchLinux (see also https://bugs.kde.org/show_bug.cgi?id=460389 which may be the same issue). If so, this also points to a third party library issue.

What version of libical (possibly libical3) is installed on your system?

Comment 2 Erica J. 2022-10-16 03:48:34 UTC

I had the same issue.  Libical was 3.0.15.  Problem started after updating KDE to 22.08.2, also on Arch.  A fresh Arch install, however, has no problem.  Only one which already existed before the KDE update.  I never found a solution in the two days since I updated, and unfortunately because the update also broke my monitor setup (also working fine in a fresh install) and I use kalarms for very important medications I've had to give up and just start using the fresh install as my daily driver.

Comment 3 Erica J. 2022-10-16 03:51:54 UTC

(In reply to Erica Clawson from comment #2)

Let me note, regarding specifics to Arch Linux, I use only the stable repos and haven't had to reinstall my Arch/KDE setup in over six or seven year until now.  I am not one of those typical "Arch update broke my system" users.

Comment 4 Rafal 2022-10-16 11:53:38 UTC

(In reply to David Jarvie from comment #1)
> I don't get this issue on my system, which is an up to date KDE Neon
> development installation. I extracted the calendar file contents from your
> report to create a calendar file, and that also works correctly in KAlarm
> for me.
> 
> None of the code in KAlarm relating to calendar reading/writing has changed
> recently. Since KAlarm works for me using the current version of
> libkf5calendarcore, the KDE library which it uses to access calendar data,
> it could be that libical, the 3rd party library used by libkf5calendarcore
> to access iCalendar data, is responsible for what you see.
> 
> This bug seems to be specific to ArchLinux (see also
> https://bugs.kde.org/show_bug.cgi?id=460389 which may be the same issue). If
> so, this also points to a third party library issue.
> 
> What version of libical (possibly libical3) is installed on your system?

I'm using version 3.0.15.

Comment 5 Branimir Amidzic 2022-10-16 15:45:47 UTC

This seems to be libical problem. The most recent is 3.0.15. When I downgraded to 3.0.14 everything works fine.

Comment 6 David Jarvie 2022-10-16 16:40:42 UTC

Thank you for confirming that libical version 3.0.15 causes the bug. It would be a good idea to report this problem on the ArchLinux bug reporting system, to ask for a downgrade to 3.0.14.

Comment 7 David Jarvie 2022-10-16 16:44:34 UTC

*** Bug 460389 has been marked as a duplicate of this bug. ***

Comment 8 Rafal 2022-10-18 07:33:09 UTC

I can confirm that the latest upgrade to version 3.0.16 the calendar is now loaded correctly.