Revision history [back]

Well not a question, but just wanting to share.

I noticed that my Jolla 1 has huge uptime:

$ uptime
 18:53:11 up 474 days,  4:45,  2 users,  load average: 0.12, 0.16, 0.36
$ grep PRETTY /etc/os-release
PRETTY_NAME="SailfishOS 2.0.5.6 (Haapajoki) (armv7hl)"

Yup, I have not updated it for very long time. I currently use it just as sound recorder.

The interesting thing I found it that timed stopped responding between 2018-11-03 and 2018-11-06. That is suspiciously close to 1 year since it was started:

$ ps -o lstart -C timed-qt5
                 STARTED
Sat Nov 11 14:08:12 2017

timedclient-qt5 -l freezes and clock shows empty list of timers and alarms.

This might be a peculiar bug, but again it might have been already fixed in subsequent releases.

Any ideas what might be fun to check before I reboot this device?

Well not a question, but just wanting to share.

I noticed that my Jolla 1 has huge whopping uptime:

$ uptime
 18:53:11 up 474 days,  4:45,  2 users,  load average: 0.12, 0.16, 0.36
$ grep PRETTY /etc/os-release
PRETTY_NAME="SailfishOS 2.0.5.6 (Haapajoki) (armv7hl)"

Yup, I have not updated it for very long time. I currently use it just as sound recorder.

The interesting thing I found it that timed stopped responding between 2018-11-03 and 2018-11-06. That is suspiciously close to 1 year since it was started:

$ ps -o lstart -C timed-qt5
                 STARTED
Sat Nov 11 14:08:12 2017

timedclient-qt5 -l freezes and clock shows empty list of timers and alarms.

This might be a peculiar bug, but again it might have been already fixed in subsequent releases.

Any ideas what might be fun to check before I reboot this device?