Phone app, and many other app do not work after update to 4.4.0.64

[olf]

@nephros

@Amper

Warning: The installed version 4.4.0.64 is greater than the one currently set for SSU (4.3.0.15).

This is quite unusual!

Indeed. One thing is that 4.3.0.15 → 4.4.0.64 is not a usual update path - most people would have gone through 4.4.0.58 first. though it is not clear from the official release notes if both 4.4 releases have been “Stop releases”.

I stumbled across this ambiguity, too. But I ultimately decided that it does not make much sense to handle both, 4.4.0.58 and 4.4.0.64 as stop releases.

Reasons:

1. The release notes for SailfishOS 4.4.0 use singular (“is”) and only mention 4.4.0 (i.e., without a point release number):

   Yes, 4.4.0 is a stop release.

   – Is 4.4.0 also a stop release?
   – Yes. We will switch the rpm compression from xz to zstd on 4.5.0. As the prerequisite, we have enabled zstd in deltarpm and related tools in the 4.4.0 release.

2. The technical reason (enabling zstd compression) also indicates that only the latest point release of 4.4.0 should be treated as a stop release.
3. This is how it has been for 4.3.0.12 / 4.3.0.15: Now only 4.3.0.15 is listed as a stop release.
4. The GUI updater took @Amper’s device from 4.3.0.xx to 4.4.0.64. He only used sfos-upgrade --verify with 4.3.0.12 installed on 2022-01-09t21-32-51 (but missed to run post_sfos-upgrade thereafter), again with 4.4.0.64 installed on 2022-05-28t07-45-29, and then a couple of times when trying to resolve this issue.

But OTOH, the list of stop releases currently only lists 4.4.0.58 as a stop release, but does not mention 4.4.0.64 at all. I attributed that to negligent maintenance of this document (as often before) and posed a PR to fix it, but may be wrong. It would be helpful, if @jovirkku can check and clarify.

Obviously the SailfishOS upgrade triggered by version --dup never proceeded further than 4% (but /etc/os-release apparently was among these 4%), always failing when trying update from jolla-common-configurations-0.11.1.1-1.5.1.jolla.noarch (in 4.3.0) to jolla-common-configurations-0.11.3-1.5.1.jolla.noarch (in 4.4.0).

@Amper

I updated on May 28
before that i have broken phone app and launch it from terminal
one update i do with this bug
before that i try to solve bug with phone and turn on developer mod

@Amper, on lesson from this unfortunate experience might be: Do not upgrade SailfishOS, when there is something severely wrong with SailfishOS or Jolla’s core apps (which are updated by SailfishOS upgrades). Try to fix the issue first. Side note: Third party apps from OpenRepos (via Storeman) or SailfishOS:Chum usually do not matter, although sometimes they also may indicate an SailfishOS malfunction.

Sadly I have no idea what to try beyond all the analysis and actions @nephros has suggested and you have executed.

When you consider to re-flash again (SailfishOS 4.4.0.64 this time), you may try as a last resort:

• devel-su
ssu re 4.3.0.15
• Check if the GUI updater works: Likely it will not offer you to download the update to 4.4.0.64.
• sfos-upgrade # without a parameter
  It will warn you about a downgrade: Tell it to ignore that. It still may refuse that, because the downgrade is across a stop release (i don’t exactly remember how it is currently implemented). If so, you can manually issue an version --dup instead.

Note that this action may make your current SailfishOS installation unbootable, but flashing SailfishOS again will work.