I had an interrupted download which probably explains why I had a similar problem.
While @wetab73 correctly denoted …
… this may also happen at any other time, when a new SailfishOS release is available, see:
To avoid any mishaps (by mistyping or mis-guessing the truly installed SailfishOS release) one may use (as described in the bug report) to bring the SailfishOS installation into a consistent state again:
devel-sussu re "$(grep -F VERSION_ID /etc/os-release | cut -s -f 2 -d "=")"rm -f /var/cache/ssu/features.inissu ur
Then either run post_sfos-upgrade (if sfos-upgrade is installed),
or manually execute the “Final clean up steps” (specifically killing the store-client followed by removing its cached SailfishOS upgrade release version info),
plus a zypper ref (if zypper is installed)
and a pkcon refresh (i.e., always when doing this manually instead of using post_sfos-upgrade).
3 Likes
Wow, what a nasty bug! I have never experienced it myself before yesterday.
Luckily, I quickly reacted and only ofono got broken, which I then replaced with the right version. But as can be seen from other posts in this thread, for other people it had much worse consequences… It’s hard to believe that Jolla hasn’t fixed such an awful bug for so long…
From now on, with every new OS update discovered, I will always check if it didn’t mess with it again.
1 Like
I one reads this forum regularly, simply switching off the osupdate-check as described in “Workaround b.” is the appropriate solution IMO (until Jolla has fixed this issue). I definitely do not need any update-reminder (rather the contrary).
1 Like
Very good suggestion! Done.