https://bugs.kde.org/show_bug.cgi?id=460442
--- Comment #4 from Rafal <m6vuth...@mozmail.com> --- (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. -- You are receiving this mail because: You are watching all bug changes.
