Bug 514804

Summary: KAlarm hangs and does not show a window when started
Product: [Applications] kalarm Reporter: daforlynx
Component: generalAssignee: David Jarvie <djarvie>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: https://invent.kde.org/pim/kalarm/-/commit/8337a8cabaf8ff76723234cb7aeabad820908ef3 Version Fixed/Implemented In: 25.12.2
Sentry Crash Report:
Attachments: my calendar
my config

Description daforlynx 2026-01-18 19:35:22 UTC 
SUMMARY
Using the Arch Linux package (25.12.1-1), kalarm cannot start. Instead, it constantly uses 6.1% of my CPU and doesn't appear to function. Nothing appears to be logged. The CLI appears to function, though.
This application worked before, I want to say it stopped working around November but I can't give an exact date.

STEPS TO REPRODUCE
1. Install the Arch Linux package.

OBSERVED RESULT
Kalarm does not start. It doesn't crash, either, and constantly uses one thread of the CPU.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.14.0-rt3-arch1-6-rt (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: AMD Radeon RX 6650 XT


ADDITIONAL INFORMATION
Could be a packaging issue. I noticed it gave libmpv errors since I did not have libmpv, but why would libmpv be required and not included in the dependencies? I would try the AUR -git package, but that requires so many other components to also use their -git package that it's not worth it.
Even if it is a packaging issue, I would like to know if I'm not the only one experiencing it. There's no active issue for it in the Arch repo's Gitlab.
Comment 1 David Jarvie 2026-01-18 19:58:39 UTC 
This may be the same as bug 514609. Can you please attach your active alarms calendar (probably ~/.local/share/kalarm/calendar.ics) and config file (~/.config/kalarmrc). Feel free for privacy to edit your calendar to change the DESCRIPTION fields to 
    DESCRIPTION:x
before attaching it.
Comment 2 daforlynx 2026-01-18 21:30:18 UTC 
Created attachment 188657 [details]
my calendar
Comment 3 daforlynx 2026-01-18 21:31:53 UTC 
Created attachment 188658 [details]
my config
Comment 4 daforlynx 2026-01-18 21:32:07 UTC 
(In reply to David Jarvie from comment #1)
> This may be the same as bug 514609. Can you please attach your active alarms
> calendar (probably ~/.local/share/kalarm/calendar.ics) and config file
> (~/.config/kalarmrc). Feel free for privacy to edit your calendar to change
> the DESCRIPTION fields to 
>     DESCRIPTION:x
> before attaching it.

I uploaded the requested files.
Comment 5 daforlynx 2026-01-18 21:33:55 UTC 
I should note that I was asked to update the format as well; however, it stopped working before this.
Comment 6 David Jarvie 2026-01-20 10:31:08 UTC 
Thank you for the files, which enabled me to track down the bug. The error turned out to be due to a Qt library call which unexpectedly changed a date/time value from standard to daylight savings time, which caused an infinite loop when evaluating the next recurrence time of an alarm.

Fixed for KAlarm version 3.12.2, which will be released in KDE Gear 25.12.2 (commit 8337a8cabaf8ff76723234cb7aeabad820908ef3).