# Bug: timed breaks / alarm clock alarms vanished

I have 3 alarms and one count-down timer in use on my Jolla. Last night, I opened the clock app to set the alarm for the morning and for some weird reason the clock app just displayed the clock in the top and the rest of the view was empty. Restarting the app several times did not help.

I first assumed that my alarms and the timer got deleted somehow and tried to create a new alarm, but the newly created alarm was not displayed either.

After restarting the phone, the clock app showed my original 3 alarms and the timer again, but the additional alarm I had created before the boot has not been shown ever. Now everything seems to be back to normal again, all newly created alarms are displayed properly.

I sincerely hope this doesn't affect the actual alarm functionality...

EDIT: This happened to me again yesterday. No idea what I did in the mean time. I'd be also grateful for comments on how to help debug this.

EDIT2: This happened to me again, and I noticed that timed coincidentally does not answer anything on dbus anymore. timedclient-qt5 -i gives

[W] cookies_get:947 - 'query' call failed: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")


Restarting timed (systemctl --user restart timed-qt5.service) fixed things and I got the alarms back.

edit retag close delete

From the fact that neither tag 'timed' nor 'timed-qt5' are appearing anymore, I assume neither of them was approved? Would anyone care to explain why not? Quite obviously this is strongly related to timed.

( 2015-04-07 10:31:00 +0300 )edit

To continue my monologue: Since this situation seems to occur only after uptime is well over 1 week, I try to workaround this one by having timed restart itself (oh, yes) once a day. This obviously relies on the assumption that timed will not go bad after having run only for a day. Also, some self-daemonizing shell script magic was necessary to be able to trigger the restart from timed itself. Let's see where this gets me.

( 2015-04-09 09:45:43 +0300 )edit

This indeed sounds like timed crashing. As a system service managed by systemd timed is restarted if it shuts down, in this case it sounds like the restarting has failed as well. An alternative explanation for the missing alarms would be that timed is unresponsive.

@Jolly-Jo: please do attach the journal log here if you encounter this bug again, this kind of malfunction is bound to leave something in the log. You can store the log contents to a file by running the following as root: journalctl > journal.log.

The output of systemctl --user status timed-qt5 is useful too, it shows whether the timed-qt5 service is running or not.

( 2015-05-19 09:32:44 +0300 )edit

@PMG AFAIR timed is still listed by ps, so it hasn't crashed. Also the fact that manual restarting fixes the issue contradicts this theory. (Like you mentioned it should be restarted automatically if crashed.) So most likely the dbus part just does not respond anymore.

This only happened to me with uptime > 20 days or so. Since I experienced also other problems with high uptime (lipstick and apps eating memory), my phone now reboots every 7 days automatically. So I'm positive I won't see this again. But in case I do see it, I will post logs.

( 2015-05-21 10:54:42 +0300 )edit

@PMG: I have just encountered the same problem, only that systemctl --user restart timed-qt5.service did not bring back any of my disappeared alarms. Sadly journalctl does not go far enough back to serve you with usable output. I remember that the browser freaked out not allowing any keyboard input to a TJC comment field which lead into a critical storage error and quickly flashing yellow LED. I rebooted the phone and everything worked again. Today I found out that the alarms were gone.

( 2015-05-28 13:45:23 +0300 )edit

Sort by » oldest newest most voted

Probably this old bug is returned...
I never had this bug before update to 2.0.5.6, but now I have it on all my 3 devices and I can't catch what cause to this...
I get exactly the same error like in the first post, even with the same number (947). On jolla C it happens often than on jolla1 and tablet, maybe because it primary device and used often.
I'm already on direct communication with Simo, he tried to help me investigate what cause to this and why...
Also for catching the specific period when crash happens, I created a simple script that work with systemd.timer. Script run every 1 min and check if one of my Cookies available (timedclient-qt5 -g cookie_num) and if it not, it send journalctl -x > /home/nemo/Templates/timed.log and will restart timed-qt5.service. In this case I can see exactly when happened something between "All is Ok" and "Timed-qt5 is broken".
I will update my post when I will get something new...
P.S. Also when it happens, not only alarms disappears from Clock app, calendar events also disappear from calendar app, and all restored after restart of timed-qt5 service... at least in my case...

more

I suffer from this bug too and quite often. It's still happening with the newest OS version.

more

I have created https://bugs.merproject.org/show_bug.cgi?id=1584 to track this issue.

Can anyone provide logs (devel-su journalctl -a > logs.txt) and then redact those logs of personal information and send them to me at chris dot adams at jolla dot com so that I can try to see what caused timed to hang? Thanks!

( 2016-05-13 05:36:20 +0300 )edit

Logs sent, good luck!

( 2016-05-30 14:08:18 +0300 )edit

Hi @yanoo, I sent Simo the logs and he said that it looked like timed wasn't active at all (i.e. either crashed or hung) and asked if you could collect some more information:

 devel-su systemctl-user status timed-qt5


or

 systemctl --user status timed-qt5


Also, what time was the alarm set for? How long had it been since you set the alarm, and did anything notable occur in between when it was set and when it should have triggered (e.g., did you enable flight mode, did the phone reboot, anything like that)?

Thanks!

( 2016-05-31 11:47:34 +0300 )edit

devel-su systemctl-user status timed-qt5

It says loaded, active(running). Second command also gives warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Also, what time was the alarm set for? How long had it been since you set the alarm

I have a lot of alarms but none of them was active when clock stopped working properly.

did anything notable occur in between when it was set and when it should have triggered (e.g., did you enable flight mode, did the phone reboot, anything like that)?

Reboot is the way how I fix the clock actually ;) AFAIR it always works after reboot. No flight mode, actually nothing specific - it just always stops working after some time since last reboot.

( 2016-05-31 14:45:09 +0300 )edit

~~BTW - devel-su systemctl --user restart timed-qt5 did not fix the problem.~~

Errata: it fixed the problem. I just have to wait some time before alarms starts being visible.

( 2016-05-31 14:47:57 +0300 )edit