Problems with installing the OS update 4.3.0

Announcements
#1

Hi all,
I am needing some suggestions. I started an upgrade this morning (via terminal) and not long after my phone become unresponsive. I left it running for 10+ hours. I have since restarted, and some things seem ok, but I think some things are broken. The phone boots, and many things seem to be working correctly. Settings>About reports the OS version as 4.3.0.12
Jolla store reports no apps installed, and pkcon and version --dup fail to run. Both complain about PackageKit.

[root@Sailfish nemo]# pkcon
Failed to contact PackageKit: Error calling StartServiceByName for org.freedesktop.PackageKit: Failed to activate service ‘org.freedesktop.PackageKit’: timed out (service_start_timeout=25000ms)

[root@Sailfish nemo]# systemctl status packagekit.service
● packagekit.service - PackageKit Daemon
Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/packagekit.service.d
└─01-home-mount.conf, 01-prevent-start.conf
Active: inactive (dead)
Nov 04 21:00:12 Sailfish systemd[1]: Starting PackageKit Daemon

Nov 04 21:00:12 Sailfish PackageKit[6163]: daemon start
Nov 04 21:00:12 Sailfish PackageKit[6163]: daemon quit
Nov 04 21:00:12 Sailfish packagekitd[6163]: Failed to load the backend: opening module zypp failed : /usr/lib/libzypp.s
o.1722: undefined symbol: _ZN4YAML15ostream_wrapper5writeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
Nov 04 21:00:12 Sailfish systemd[1]: Started PackageKit Daemon.
Nov 04 21:14:20 Sailfish systemd[1]: Starting PackageKit Daemon

Nov 04 21:14:20 Sailfish PackageKit[6850]: daemon start
Nov 04 21:14:20 Sailfish PackageKit[6850]: daemon quit
Nov 04 21:14:20 Sailfish packagekitd[6850]: Failed to load the backend: opening module zypp failed : /usr/lib/libzypp.s
o.1722: undefined symbol: _ZN4YAML15ostream_wrapper5writeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
Nov 04 21:14:20 Sailfish systemd[1]: Started PackageKit Daemon.

Any suggestions on how to get the update to finish, and for everything to be as it should?
Thanks so much,
Justin.

[Release notes] Suomenlinna 4.3.0
[4.3.0.12] Jolla camera (also torch) does not start at all - as well as videos do not play
Unstability of OS upgrades (on CLI)
[Wiki] Common problems with SFOS OTA upgrades (updates)
[Release notes] Suomenlinna 4.3.0
#2

hm, seem that package kit tries to use libzypp which seems to be broken.
I’d try to manually download and install PackageKit-zypp-1.1.13+git14-1.4.1.jolla.armv7hl and libzypp-17.26.0+git1-1.6.1.jolla.armv7hl.
Both are installed on my XA2. Note this is for arm7, ie. 32 bit, if you’re on 64 bits use the correct package. Unfortunately I’m not sure where to get the packages from.

Have a look here: (for the 32bit variants)
https://releases.jolla.com/releases/4.3.0.12/jolla/armv7hl/repodata/repomd.xml

#3

Looks like this is a common error on upgrading!

Reported here now twice and on all other upgrades, happened to me as well similarly.

Some borked up mix between old and new versions of pkcon, PackageKit, PackageKit-zypp, libzypp and zypper packages. You need to search this forum and also TJC to find some hints, it will be finding out current versions installed, find needed versions of new OS release, manually download newer packages, transfer to device and install and so on
 (maybe a simple symlinking or copying of one lib to other location may suffice, iirc from other topic?)

I definitely would like to see a Zendesk article regarding this topic! @Jolla?

2 Likes
#4

Thanks Jollajo. I meant to say it is Xperia X - so 32 bit.
I will search for that package and try and install as mentioned.
Thanks very much.

1 Like
#5

Thanks peterleinchen,
I have been trawling the forum, and have found a few things, though nothing that I have managed to make work yet. I had no suitable packages in cache. Will search as per jollajo suggestion.
Thanks so much,

#6

Maybe. But such an article would require artificial intelligence, I am afraid of. :grinning:

There should not be any issues with PackageKit if the OS releases are upgraded using the phone UI instead of doing it at the command line. Our tests have passed flawlessly, and they are many.

One reason for the problems could be that since all of the Sailfish 4 releases, so far, have been Stop Releases, it could be that some users have not traversed all releases when upgrading their devices with “version --dup”. There are probably other reasons, too.

Before an article can be written, the whole problem chain should be understood.

Let’s try to find out what takes the system to such a fragile state.

4 Likes
Unstability of OS upgrades (on CLI)
#7

Yes, I agree. Some AI would be nice to find what exactly is borked up :wink:

But maybe just a simple lesson how to find out which versions one have installed still, which version one should have according to repodata primary XML gz file (how to get to this listing and analyze!), How to extract the correct url for your packages and download and install.

That should do the trick here and most of other occurrences, or?
At least it would be a starting point for further analysis and resolution findings.

It happened quite often, at least I read about it (as I was personally attracted by it).
And it was always a mix up of packages like
pkcon
PackageKit
PackageKit-zypp
libzypp
(zipper)


Maybe ssu

#8

Hi @jollajo ,
I have tried to follow your suggestions.
I downloaded repo data from:
https://releases.jolla.com/releases/4.3.0.12/jolla/armv7hl/repodata/291c3ba847217d4db39b8bd73baee748409d77f7f06a63518cd6e3527b002ad7-primary.xml.gz
A search for your suggested packages seemed to suggest the following URLs:

  1. https://releases.jolla.com/releases/4.3.0.12/oss/armv7hl/libzypp-17.26.0+git1-1.6.1.jolla.armv7hl.rpm

  2. https://releases.jolla.com/releases/4.3.0.12/oss/armv7hl/PackageKit-zypp-1.1.13+git14-1.4.1.jolla.armv7hl.rpm

I used “curl -O TheAboveURL’s”, however that doesn’t seem to have been correct. A file has been created, however, it is essentially empty.

Attempting to install using “rpm -Uvh ________” doesn’t work as the rpm package is not right.

Any suggestions on the correct process?

Thanks all.

#9

Nope, I updated with the GUI. I tried running version --dup but there was nothing to do. Then I tried installing anyway. There was a message that update cannot be done. I rebooted the phone, downloaded the package again and got the same warnings about git packages. Tried the update anyway and this time it gave the same warnings but the update was succesful. I run the version --dup once more but it did not find anything to do.

#10

Thanks for that hot tip - I had wondered about that. This has allowed me to download the packages!
However, on install it was reported that both packages where already installed.
So I tried “rpm -Uvh --replacepkgs _____________” This installed the packages.
Following a reboot there is no change in behavior.
pkcon reports the same error. systemctl status packagekit.service reports the same error.
I feel this is out of me reach. A reflash might be required :frowning:
Thanks for all the help.

#11

What a shame,
don’t give up too quickly, I was close to it yesterday as well, however as long as you manage to login to your phone there should be a way to fix it.

You should try to find why packagekit fails.
The service file /usr/lib/systemd/system/packagekit.service mentions some options for debugging:

# To enable verbose logging define following in sysconfig file:
# PACKAGEKIT_ARGS="--keep-environment --verbose"
# ZYPP_LOGFILE=-

I’d uncomment those lines and restart the service. I guess you don’t need to reboot, if you restart the service by systemctl restart packagekit should do the job, I’m just not sure if the modified file will be read without asking systemd to rescan the files.

Actually shouldn’t we move this discussion into a new thread, to stop polluting this one here?

#12

Yes, do not give up too early.
As long as you can log in (even only via ssh) there is hope :wink:

What does
ldd /usr/lib/libzypp.so.1722 tell you?
Some other lib missing or wrong symbols (wrong package version)?

1 Like
#13

And another yes, our posts should be extracted into a distinct thread.
But we cannot do this. @jovirkku?

1 Like
[Release notes] Suomenlinna 4.3.0
#14

I am trying to install the update, but it’s saying that all my packages are blocking

Capture d'Ă©cran_20211104_001
Capture d'Ă©cran_20211104_0011080×2520 615 KB

Capture d'Ă©cran_20211104_002
Capture d'Ă©cran_20211104_0021080×2520 527 KB

there is way more packages

Should I try installing anyway ?

Upgrade to 4.3.0.12 Unstable Internet Connection - No Help From Jolla
#15

This is what a zypper dup give me:

Capture d'Ă©cran_20211104_005
Capture d'Ă©cran_20211104_0051080×2520 624 KB

it says that it’s going to retrograde 186 package (sailfish one from what it looks like)

I guess I should reflash with the latest version ?

#16

Thanks for the continued help. It would be great to have this topic separated, is there anything I can do? Should I start a new one?

@peterleinchen I tried your suggestion and there are no alarm bells there. Though there is one different line. /lib/ld-linux-armhf.so.3 (0xaaebe000) is different to all the others. Is this the way it should be?

[root@Sailfish nemo]# ldd /usr/lib/libzypp.so.1722
libutil.so.1 => /lib/libutil.so.1 (0xf6dec000)
librpm.so.9 => /usr/lib/librpm.so.9 (0xf6d93000)
libcurl.so.4 => /usr/lib/libcurl.so.4 (0xf6d2d000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0xf6c42000)
libz.so.1 => /usr/lib/libz.so.1 (0xf6c19000)
libsolv.so.1 => /usr/lib/libsolv.so.1 (0xf6bab000)
libsolvext.so.1 => /usr/lib/libsolvext.so.1 (0xf6b77000)
libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0xf69b0000)
libboost_thread-mt.so.1.66.0 => /usr/lib/libboost_thread-mt.so.1.66.0 (0xf6955000)
libgpgme-pthread.so.11 => /usr/lib/libgpgme-pthread.so.11 (0xf6924000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf68fd000)
libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0xf68e6000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xf67f7000)
libyaml-cpp.so.0.6 => /usr/lib/libyaml-cpp.so.0.6 (0xf6793000)
libudev.so.1 => /usr/lib/libudev.so.1 (0xf676a000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xf6658000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf663f000)
libc.so.6 => /lib/libc.so.6 (0xf6526000)
/lib/ld-linux-armhf.so.3 (0xaaebe000)
librpmio.so.9 => /usr/lib/librpmio.so.9 (0xf64f5000)
libbz2.so.1 => /usr/lib/libbz2.so.1 (0xf64d9000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0xf64af000)
liblua-5.3.so => /usr/lib/liblua-5.3.so (0xf647d000)
libm.so.6 => /lib/libm.so.6 (0xf6411000)
libpopt.so.0 => /usr/lib/libpopt.so.0 (0xf63f8000)
libcap.so.2 => /usr/lib/libcap.so.2 (0xf63e4000)
libdb-4.8.so => /usr/lib/libdb-4.8.so (0xf62ed000)
libdl.so.2 => /lib/libdl.so.2 (0xf62d9000)
libnghttp2.so.14 => /usr/lib/libnghttp2.so.14 (0xf62ae000)
libpsl.so => /usr/lib/libpsl.so (0xf629a000)
libssl.so.1.1 => /usr/lib/libssl.so.1.1 (0xf6234000)
libboost_system-mt.so.1.66.0 => /usr/lib/libboost_system-mt.so.1.66.0 (0xf621f000)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0xf6200000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0xf61a0000)
libmount.so.1 => /usr/lib/libmount.so.1 (0xf6154000)
libblkid.so.1 => /usr/lib/libblkid.so.1 (0xf610f000)
libuuid.so.1 => /usr/lib/libuuid.so.1 (0xf60f9000)
librt.so.1 => /lib/librt.so.1 (0xf60e3000)

@jollajo, I uncommented the lines you suggested, and restarted service. I think I might need to do more than that. It resulted in the following:

[root@Sailfish nemo]# systemctl status packagekit
● packagekit.service - PackageKit Daemon
   Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static; vendor preset: enabled)
  Drop-In: /usr/lib/systemd/system/packagekit.service.d
           └─01-home-mount.conf, 01-prevent-start.conf
   Active: inactive (dead)

Nov 05 05:58:14 Sailfish systemd[1]: Started PackageKit Daemon.
Nov 05 06:05:50 Sailfish systemd[1]: /usr/lib/systemd/system/packagekit.service:13: Unknow
n lvalue 'PACKAGEKIT_ARGS' in section 'Service'
Nov 05 06:05:50 Sailfish systemd[1]: /usr/lib/systemd/system/packagekit.service:14: Unknow
n lvalue 'ZYPP_LOGFILE' in section 'Service'
Nov 05 06:05:50 Sailfish systemd[1]: Starting PackageKit Daemon...
Nov 05 06:05:50 Sailfish PackageKit[12911]: daemon start
Nov 05 06:05:50 Sailfish PackageKit[12911]: daemon quit
Nov 05 06:05:50 Sailfish packagekitd[12911]: Failed to load the backend: opening module zypp failed : /usr/lib/lib
zypp.so.1722: undefined symbol: _ZN4YAML15ostream_wrapper5writeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaI
cEEE
Nov 05 06:05:50 Sailfish systemd[1]: Started PackageKit Daemon.
Nov 05 06:06:04 Sailfish systemd[1]: /usr/lib/systemd/system/packagekit.service:13: Unknow
n lvalue 'PACKAGEKIT_ARGS' in section 'Service'
Nov 05 06:06:04 Sailfish systemd[1]: /usr/lib/systemd/system/packagekit.service:14: Unknow
n lvalue 'ZYPP_LOGFILE' in section 'Service'

Thanks again for the help. Slow replies due to sleep, and now off to work. All very much appreciated though. Sorry for convoluting this thread further.

#17

I had this endless list as well. Something was messed up. A version --dup followed by a shutdown -r now solved it for me.

1 Like
#18

I would suggest you just start a new thread with the key information copied from here with a reference to this thread.

There are a few differences to my output of ldd but it doesn’t seem to be significant.
You’re right your variables in the service file seem to need more info. The Zypp-Logfile probalby needs a location where to write the log to.

Actually does zypper run on your phone? That also uses libzypp.

#19

Looks auite similar but some libs different:
the one abiut ld-linux is normal

But something came to my mind, what version is curl? curl-7.78.0+git1-1.6.1.jolla.armv7hl?

ldd /usr/lib/libzypp.so.1722
/usr/lib/libpreloadpatchmanager.so (0xf6f5e000)
libutil.so.1 => /lib/libutil.so.1 (0xf6f40000)
librpm.so.9 => /usr/lib/librpm.so.9 (0xf6ee7000)
libcurl.so.4 => /usr/lib/libcurl.so.4 (0xf6e81000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0xf6d96000)
libz.so.1 => /usr/lib/libz.so.1 (0xf6d6d000)
libsolv.so.1 => /usr/lib/libsolv.so.1 (0xf6cff000)
libsolvext.so.1 => /usr/lib/libsolvext.so.1 (0xf6ccb000)
libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0xf6b04000)
libboost_thread-mt.so.1.66.0 => /usr/lib/libboost_thread-mt.so.1.66.0 (0xf6aa90
00)
libgpgme-pthread.so.11 => /usr/lib/libgpgme-pthread.so.11 (0xf6a78000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf6a4f000)
libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0xf6a3a000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xf694b000)
libyaml-cpp.so.0.6 => /usr/lib/libyaml-cpp.so.0.6 (0xf68f4000)
libudev.so.1 => /usr/lib/libudev.so.1 (0xf68cb000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xf67b9000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf67a0000)libc.so.6 => /lib/libc.so.6 (0xf6687000)
/lib/ld-linux-armhf.so.3 (0xab201000)
libdl.so.2 => /lib/libdl.so.2 (0xf6673000)
libm.so.6 => /lib/libm.so.6 (0xf6609000)
librpmio.so.9 => /usr/lib/librpmio.so.9 (0xf65d8000)
libbz2.so.1 => /usr/lib/libbz2.so.1 (0xf65ba000)
liblzma.so.5 => /usr/lib/liblzma.so.5 (0xf6590000)
liblua-5.3.so => /usr/lib/liblua-5.3.so (0xf655e000)
libpopt.so.0 => /usr/lib/libpopt.so.0 (0xf6545000)
libcap.so.2 => /usr/lib/libcap.so.2 (0xf6531000)
libdb-4.8.so => /usr/lib/libdb-4.8.so (0xf643a000)
libnghttp2.so.14 => /usr/lib/libnghttp2.so.14 (0xf640f000)
libpsl.so => /usr/lib/libpsl.so (0xf63fb000)
libssl.so.1.1 => /usr/lib/libssl.so.1.1 (0xf6395000)
libboost_system-mt.so.1.66.0 => /usr/lib/libboost_system-mt.so.1.66.0 (0xf63800
00)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0xf635f000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0xf6301000)
libmount.so.1 => /usr/lib/libmount.so.1 (0xf62b5000)

#20

Actually, is the issue in that thread related to yours? Bricked zypper and pkcon from restarting during hung 4.3 download
Maybe @throwaway69 's findings help you as well.

1 Like
Xperia X hangs on boot after upgrade to [4.3.0.12]