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

[Amper]

REPRODUCIBILITY (% or how often): always

BUILD ID = OS VERSION (Settings > About product): 4.4.0.64

HARDWARE (XA2, X10, X10 II, …): XA2

UI LANGUAGE: Russian

REGRESSION: (compared to previous public release: Yes, No, ?):

DESCRIPTION:

previous problem: Phone app do not work

when start phone app tries to load and can be seen on the app grid for two second and then closes. After this the app always closes.

when someone ring, menu for answering a call does not appear

contacts open fine, when try to call from contacts nothing happened

and thats

after rebooting i use in terminal sailjail -p voicecall-ui.desktop /usr/bin/voicecall-ui and thats work fine

after updating phone app do not start from terminal too

browser do not start, android app support do not start, screnshots don“t make, usb with PC do not work, fernshriber works fine

PRECONDITIONS:

nothing

STEPS TO REPRODUCE:

this i see in terminal

[defaultuser@XperiaXA2-DualSIM ~]$ devel-su sfos-upgrade --verify

Password:

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!

Nevertheless, the version for SSU will be set correctly again, later on.

Do you want to continue? (y/N) y

Notice: Do you want to ensure this SailfishOS 4.4.0.64 installation to be complete and up to date? (y/N) y

Notice: For troubleshooting issues with the upgrade proper, please consult

• Stopping osupdate-check.timer

• Setting SSU to SailfishOS release:

Changing release from 4.3.0.15 to 4.4.0.64

Your device is now in release mode!

• Fetching and installing the SailfishOS upgrade from 4.4.0.64 to 4.4.0.64 (this may take a while):

REFRESHING CACHE AND DOWNLOADING PACKAGES

Finished transaction (status=1, runtime=83309ms)

UPGRADING SYSTEM

Finished transaction (status=2, runtime=177ms)

NO UPDATES FOUND. Try again later.

Notice: After rebooting, do not miss to run post_sfos-upgrade

[defaultuser@XperiaXA2-DualSIM ~]$ devel-su post_sfos-upgrade

Password:

Notice: Mind that post_sfos-upgrade is best run on a freshly rebooted device.

• Cleaning logfiles of duplicate entries.

• systemupdate_4.3.0.12-from-4.3.0.12_2022-01-09t21-32-51.log-dupes.txt: O.K.

• systemupdate_4.4.0.64-from-4.4.0.64_2022-05-28t07-45-29.log-dupes.txt: O.K.

Summary: Processed 2 untidy log file(s) in /var/log successfully.

• Removing outdated Store version info.

• Refreshing pkcon’s caches:

Refreshing cache

Starting

Refreshing software list

Finished

• Checking for updates per pkcon:

Getting updates

Finished

Updating packages

Refreshing software list

Starting

Resolving dependencies

Installing updates

Downloading packages

Installing packages

Finished

Fatal error: Subprocess failed. Error: RPM failed: warning: /var/cache/pk-zypp-cache/packages/jolla/non-oss

/noarch/jolla-common-configurations-0.11.3-1.5.1.jolla.noarch.rpm: Header V3 RSA/SHA1 Signature, key ID 473

94f23: NOKEY

error: unpacking of archive failed: cpio: lstat failed - Not a directory

error: jolla-common-configurations-0.11.3-1.5.1.jolla.noarch: install failed

error: jolla-common-configurations-0.11.1.1-1.5.1.jolla.noarch: erase skipped

[defaultuser@XperiaXA2-DualSIM ~]$ devel-su sfos-upgrade --verify

Password:

Notice: Mind that sfos-upgrade is best run on a freshly rebooted device.

Notice: Do you want to ensure this SailfishOS 4.4.0.64 installation to be complete and up to date? (y/N) y

Notice: For troubleshooting issues with the upgrade proper, please consult

• Setting SSU to SailfishOS release:

Changing release from 4.4.0.64 to 4.4.0.64

Your device is now in release mode!

• Fetching and installing the SailfishOS upgrade from 4.4.0.64 to 4.4.0.64 (this may take a while):

REFRESHING CACHE AND DOWNLOADING PACKAGES

Finished transaction (status=1, runtime=51407ms)

UPGRADING SYSTEM

[4 %] [Install] jolla-common-configurations 0.11.3-1.5.1.jolla: [100 %]

Error: Subprocess failed. Error: RPM failed: warning: /var/cache/pk-zypp-cache/packages/jolla/non-oss/noarc

h/jolla-common-configurations-0.11.3-1.5.1.jolla.noarch.rpm: Header V3 RSA/SHA1 Signature, key ID 47394f23:

NOKEY

error: unpacking of archive failed: cpio: lstat failed - Not a directory

error: jolla-common-configurations-0.11.3-1.5.1.jolla.noarch: install failed

error: jolla-common-configurations-0.11.1.1-1.5.1.jolla.noarch: erase skipped

[defaultuser@XperiaXA2-DualSIM ~]$

!
!
!
Try to start phoneapp from terminal:

defaultuser@XperiaXA2-DualSIM ~]$ sailjail -p voicecall-ui.desktop /usr/bin/voicecall-ui

…/daemon/util.c:366: keyfile_load(): E: /etc/sailjail/config/50-sailfish-allowlist.conf: load failed: Key

file contains line ELF???” which is not a key-value pair, group, or comme

nt

constructing /run/firejail/mnt/privileged: Phone,Contacts …

mounting /run/firejail/mnt/privileged @ /home/defaultuser/.local/share/system/privileged

hiding /run/firejail/mnt/privileged

[W] unknown:0 - Could not open /sys/fs/cgroup/memory/noswapping/tasks for disabling caching

[W] unknown:0 - Could not open /sys/fs/cgroup/cpu,cpuacct/interactive/tasks for disabling caching

[D] unknown:0 - Using Wayland-EGL

[F] unknown:0 - QMetaType::registerType: Binary compatibility break – Size mismatch for type 'Notification

Data’ [1995]. Previously registered size 36, now registering size 32.

[defaultuser@XperiaXA2-DualSIM ~]$

EXPECTED RESULT:

ACTUAL RESULT:

ADDITIONAL INFORMATION:

(Please ALWAYS attach relevant data such as logs, screenshots, etc…)

[nephros]

A couple of things from the logs you posted.

1. this:

@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”.

Can you give some more information on the update history of this device? Which version did you flash, and which updates did you do?

2. you have this twice in the log

@Amper

UPGRADING SYSTEM

[4 %] [Install] jolla-common-configurations 0.11.3-1.5.1.jolla: [100 %]

Error: Subprocess failed. Error: RPM failed: warning: /var/cache/pk-zypp-cache/packages/jolla/non-oss/noarc

h/jolla-common-configurations-0.11.3-1.5.1.jolla.noarch.rpm: Header V3 RSA/SHA1 Signature, key ID 47394f23:

NOKEY

error: unpacking of archive failed: cpio: lstat failed - Not a directory

error: jolla-common-configurations-0.11.3-1.5.1.jolla.noarch: install failed

So there’s some indication the update never did finish successfully.
That package contains some critical config files, some of which reference sailjail permissions for voicecall-ui - so this matches the defects you are seeing.

Can you post the output of these commands please?

ssu lr | grep jolla
pkcon resolve jolla-common-configurations
pkcon install jolla-common-configurations --allow-reinstall

file /etc/sailjail/config/50-sailfish-allowlist.conf

[Amper]

thank you for answer!
1.i’m not sure exactly what version i upgraded from, but i did it through the GUI
i think it was 4.3.X.X.
developer unstable updates are disabled
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
before that all fine, i use storeman
before that i reflash phone, because when phone load i see black screen, but recovery mod works fine
before that i use storeman and test version starfish (to pair with asteroid os) from github
phone i buy new in store

2. sorry for twice log

[defaultuser@XperiaXA2-DualSIM ~]$ ssu lr | grep jolla
WARNING: ssu.ini does not seem to be writable. Setting values might not work.

• adaptation-common … https://releases.jolla.com/releases/4.4.0.64/jolla-hw/adaptation-common/armv7hl/
• adaptation0 … https://store-repository.jolla.com/releases/4.4.0.64/jolla-hw/adaptation-qualcomm-
  sony-nile/armv7hl/
• aliendalvik … https://store-repository.jolla.com/features/4.4.0.64/appsupport/armv7hl/
• apps … https://releases.jolla.com/jolla-apps/4.4.0.64/armv7hl/
• customer-jolla … https://releases.jolla.com/features/4.4.0.64/customers/jolla/armv7hl/
• hotfixes … https://releases.jolla.com/releases/4.4.0.64/hotfixes/armv7hl/
• jolla … https://releases.jolla.com/releases/4.4.0.64/jolla/armv7hl/
• sailfish-eas … https://store-repository.jolla.com/features/4.4.0.64/sailfish-eas/armv7hl/
• xt9 … https://store-repository.jolla.com/features/4.4.0.64/xt9/armv7hl/
• store … https://store-repository.jolla.com/h4113/armv7hl/?version=4.4.0.64
  [defaultuser@XperiaXA2-DualSIM ~]$ pkcon resolve jolla-common-configurations
  Сопоставление
  Установлен jolla-common-configurations-0.11.1.1-1.5.1.jolla.noarch (installed) Common configuratio
  n files for all Jolla devices
  Доступен jolla-common-configurations-0.11.3-1.5.1.jolla.noarch (jolla) Common configuration files
  for all Jolla devices
  [defaultuser@XperiaXA2-DualSIM ~]$ pkcon install jolla-common-configurations --allow-reinstall
  Сопоставление
  Проверка изменений
  Завершено
  Установка
  Ожидание аутентификации r all Jolla devices
  Запуск
  Установка пакетов
  Завершено
  Неисправимая ошибка: Subprocess failed. Error: Сбой RPM: warning: /var/cache/pk-zypp-cache/packages/jolla/n
  on-oss/noarch/jolla-common-configurations-0.11.3-1.5.1.jolla.noarch.rpm: Header V3 RSA/SHA1 Signature, key
  ID 47394f23: NOKEY
  error: unpacking of archive failed: cpio: lstat failed - Not a directory
  error: jolla-common-configurations-0.11.3-1.5.1.jolla.noarch: install failed
  error: jolla-common-configurations-0.11.1.1-1.5.1.jolla.noarch: erase skipped

[defaultuser@XperiaXA2-DualSIM ~]$ file /etc/sailjail/config/50-sailfish-allowlist.conf
/etc/sailjail/config/50-sailfish-allowlist.conf: ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV)
, dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=e2017e1647276230d997193902170a263
356c6b2, for GNU/Linux 3.2.0, stripped
[defaultuser@XperiaXA2-DualSIM ~]$

[nephros]

The repositories look fine (the ssu lr output).
The “pkcon resolve” output means you definitely don’t have a properly updated system.
In fact:

[4 %] [Install] jolla-common-configurations 0.11.3-1.5.1.jolla: [100 %]

you probably have a 4% updated system, because the updater failed at that step.

That last one is weird beyond measure - something went seriously wrong somewhere.

Not sure what to recommend from here.

[nephros]

I would:

• delete the zypp-cache (devel-su rm -rf /var/cache/pk-zypp-cache/*)

1. rename the zypp-cache (devel-su mv /var/cache/pk-zypp-cache /var/cache/pk-zypp-cache_old )
2. delete that conf file (devel-su rm /etc/sailjail/config/50-sailfish-allowlist.conf)
3. pkcon refresh
4. and then then try to do the reinstall of that package (devel-su pkcon install jolla-common-configurations --allow-reinstall)
5. and then sfos-update --verify again.

Most important being that that config package installs OK. Don’t try that last part before that isn’t resolved.

[Amper]

config package don’t installs:

defaultuser@XperiaXA2-DualSIM ~]$ devel-su mv /var/cache/pk-zypp-cache /var/cache/pk-zypp-cache_old
Password:
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su mv /var/cache/pk-zypp-cache /var/cache/pk-zypp-cache_old
Password:
Auth failed
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su mv /etc/sailjail/config/50-sailfish-allowlist.conf /etc/sailjai
l/config/50-sailfish-allowlist_old.conf
Password:
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su rm /etc/sailjail/config/50-sailfish-allowlist.conf
Password:
rm: can’t remove ‘/etc/sailjail/config/50-sailfish-allowlist.conf’: No such file or directory
[defaultuser@XperiaXA2-DualSIM ~]$ pkcon refresh
Обновление кэша
Запуск
Обновление списка приложений
Завершено
Неисправимая ошибка: Ошибка загрузки (curl) “https://releases.jolla.com/releases/4.4.0.64/jolla-hw/adaptati
on-common/armv7hl/repodata/repomd.xml”:
Код ошибки: Connection failed
Сообщение об ошибке: Could not resolve host: releases.jolla.com

[defaultuser@XperiaXA2-DualSIM ~]$ pkcon refresh
Обновление кэша
Запуск
Обновление списка приложений
Завершено
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su pkcon install jolla-common-configurations -allow-reinstall
Password:
Не удалось разобрать аргументы командной строки: Unknown option -allow-reinstall
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su pkcon install jolla-common-configurations --allow-reinstall
Password:
Сопоставление
Запрос
Проверка изменений
Завершено
Установка
Запуск ces
Установка пакетов
Завершено
Неисправимая ошибка: Subprocess failed. Error: Сбой RPM: warning: /var/cache/pk-zypp-cache/packages/jolla/n
on-oss/noarch/jolla-common-configurations-0.11.3-1.5.1.jolla.noarch.rpm: Header V3 RSA/SHA1 Signature, key
ID 47394f23: NOKEY
error: unpacking of archive failed: cpio: lstat failed - Not a directory
error: jolla-common-configurations-0.11.3-1.5.1.jolla.noarch: install failed
error: jolla-common-configurations-0.11.1.1-1.5.1.jolla.noarch: erase skipped

[defaultuser@XperiaXA2-DualSIM ~]$ devel-su pkcon install jolla-common-configurations --allow-reinstall
Password:
Сопоставление
Проверка изменений
Завершено
Установка
Запуск ces
Установка пакетов
Завершено
Неисправимая ошибка: Subprocess failed. Error: Сбой RPM: warning: /var/cache/pk-zypp-cache/packages/jolla/n
on-oss/noarch/jolla-common-configurations-0.11.3-1.5.1.jolla.noarch.rpm: Header V3 RSA/SHA1 Signature, key
ID 47394f23: NOKEY
error: unpacking of archive failed: cpio: lstat failed - Not a directory
error: jolla-common-configurations-0.11.3-1.5.1.jolla.noarch: install failed
error: jolla-common-configurations-0.11.1.1-1.5.1.jolla.noarch: erase skipped

[defaultuser@XperiaXA2-DualSIM ~]$

[nephros]

Ok, some files that belong to that package aren’t what they should be.

Please do a

rpm -ql jolla-common-configurations |  xargs file

and

rpm --verify --noscripts  jolla-common-configurations -v

[Amper]

[defaultuser@XperiaXA2-DualSIM ~]$ rpm -ql jolla-common-configurations | xargs file
/etc/hostname: ASCII text
/etc/sailjail-homescreen/allow.d/sailfish-allowlist.conf: cannot open /etc/sailjail-hom escreen/allow.d/sailfish-allowlist.conf' (Not a directory) /etc/sailjail/config/50-sailfish-allowlist.conf: cannot open /etc/sailjail/con
fig/50-sailfish-allowlist.conf’ (No such file or directory)
/etc/zypp/systemCheck.d/jolla-core.check: ELF 32-bit LSB pie executable,
ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, BuildID[sha1]=51ac4
f2bd467d24e41030a207be9c89ce0307408, for GNU/Linux 3.2.0, stripped
/usr/bin/jolla-usersetup: directory
/usr/lib/oneshot.d/hostname-setup: ASCII text
/usr/lib/oneshot.d/remove-fimage-from-fstab: POSIX shell script, ASCII text
executable
/usr/lib/oneshot.d/remove-swap-from-fstab: directory
/usr/lib/systemd/system/home.mount.wants/quota@home.service: cannot open `/usr/lib/systemd/
system/home.mount.wants/quota@home.service’ (No such file or directory)
/usr/lib/systemd/system/sys-brtfs-setup.service: ASCII text
/usr/lib/systemd/system/sysinit.target.wants/sys-brtfs-setup.service: symbolic link to …/sys-brtfs-
setup.service
/usr/lib/systemd/user/jolla-usersetup.service: ASCII text
/usr/lib/systemd/user/pre-user-session.target.wants/jolla-usersetup.service: symbolic link to …/jolla-user
setup.service
/usr/libexec/sys-brtfs-setup: POSIX shell script, ASCII text
executable
/usr/share/dbus-1/system.d/dbus-sailfish-busconfig.conf: exported SGML document, ASCII
text
[defaultuser@XperiaXA2-DualSIM ~]$ rpm --verify --noscripts jolla-common-configurations -v
… g /etc/hostname
missing /etc/sailjail-homescreen/allow.d/sailfish-allowlist.conf (Это не каталог)
missing /etc/sailjail/config/50-sailfish-allowlist.conf
SM5…T. c /etc/zypp/systemCheck.d/jolla-core.check
.M… /usr/bin/jolla-usersetup
SM5…T. /usr/lib/oneshot.d/hostname-setup
S.5…T. /usr/lib/oneshot.d/remove-fimage-from-fstab
.M… /usr/lib/oneshot.d/remove-swap-from-fstab
missing /usr/lib/systemd/system/home.mount.wants/quota@home.service
… /usr/lib/systemd/system/sys-brtfs-setup.service
… /usr/lib/systemd/system/sysinit.target.wants/sys-brtfs-setup.service
… /usr/lib/systemd/user/jolla-usersetup.service
… /usr/lib/systemd/user/pre-user-session.target.wants/jolla-usersetup.service
… /usr/libexec/sys-brtfs-setup
… /usr/share/dbus-1/system.d/dbus-sailfish-busconfig.conf
[defaultuser@XperiaXA2-DualSIM ~]$

[nephros]

@Amper

rpm -ql jolla-common-configurations | xargs file

I can again only shake my head about what went wrong here. This is how it should look:

/etc/hostname:                                                               ASCII text
/etc/sailjail-homescreen/allow.d/sailfish-allowlist.conf:                    ASCII text
/etc/sailjail/config/50-enable-sandboxing.conf:                              ASCII text
/etc/sailjail/config/50-sailfish-allowlist.conf:                             ASCII text
/etc/zypp/systemCheck.d/jolla-core.check:                                    ASCII text
/usr/bin/jolla-usersetup:                                                    POSIX shell script, ASCII text executable
/usr/lib/oneshot.d/hostname-setup:                                           POSIX shell script, ASCII text executable
/usr/lib/oneshot.d/remove-fimage-from-fstab:                                 POSIX shell script, ASCII text executable
/usr/lib/oneshot.d/remove-swap-from-fstab:                                   POSIX shell script, ASCII text executable
/usr/lib/systemd/system/home.mount.wants/quota@home.service:                 symbolic link to ../quota@.service
/usr/lib/systemd/system/sys-brtfs-setup.service:                             ASCII text
/usr/lib/systemd/system/sysinit.target.wants/sys-brtfs-setup.service:        symbolic link to ../sys-brtfs-setup.service
/usr/lib/systemd/user/jolla-usersetup.service:                               ASCII text
/usr/lib/systemd/user/pre-user-session.target.wants/jolla-usersetup.service: symbolic link to ../jolla-usersetup.service
/usr/libexec/sys-brtfs-setup:                                                POSIX shell script, ASCII text executable
/usr/share/dbus-1/system.d/dbus-sailfish-busconfig.conf:                     exported SGML document, ASCII text

So these files are all wrong:

SM5…T. c /etc/zypp/systemCheck.d/jolla-core.check
.M… /usr/bin/jolla-usersetup
SM5…T. /usr/lib/oneshot.d/hostname-setup
S.5…T. /usr/lib/oneshot.d/remove-fimage-from-fstab
.M… /usr/lib/oneshot.d/remove-swap-from-fstab

… and these two are likely the cuplrit why the installation of the updated package fails. It expects to write a new file, but sees a directory and fails.

/usr/bin/jolla-usersetup: directory
/usr/lib/oneshot.d/remove-swap-from-fstab: directory

… so remove these using devel-su rmdir <filename>. If that fails, rename them to _backup or something.

Then we have this

/etc/zypp/systemCheck.d/jolla-core.check

which on your system is a binary when it should be a text file. Not sure what it does, but replace it with a text file with these contents:

requires:glibc
requires:wayland
requires:pulseaudio
requires:PackageKit
requires:mce
requires:dsme
requires:tracker
requires:rpm
requires:shadow-utils
requires:systemd
requires:connman
requires:connectionagent-qt5
requires:ofono
requires:wireless-tools
requires:ssu-vendor-data
requires:jolla-common-configurations

… and then do the pkcon install jolla-common-configurations again.

[Amper]

unfortunately I didn’t succeed
i did some commands twice to make sure the files moved
and did pkcon install jolla-common-configurations twice to make sure it didn’t work
it says: Fatal error: This request will damage your system! (Неисправимая ошибка: Этот запрос повредит вашу систему!)

[defaultuser@XperiaXA2-DualSIM ~]$ devel-su rmdir /usr/bin/jolla-usersetup
Password:
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su rmdir /usr/bin/jolla-usersetup
Password:
rmdir: ‘/usr/bin/jolla-usersetup’: No such file or directory
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su rmdir /usr/lib/oneshot.d/remove-swap-from-fstab
Password:
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su rmdir /usr/lib/oneshot.d/remove-swap-from-fstab
Password:
rmdir: ‘/usr/lib/oneshot.d/remove-swap-from-fstab’: No such file or directory
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su mv /etc/zypp/systemCheck.d/jolla-core.check /etc/zypp/systemChe
ck.d/jolla-core_old.check
Password:
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su mv /etc/zypp/systemCheck.d/jolla-core.check /etc/zypp/systemChe
ck.d/jolla-core_old.check
Password:
mv: can’t rename ‘/etc/zypp/systemCheck.d/jolla-core.check’: No such file or directory
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su mv /home/defaultuser/Downloads/Yottagram/documents/jolla-core.c
heck /etc/zypp/systemCheck.d/jolla-core.check
[defaultuser@XperiaXA2-DualSIM ~]$ pkcon refresh
Обновление кэша
Запуск
Обновление списка приложений
Завершено
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su pkcon install jolla-common-configurations --allow-reinstall
Password:
Сопоставление
Запрос
Проверка изменений
Завершено
Неисправимая ошибка: Этот запрос повредит вашу систему!
[defaultuser@XperiaXA2-DualSIM ~]$ devel-su pkcon install jolla-common-configurations --allow-reinstall
Password:
Сопоставление
Проверка изменений
Завершено
Неисправимая ошибка: Этот запрос повредит вашу систему!
[defaultuser@XperiaXA2-DualSIM ~]$

[nephros]

@Amper

devel-su mv /home/defaultuser/Downloads/Yottagram/documents/jolla-core.check /etc/zypp/systemCheck.d/jolla-core.check

I assume that is where you created that text file and moved it to the right location?

Now, it looks better now, but I don’t know how to bypass that “will break your system” message.

Perhaps

pkcon update jolla-common-configurations --allow-reinstall

will do it.

Anyway, I think you can retry devel-su sfos-upgrade --verify again now.

[Amper]

@nephros

I assume that is where you created that text file and moved it to the right location?

yes, i copy text on laptop to texeditor and move file in yotagramm (fernsriber won’t start)

do i need reboot and try again?

[defaultuser@XperiaXA2-DualSIM ~]$ devel-su sfos-upgrade --verify
Password:
Notice: Battery is charged less than 50% (49%) of its capacity.
Please plug in a charger before continuing.

Notice: Mind that sfos-upgrade is best run on a freshly rebooted device.

Notice: Do you want to ensure this SailfishOS 4.4.0.64 installation to be complete and up to date? (y/N) y

Notice: For troubleshooting issues with the upgrade proper, please consult https://jolla.zendesk.com/hc/en-
us/articles/360005795474

• Stopping osupdate-check.timer

• Setting SSU to SailfishOS release:
  Changing release from 4.4.0.64 to 4.4.0.64
  Your device is now in release mode!

• Fetching and installing the SailfishOS upgrade from 4.4.0.64 to 4.4.0.64 (this may take a while):
  REFRESHING CACHE AND DOWNLOADING PACKAGES
  Resolving: 100%
  Error: This request will break your system!
  Finished transaction (status=2, runtime=63658ms)
  UPGRADE NOT COMPLETE - Retry 1 of 9
  Waiting 1 seconds before retry.
  REFRESHING CACHE AND DOWNLOADING PACKAGES
  Resolving: 100%
  Error: This request will break your system!
  Finished transaction (status=2, runtime=59550ms)
  UPGRADE NOT COMPLETE - Retry 2 of 9
  Waiting 3 seconds before retry.
  REFRESHING CACHE AND DOWNLOADING PACKAGES
  Resolving: 100%
  Error: This request will break your system!
  Finished transaction (status=2, runtime=64809ms)
  UPGRADE NOT COMPLETE - Retry 3 of 9
  Waiting 3 seconds before retry.
  REFRESHING CACHE AND DOWNLOADING PACKAGES
  Resolving: 100%
  Error: This request will break your system!
  Finished transaction (status=2, runtime=60040ms)
  UPGRADE NOT COMPLETE - Retry 4 of 9
  Waiting 5 seconds before retry.
  REFRESHING CACHE AND DOWNLOADING PACKAGES
  Resolving: 100%
  Error: This request will break your system!
  Finished transaction (status=2, runtime=63546ms)
  UPGRADE NOT COMPLETE - Retry 5 of 9
  Waiting 5 seconds before retry.
  REFRESHING CACHE AND DOWNLOADING PACKAGES
  Resolving: 100%
  Error: This request will break your system!
  Finished transaction (status=2, runtime=61357ms)
  UPGRADE NOT COMPLETE - Retry 6 of 9
  Waiting 5 seconds before retry.
  REFRESHING CACHE AND DOWNLOADING PACKAGES
  Resolving: 100%
  Error: This request will break your system!
  Finished transaction (status=2, runtime=59081ms)
  UPGRADE NOT COMPLETE - Retry 7 of 9
  Waiting 10 seconds before retry.
  REFRESHING CACHE AND DOWNLOADING PACKAGES
  Resolving: 100%
  Error: This request will break your system!
  Finished transaction (status=2, runtime=62247ms)
  UPGRADE NOT COMPLETE - Retry 8 of 9
  Waiting 20 seconds before retry.
  REFRESHING CACHE AND DOWNLOADING PACKAGES
  Resolving: 100%
  Error: This request will break your system!
  Finished transaction (status=2, runtime=62223ms)
  UPGRADE NOT COMPLETE - Retry 9 of 9
  Waiting 30 seconds before retry.
  REFRESHING CACHE AND DOWNLOADING PACKAGES
  Resolving: 100%
  Error: This request will break your system!
  Finished transaction (status=2, runtime=65306ms)
  FINISHING

The upgrade could NOT be finished. Make sure you have
a working Internet Connection and SSU is propertly set up. In
case the repos are changing rapidly (e.g. during development),
just restarting the upgrade might fix the issue.

REBOOT AT YOUR OWN RISK.

Notice: After rebooting, do not miss to run post_sfos-upgrade
[defaultuser@XperiaXA2-DualSIM ~]$

[nephros]

Okay, lets do this the forceful way:

mkdir -p ~/tmp
cd ~/tmp
pkcon download ~/tmp/ jolla-common-configurations
devel-su rpm -U --force jolla-common-configurations*.rpm
devel-su sfos-upgrade --verify

[Amper]

it did not help (archive unpacking failed: cpio: lstat failed - This is not a directory)
maybe there is some problem with absence(lack?) encryption key for home directory?
how to enter the encryption key in the terminal? and when?

[defaultuser@XperiaXA2-DualSIM ~]$ mkdir -p ~/tmp
[defaultuser@XperiaXA2-DualSIM ~]$ cd ~/tmp
[defaultuser@XperiaXA2-DualSIM tmp]$ pkcon download ~/tmp/ jolla-common-configurations
Сопоставление
Загрузка пакетов
Запрос
Запуск
Завершено
Загрузка пакетов
Завершено
Загружен jolla-common-configurations-0.11.3-1.5.1.jolla.noarch (jolla) Common configuration files
for all Jolla devices
[defaultuser@XperiaXA2-DualSIM tmp]$ devel-su rpm -U --force jolla-common-configurations*.rpm
Password:
предупреждение: jolla-common-configurations-0.11.3-1.5.1.jolla.noarch.rpm: Заголовок V3 RSA/SHA1 Signature,
key ID 47394f23: NOKEY
ошибка: распаковка архива не удалась: cpio: lstat не удалось - Это не каталог
ошибка: jolla-common-configurations-0.11.3-1.5.1.jolla.noarch: установить не удалось
ошибка: jolla-common-configurations-0.11.1.1-1.5.1.jolla.noarch: стереть пропущено
[defaultuser@XperiaXA2-DualSIM tmp]$ devel-su rpm -U --force jolla-common-configurations*.rpm
Password:
предупреждение: jolla-common-configurations-0.11.3-1.5.1.jolla.noarch.rpm: Заголовок V3 RSA/SHA1 Signature,
key ID 47394f23: NOKEY
ошибка: распаковка архива не удалась: cpio: lstat не удалось - Это не каталог
ошибка: jolla-common-configurations-0.11.3-1.5.1.jolla.noarch: установить не удалось
ошибка: jolla-common-configurations-0.11.1.1-1.5.1.jolla.noarch: стереть пропущено
[defaultuser@XperiaXA2-DualSIM tmp]$ devel-su rpm -U --force jolla-common-configurations.rpm
Password:
ошибка: невозможно открыть jolla-common-configurations.rpm: Нет такого файла или каталога
[defaultuser@XperiaXA2-DualSIM tmp]$

[Sikarjan]

I see the same bug. Once in a while it is not possible to make a call. Entering a number or selecting a contact does nothing. Only a reboot can solve the issue for me.

[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.

[olf]

@Sikarjan

I see the same bug.

No, you don’t.
Do read thoroughly first!

Once in a while it is not possible to make a call. Entering a number or selecting a contact does nothing.

a. This is a 100% reproducible issue, not “once in a while”.
b. Here the phone application and many other Jolla apps cannot be started at the GUI, only via command line.

Only a reboot can solve the issue for me.

A reboot does not “solve” this issue temporarily.

[nephros]

Thanks for chipping in and your insightful analysis.

One thing that might be tried too:

That config file above lists the configuration-common package. Maybe that is where the “will break your system” message is from.

Possibly removing the line from the file will allow rpm -U to proceed…

[olf]

You mean removing
requires:jolla-common-configurations from
/etc/zypp/systemCheck.d/jolla-core.check and then a
pkcon --allow-reinstall update jolla-common-configurations or
rpm -U --force jolla-common-configurations*.rpm ?

This might be worth as a last try going forward before trying my last-resort suggestion to try going backwards (to 4.3.0.15), which may end up in a completely broken SailfishOS installation.

Another idea I had is to install zypper (by pkcon install zypper), read its man-page toroughly and try to resolve the situation with it. Usually zypper handles things better and safer than the low-level tool rpm and provides much more options for fine-tuning than pkcon.

[Sikarjan]

@olf

No, you don’t.

Hi @olf ,

you are right, it did not read carefully enough. For me only the phone app is affected but may be this is somehow connected. If some thinks I can support in finding the issue let me know.

Once in a while I see that even after booting the device it is not possible to make a call. The phone app can be opened and works as expected but no calls can be placed.