Revision history [back]
 | 1 | initial version | posted 2018-09-14 12:18:08 +0200  |
[bug] alarm clock stays silent and can't be switched off at the same time
Today I overlept for 3 hours because the alarm on my Jolla1 went off, but didn't emit any alarm sound:
The device was switched on and the alarm UI was displayed. But trying to dismiss the alarm using the lower pulley menu entry didn't do anything, the alarm UI just stayed there in foreground silently.
No alarm sound was played though.
This issue isn't really reproducible, because it went away after a reboot. But I attached the journald log as it contains multiple suspicious entries like Sep 14 10:57:56 Sailfish timed-qt5[1236]: ERROR: Voland call 'create' failed, message: '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.'
Sep 14 10:57:56 Sailfish mce[591]: tklock.c: tklock_datapipe_uiexception_type_cb(): uiexception_type = none -> alarm
.
I hope you can take a look at this issue, because an alarm clock which doesn't work reliably is worthless.
I'm running Sailfish OS 2.2.1.18
| | 2 | No.2 Revision |
[bug] alarm clock stays silent and can't be switched off at the same time
Today I overlept for 3 hours because the alarm on my Jolla1 went off, but didn't emit any alarm sound:
The device was switched on and the alarm UI was displayed. But trying to dismiss the alarm using the lower pulley menu entry didn't do anything, the alarm UI just stayed there in foreground silently.
No alarm sound was played though.
This issue isn't really reproducible, because it went away after a reboot. But I attached the journald log as it contains multiple suspicious entries like Sep 14 10:57:56 Sailfish timed-qt5[1236]: ERROR: Voland call 'create' failed, message: '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.'
Sep 14 10:57:56 Sailfish mce[591]: tklock.c: tklock_datapipe_uiexception_type_cb(): uiexception_type = none -> alarm
.
journald log ending during the time the bug appears
I hope you can take a look at this issue, because an alarm clock which doesn't work reliably is worthless.
I'm running Sailfish OS 2.2.1.18