Created attachment 188531 [details] Desktop view when Kalarm is activated after calendar format update Updated Opensuse Tumbleweed Linux to 2026-01-03 version. Kalarm, which I have used for years, asked to update file format. I told it to do so. All the window title bars, absent any content, of all my alarms appeared on the desktop but the Kalarm icon in the system tray never appeared. Ie, hung. This will happen every time if I update at the beginning of the kalarm session. === I then copied the backup .ics file to the active file, ran Kalarm again, and told it NOT to update the format. All my alarm windows appeared as normal but only had the option to close the window as they are read-only. Expected behavior. I then closed all the open read-only alarms, went to the calendar, and told it to update. Closed kalarm, reopened, and again only the title bars appear and kalarm never finished coming up, image attached. KDE Plasma Version: 6.5.4 Qt: 5.15.18 KDE Frameworks: 5.116.0 kf5-config: 1.0
I don't see this behaviour on my system. If you are willing to share it, it would be useful to test using your calendar.ics to see if I can reproduce it. If for privacy reasons you don't want to attach it to this bug report, perhaps you could either send it to me privately, or alternatively edit a copy of the file to change all the DESCRIPTION field contents (for example to DESCRIPTION:x ) and attach the edited file. The only update to the calendar format relates to how sub-repetition intervals counted in days are stored. If you don't have any alarms with such sub-repetitions, you can safely edit calendar.ics to change the line near the top of the file from X-KDE-KALARM-VERSION:2.7.0 to X-KDE-KALARM-VERSION:3.12.0 This will then prevent KAlarm from asking to update the file format. It would still be very useful for me to have a copy (or edited copy) of your calendar file so that I can investigate the bug and try to fix it for other people. Thank you.
Thank you very much for sending your calendar and config files, which allowed me to reproduce the bug. Date-only alarms could cause KAlarm to enter an infinite loop in some circumstances. As it happens, it was actually triggered by your calendar, not your config, even though you were able to fix it by changing your config. The bug has now been fixed for KAlarm version 3.12.2 which will be release in KDE Gear 25.12.2 (commit 27a71dd7835c4b83830547580d6260d7dc8a771e).