[bug] Alarm set but clock does not show

answered 2018-03-05 10:30:16 +0200

spiiroin
13237 ●151 ●224 ●199

  moderator

Are you sure it is clock alarm that is ringing (has familiar title or something)?

If possible, the first thing to do would be to check if alarm service has logged any issues (this needs to be done as root, so developer mode needs to be activated etc):

journalctl /usr/bin/timed-qt5  -a

If there are issues, rebooting the device / restarting timed service might also be needed. But do check the alarm queue status etc as shown below before doing this (as it could clear what ongoing situation is causing the issues):

systemctl --user restart timed-qt5.service # if running as regular user
systemctl-user restart timed-qt5.service # if running as root user

You can use timedclient utility to inspect what kind of alarms are currently queued.

timedclient-qt5 -i

Alarms that have "APPLICATION = libextendedkcal" are controlled by calendar application.

Alarms that have "APPLICATION = nemoalarms" are controlled by clock app and are further divided into clock alarms (type = clock) and countdown timers (type = countdown).

If there are alarms that look like they should be visible in clock application, but either are not / the state differs from what is shown in the clock alarm - you can remove them manually based on "cookie" number shown by timedclient - as an example:

timedclient-qt5 -c 4

Note: If there are running countdown timers, they must be stopped from the clock ui too. And you need to restart clock app to refresh the list of alarms after removing things via command line.