Problems with installing the OS update 4.3.0

juz · 5 November 2021 10:08

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

abranson · 5 November 2021 10:32

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

juz · 5 November 2021 10:51

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.

peterleinchen · 5 November 2021 11:51

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

jayki · 5 November 2021 13:06

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

peterleinchen · 5 November 2021 15:48

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

jayki · 5 November 2021 16:26

For me i have exactly these versions installed and still have the libzypp issue

N-Mi · 5 November 2021 18:17

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.

throwaway69 · 5 November 2021 18:18

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

miau · 5 November 2021 19:21

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.

babo · 5 November 2021 19:37

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

N-Mi · 5 November 2021 20:53

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.

juz · 6 November 2021 03:40

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.

direc85 · 6 November 2021 08:53

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.

abranson · 6 November 2021 08:56

That’s really strange, and makes me think that something’s blocked the upgrade of PackageKit or one of its components. What version number do you see for PackageKit and PackageKit-zypp? If they’re still on the 4.2 version ( 1.1.13+git14-1.3.2 instead of 1.1.13+git14-1.4.1) then you could try upgrading those (and of course libzypp) with zypper up. If you get an error from that, then that might explain why these upgrades are failing.

juz · 6 November 2021 10:04

Hi @abranson, thanks for continuing to think about it.
I can confirm on my xperia X it seems I have the 4.3 version of both PackageKit and PackageKit-zypp. I have the following installed:

Name : PackageKit
Version : 1.1.13+git14-1.4.1.jolla

and

Name : PackageKit
Version : 1.1.13+git14-1.4.1.jolla

peterleinchen · 6 November 2021 10:08

Indeed, really really strange.

Also as downgrading libzypp seems to not argue about any other package to be downgraded!

But re-reading the error output it came to my mind!!!

What about the YAML-cpp package? :facepalm:
yaml-cpp-0.6.3+git1-1.5.1
against 0.6.3+git1-1.4.2 from 4.2.0.21

I guess it is up-to-date with 0.6.3+git-1.5.1 as version --dup did not find anything to update?

Please do a
grep -ilr _ZN4YAML15ostream_wrapper5writeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE /usr/lib/
and see libyaml-cpp.so to be found.

If you now have current version of yaml-cpp package and this symbol then something is really really really strange.
And this must not happen!

If all above is right then “update” yaml-cpp with ssu re 4.3.0.12 and zipper in -f --oldpackage to get the “same” newer package reinstalled and see if that helps.

juz · 6 November 2021 10:39

@peterleinchen This seems to be the golden ticket.
I do not have yaml-cpp installed - no version.
Following, the grep command returned grep: /usr/lib/xulrunner-qt5-60.9.1/dictionaries: No such file or directory
Is the answer to install yaml-cpp and return libzypp to 4.3 version?
Is there a right order to do this?

Should this have been pulled in automatically? Why not on my system? Why is everything happy with the older libzypp package?

Thanks again,

peterleinchen · 6 November 2021 10:54

Oh wow.
Did not expect this!

With the old libzypp package installed please tell us what
zipper info --requires libzypp tells you.

Is there a dependency to yaml-cpp?

If not go ahead to newest stuff and installing yaml-cpp

If there is I do not know what is going on with dependency resolution (but would go above way as well). As in 4.3 there is a dependency of libzypp to yaml-cpp.

juz · 6 November 2021 11:15

Hi @peterleinchen,
I have pasted the output from zypper info --requires libzypp here:

There is no mention of yaml-cpp, but there is mention of libyaml-cpp.
Following, an attempt to zypper in yaml-cpp resulted in a conflict, but then a weird result when I check if the conflicting package (libyaml-cpp) is installed. Is this due to repos being refreshed to 4.3?
Should I proceed with the install?

root@Sailfish nemo]# zypper in yaml-cpp

Loading repository data…
Reading installed packages…
Resolving package dependencies…

The following NEW package is going to be installed:
yaml-cpp

1 new package to install.
Overall download size: 0 B. Already cached: 127.1 KiB. After the
operation, additional 127.1 KiB will be used.
Continue? [y/n/v/…? shows all options] (y): y
In cache yaml-cpp-0.6.3+git1-1.5.1.jolla.armv7hl.rpm
(1/1), 127.1 KiB (127.1 KiB unpacked)

Checking for file conflicts: …[error]
Detected 1 file conflict:

File /usr/lib/libyaml-cpp.so.0.6
from install of
yaml-cpp-0.6.3+git1-1.5.1.jolla.armv7hl (jolla)
conflicts with file from package
libyaml-cpp0_6-0.6.2+master.20181213083542.4d61e32-1.3.3.jolla.armv7hl (@System)

File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
Continue? [yes/no] (no): n

Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
History:
- ABORT request:

Please see the above error message for a hint.
[root@Sailfish nemo]# zypper info libyaml-cpp
Loading repository data…
Reading installed packages…

package 'libyaml-cpp' not found.
[root@Sailfish nemo]# rpm -q libyaml-cpp
package libyaml-cpp is not installed

I assume proceed with the install of yaml-cpp?