This just flat out crashes kalarm.
Any other option works fine, from creation to the actual alarm trigger, however I specifically need that functionality - the dismissible popup window.
What i do:
Launch Kalarm.
Press that option.
Crash
When I do it in the terminal:
╭─alucard@battlestation ~
╰─➤ kalarm #here I reproduce the steps from above
org.kde.pim.kalarm: Wake from suspend: use RTC (no CAP_WAKE_ALARM capability)
[1] 13289 segmentation fault (core dumped) kalarm
I can’t pinpoint exactly when this issue started, but the error would seem to suggest it was around the time I changed power management options.
I usually don’t turn off my computer unless I leave my home for a time. I use it as an alarm clock. But I never switched those power mgmt options - screens on 24/7, no dimming, no suspend, no hibernate. I did chaggne them recently to dim the screen after 1 minute and turn them off after 2.
I currently have a “sound alarm” set up (the second to last option in the ss), but that is not ideal as it is not easily dismissible as the popup, like in this screenshot:
I am on Endeavor OS, I try to keep my packages up to date.
I need help in identifying the issue and possibly fixing it.
Please let me know what logs I’d need to atach.
KAlarm Version 3.12.0 (KDE Gear 25.12.0) is smooth here…
KDE Plasma 6.5.4, Qt 6.10.1
Wayland.
You could test with a new USER account to check - then the issue is likely in your data/settings folders…
But yes, it’s possible you messed up some power management settings… I haven’t done that, and Kalarm puts my machine to sleep at night, and gently wakes me up in the morning:
rtcwake -m no -l -t $(date +%s -d 'tomorrow 0559'); sets the wakeup… delayed-suspend.sh suspends unless I skip.
However, you can set commands to wake up the computer - and I suspect that’s where your issue lies.
org.kde.pim.kalarm: Wake from suspend: use RTC (no CAP_WAKE_ALARM capability)
[1] 13289 segmentation fault (core dumped) kalarm
I get this:
➤ kalarm
org.kde.pim.kalarm: Wake from suspend: use RTC (no CAP_WAKE_ALARM capability)
So not too informative I’m afraid.
So as usual:
Check your mirrors and make sure they’re all ‘green’… maybe try ‘shiny-mirrors’ (I didn’t do this on EOs)
If you do change mirrors, then: sudo pacman -Syy will refresh everything.
Then: sudo pacman -Syu and check all output.
I think EOs has a distribution package for doing mirrors eos-rankmirrors so look into using that.
Thanks for the reply
I created a new user ktester.
I logged into that acocunt and tried running kalarm from the terminal, same results, but slightly different errors:
[ktester@battlestation ~]$ kalarm
org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to D-Bus auto-launch
org.kde.pim.kalarm.akonadiplugin: AkonadiResourceMigrator::checkServer: Failed to start Akonadi server
org.kde.pim.kalarm: Wake from suspend: use RTC (no CAP_WAKE_ALARM capability)
Naruszenie ochrony pamięci(zrzut pamięci) kalarm
[ktester@battlestation ~]$
[ktester@battlestation Pulpit]$
Though the final one is still a segfault, like on my default user.
I refreshed the mirrors, did the package updates. No errors, no feedback.
I’m not sure how can I force restoring the default power management config (in this window or terminal command if needed)
I’m having the same issue with kalarm 3.12.1 on CachyOS. When I start kalarm from a terminal the main window shows up but I get the following output in my terminal:
rg.kde.pim.kalarm: Wake from suspend: use kernel alarm timer
qt.qpa.services: Failed to register with host portal QDBusError(“org.freedesktop.portal.Error.Failed”, “Could not register app ID: Unable to open /proc/7597/root”)
If I do: File → New →New Display Alarm then the application crashes with the following message in the terminal.
fish: Job 1, ‘kalarm’ terminated by signal SIGSEGV (Address boundary error)
If I open kalarm and right click an existing alarm and choose edit, the same happens.
Also the existing display alarms no longer work correctly. They show their popup message at the scheduled time but the configured audio file does not play.
If KAlarm crashes, can you please use DrKonqi (which hopefully should pop up automatically) to get a stack trace and submit a bug report at bugs.kde.org. Without this, it’s impossible to investigate the crash (unless the developers can reproduce the bug themselves, which currently they can’t).
Please note that the following terminal messages are purely informational and do not indicate an error:
org.kde.pim.kalarm: Wake from suspend: use RTC (no CAP_WAKE_ALARM capability)
org.kde.pim.kalarm: Wake from suspend: use kernel alarm timer
Sorry if this isn’t the right place to ask.
DrKonqi apparently doesn’t ship with Endeavor by default, but I installed ith with pacman and followed the sysctl enable from drkonqi github repo
I reproduced the bug and sent the DrKonqi report after that - is there a way I can find it on the bugtracker?
Thank you for trying to report the bug with DrKonqi. For some reason, no new KAlarm bug report has been created. I don’t know what might have gone wrong - this should have worked.
It would be really helpful if you could try again, so that the crash can hopefully be fixed. The preferred way (assuming that DrKonqi can’t create a report) is to go to https://bugs.kde.org and use the “File a Bug” button to create a new bug report (you’ll need to create an account to do this). Then copy the stack trace ( the “developer information”) from DrKonqi and paste it into the bug report. The other way would be to copy the stack trace from DrKonqi and paste it into a message directly to me. I would then create a bug report with the details, and put a link here for you to track progress.
Just my darned luck, though. Suddenly I am unable to reproduce - the Display Alarm (finally leaned how that option is named in English ) has returned in full. Ran kalarm, clicked the option expecting it to crash, but noooo… the dialog popped up,created an alarm with the window, sound and repeats and it fired as (un)expected.
I did recently run a full package update (through yay so some AUR packages also got in the mix), but I doubt it had anything to do with that (kalarm wasn’t among the updated packages, still on 3.12.1 (KDE Gear 25.12.1)).
So, while my issue appears solved, I won’t mark the thread as such just yet.
