Saved Alarms and Timers Disappearing After Reboot

Bug Reports
13

Happened again now.

  1. Device had relatively long uptime (Two weeks or so)
  2. Shutdown was triggered by running out of power
  3. Therefore, plugging in a charger cable booted up to ‘charging’ screen (is that ‘actdead’)?
  4. After a bit of charging, boot to proper mode

Can it be that charging screen has e.g. timed running but home not mounted so it can’t read/write alarms?

Is a boot from charging screen to proper OS a real reboot, or does booting continue from charge screen?

Theory being that timed is initialized with empty config, and later writes that to the data file once it becomes writable?

I that theory holds, maybe all that’s needed is something like a RequireMountsFor dependency in the systemd unit file.

Edit: Also, I notice that jolla-usersetup service was reported as failed. That one is a dependency of pre-user-session.target which is the one that the timed service has a ‘WantedBy’ dep on.
Not sure if related, but maybe that target isn’t reached in proper time?

4 Likes