We have moved to a new Sailfish OS Forum. Please start new discussions there.

[bug] Alarm set but clock does not show

asked 2018-03-02 08:22:45 +0300

cy8aer gravatar image

updated 2018-03-02 08:32:03 +0300

I have six applications running every time, one of these is the clock application. System uptime >24h so the clock app is running more than one day.

  • clock app: there is an alarm defined but disabled.
  • (I do not know how the alarm was enabled) Statusbar shows enabled alarm
  • (night) alarm starts end ends after some ringdings. When looking into the clock app to disable the alarm the alarm is still disabled
  • (night + intervall time) alarm starts. Clock app: still disabled.
  • Enabling and disabling the alarm in clock app: Statusbar shows still enabled alarm.
  • Closing clock app and starting it again: App shows enabled alarm. Now it is possible to disable the alarm.
  • Having an Ohrwurm in the head: ring-ding -ding-ding, ring-ding, -ding-ding (congrats to your sound designer)

IMHO there is a syncing problem between the clock app and the system settings. When opening the running application it shoud resync it's settings with the system to show the real state.

ring-ding -ding-ding, ring-ding -ding-ding...

edit retag flag offensive close delete

1 Answer

Sort by » oldest newest most voted

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

spiiroin gravatar image

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.

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools



Asked: 2018-03-02 08:22:45 +0300

Seen: 100 times

Last updated: Mar 05 '18