Summary: | cant activate rtc wakeup | ||
---|---|---|---|
Product: | [Applications] kalarm | Reporter: | zak <dz.wbdev> |
Component: | general | Assignee: | David Jarvie <djarvie> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 3.8.1 | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/pim/kalarm/-/commit/97ef99f19570fb1ffaaed2b1d56df03bdf2e02bc | Version Fixed In: | 24.08.2 |
Sentry Crash Report: |
Description
zak
2024-04-27 04:14:41 UTC
The RTC wake-up code using kernel timers was contributed by somebody else who I don't have a contract for, and unfortunately I can't test it on my system. Running the following command might fix the problem: systemd-run --user --collect --unit kalarm --property=AmbientCapabilities=CAP_WAKE_ALARM -- kalarm You may possibly need to quit KAlarm first and then restart it after running the command (or perhaps it will only work if executed while KAlarm is running). It would be very helpful if you could report whether this does fix the problem, and if so whether KAlarm needs to be running when it is executed. Thank you. Looking at this again, I realise that kernel timers are not relevant after all. It looks like the KAuth process which executed rtcwake was exiting before rtcwake had completed. The bug should now be fixed in KAlarm version 3.9.2, which will be released in KDE Gear 24.08.2, by commit 97ef99f19570fb1ffaaed2b1d56df03bdf2e02bc. If the bug still occurs using KAlarm 3.9.2 or later, please reopen this bug report. |