This is what a zypper dup give me:
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 ?
it says that it’s going to retrograde 186 package (sailfish one from what it looks like)
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.
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
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.
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)
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
@peterleinchen regarding curl version, I have the same release as you have listed in your post.
@jollajo zypper seems to be fully functioning and happy.
- zypper ref - goes through the repositories and refreshes successfully
- zypper up - says nothing to do, noting 2 apps (fotokopier and whisperfish) will not be installed
- zypper dup - says nothing to do
- zypper update curl - says latest already installed
- zypper update PackageKit - says latest already installed
- zypper update libzypp - says latest already installed
I have looked through @throwaway69 's method, and am trying it now.
2 Likes
If an update hangs in the middle, some packages will be upgraded while others are not. If either PackageKit or libzypp (or rpm, or ssu) don’t all get upgraded together, then there might be linking errors as PackageKit and zypp try to load libs from older or newer packages that they weren’t built against.
If you end up in this state after upgrade, we might be able to find out what caused it to break from the update log, which should be found at /var/log/systemupdate.log
1 Like
The update log is from the update to 4.2.0.19 at the start of September. version --dup doesn’t leave behind a log perhaps.
Thanks for the help.
Okay,
I had something in mind about curl (in another version) pulling in some lib that interfers.
But okay. One possibility less 
@abranson is absolutely right
and maybe take a look at versions of
rpm-4.16.1.3+git4-1.8.1.jolla.armv7hl
and
ssu-1.0.14-1.5.1.jolla.armv7hl
ssu-declarative-1.0.14-1.5.1.jolla.armv7hl
ssu-network-proxy-plugin-1.0.14-1.5.1.jolla.armv7hl
ssu-sysinfo-1.3.0-1.4.1.jolla.armv7hl
ssu-vendor-data-jolla-0.129-1.12.1.jolla.noarch
but after that I am (almost) running out of ideas… 
maybe check also
cat /etc/os-release
Hi,
i have exactly the same Problem.
Failed to load the backend: opening module zypp failed : /usr/lib/libzypp.so.1722: undefined symbol: ZN4YAML15ostream_wrapper5writeERKNSt7_
cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
I had the wrong curl and libcurl Versions from openrepos-lpr.
I fixed this by installing the Jolla Versions.
I checked all other package versions you posted here, they are all good.
I’m really out of idea what the problem is here…
I attached the relevant parts of my systemupdate log here:
Edit:
Btw, i’ve checked my Profile Settings at account.jolla.com and have seen, that Early Access is disabled there? I had this enabled since years and never changed it. I reenabled it now. Could this maybe have something todo with my issue?
I updated manually while using sfos-upgrade app from @olf
Okay, I found my old notes.
And some more stuff to check:
libsolv-0.7.17+git1-1.5.3.jolla.armv7hl
libsolv-tools-0.7.17+git1-1.5.3.jolla.armv7hl
and (most and last chance) probably:
xulrunner-qt5-60.9.1+git61-1.11.6.jolla.armv7hl
For me i have exactly these versions installed and still have the libzypp issue
I also have the issue with PackageKit, on a Xperia 10. I did the upgrade from 4.2 to 4.3 using sfos-upgrade from Openrepos. Everything went fine, except at the end of running post_sfos-upgrade, which ended with this :
- Refreshing pkcon's caches:
Failed to contact PackageKit: Error calling StartServiceByName for org.freedesktop.PackageKit: Failed to activate service 'org.freedesktop.PackageKit': timed out (service_start_timeout=25000ms)
- Checking for updates per 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)
Now PackageKit isn’t running anymore, and complains about libzypp when I try to run the service :
[root@Xperia10-DualSIM 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)
[root@Xperia10-DualSIM nemo]# systemctl start packagekit.service
[root@Xperia10-DualSIM 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. 05 19:11:53 Xperia10-DualSIM systemd[1]: Starting PackageKit Daemon...
nov. 05 19:11:53 Xperia10-DualSIM PackageKit[16693]: daemon start
nov. 05 19:11:53 Xperia10-DualSIM PackageKit[16693]: daemon quit
nov. 05 19:11:53 Xperia10-DualSIM packagekitd[16693]: Failed to load the backend: opening module zypp failed : /usr/lib/libzypp.so.1722: undefined symbol: _ZN4YAML15ostream_wrapper5writeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
nov. 05 19:11:53 Xperia10-DualSIM systemd[1]: Started PackageKit Daemon.
I checked software versions using “zypper pa”, but I don’t see anything abnormal.
My issue was kind of self-inflicted, didn’t assume ‘downloading’ step is what consoles warn you about before start screen: don’t turn off until this icon goes away. Always assumed you had to select ‘install update’ to be in the danger zone (and pretty sure had to reboot at hung downloads before so maybe it is a new issue) where force shutdown/restart is almost guaranteed to cause problems. The libzypp issues seem totally systemic so wouldn’t suggest doing radical rm’s as I did
I had the same issue, installing the libzyp package from 4.2 fixed this for me.
Just set ssu release to 4.2.0.21 do a ‘zypper ref’ and install the libzypp package with zypper using the
–oldversion switch. After installing the package set ssu release back to 4.3 and do zypper ref again. After restarting packagekit service it was working again.
6 Likes
In my experience, ‘downloading’ phase has always been safe(very). Updates often get installed (eventually) and I have never faced a bricked system/device due to any update (since J1). However, almost every time, I (forcefully) interrupt the download process (by restarting, switching network connections… again & again… for several reasons of Jolla’s fault & mine). But eventually, downloading resumes and update gets installed (probably after 4-5 restarts).
1 Like
Thanks, it worked for me too ! 
I confirm these commands resolved the issue :
# ssu re 4.2.0.21
# zypper ref
# zypper in --oldpackage --force libzypp
# ssu re 4.3.0.12
# zypper ref
Now I can see PackageKit running :
[root@Xperia10-DualSIM 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: active (running) since Fri 2021-11-05 21:43:58 CET; 1min 59s ago
Main PID: 30182 (packagekitd)
Memory: 2.1M
CGroup: /system.slice/packagekit.service
└─30182 /usr/libexec/packagekitd
nov. 05 21:43:58 Xperia10-DualSIM systemd[1]: Starting PackageKit Daemon...
nov. 05 21:43:58 Xperia10-DualSIM PackageKit[30182]: daemon start
nov. 05 21:43:58 Xperia10-DualSIM systemd[1]: Started PackageKit Daemon.
7 Likes
Thanks @miau and @N-Mi, I have followed your suggestion of installing libzypp-17.24.2+git1-1.4.2.jolla.armv7hl from 4.2.0.21 and this has allowed PackageKit to be happy again, and thus pkcon and version --dup are now behaving.
I guess obvious with hindsight, but I did a version --dup after changing release back to 4.3.0.12, this reinstalled libzypp-17.26.0+git1-1.6.1.jolla.armv7hl. This broke PackageKit again, and I had to revert back to libzypp from 4.2.0.21.
Thanks @peterleinchen for all the help and package suggestions. I can confirm I have the same versions of all the packages you have listed above, except now, of course, libzypp.
What does this mean? There is at least a handful of systems (on different hardware) that a downgrade of libzypp is required for a stable system. What can be done to identify the problem?
Thanks also @abranson and @jollajo. Very greatful for all the help.
3 Likes
First of all, outstanding work solving the issue and helping the users that are facing the issue!
I did the upgrade using sfos-upgrade and it went fine*, and I’m running libzypp-17.26.0+git1-1.6.1.jolla.aarch64 without issues. So, it’s not the package itself that’s causing the issue, it seems.