[Ubuntu22.04] systemd-coredump package not installable via apt install when only OpenSSL 3.0 is available on the system (s390x)

[bugproxy]

---Problem Description---
Summary
=======
IBM z16 LPAR (s390x architecture)
OS: Ubuntu 20.04.1 LTS (jammy jellyfish) on 5.15.0-53-generic,
    openssl 3.0.2-0ubuntu1.7 s390x
    systemd 249.11-0ubuntu3.6 s390x
The problem is immediately reproducible.

Details
=======
We fail to install the systemd-coredump package on a system where only OpenSSL 3.0.2 is available.

Terminal output
===============
# apt info systemd-coredump
Package: systemd-coredump
Version: 249.11-0ubuntu3.6
Priority: optional
Section: universe/admin
Source: systemd
Origin: Ubuntu
Maintainer: Ubuntu Developers <email address hidden>
Original-Maintainer: Debian systemd Maintainers <email address hidden>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 337 kB
Provides: core-dump-handler
Depends: libc6 (>= 2.34), libdw1 (>= 0.158), libelf1 (>= 0.144), systemd (= 249.11-0ubuntu3.6), adduser
Conflicts: core-dump-handler
Replaces: core-dump-handler
Homepage: https://www.freedesktop.org/wiki/Software/systemd
Download-Size: 56.6 kB
APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe s390x Packages
Description: tools for storing and retrieving coredumps
 This package provides systemd tools for storing and retrieving coredumps:
  * systemd-coredump
  * coredumpctl

N: There is 1 additional record. Please use the '-a' switch to see it

# apt-get install systemd-coredump
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 apport : Conflicts: core-dump-handler
 libep11 : Depends: libssl1.0.0 but it is not installable or
                    libssl1.1 but it is not installable
 systemd-coredump : Depends: libdw1 (>= 0.158) but it is not going to be installed
                    Conflicts: core-dump-handler
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

Contact Information = <email address hidden>

---uname output---
Linux system 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:54:41 UTC 2022 s390x s390x s390x GNU/Linux

Machine Type = IBM Type: 3931 Model: 704 A01

---Debugger---
A debugger is not configured

---Steps to Reproduce---
1.) Configure the apt repos as shown in the attached sources.list file and run
    apt-get update
2.) Run: apt install systemd-coredump
There is no package install available working with openssl version 3.0.N alone
i.e. when openssl 1.0 or 1.1 are _NOT_ installed

Userspace tool common name: coredumpctl

The userspace tool has the following bit modes: 64-bit

Userspace rpm: systemd-coredump

Userspace tool obtained from project website: na

*Additional Instructions for <email address hidden>:
-Attach ltrace and strace of userspace application.

[bugproxy (bugproxy)]

Default Comment by Bridge

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2022-11-23 11:34 EDT-------
Ubuntu 22.04.1 LTS : sorry for the typo above

[Frank Heimes (fheimes)]

Hi Christian,
it looks to me that your system is package-wise not up to date.

Have you done an
apt update
before you started the installation (to update the package index)?

On my jammy system (that is up to date, with:
sudo apt update && sudo apt full-upgrade)

I have a 'libssl1.1':
$ apt-cache policy libssl1.1
libssl1.1:
  Installed: 1.1.1l-1ubuntu1
  Candidate: 1.1.1l-1ubuntu1
  Version table:
 *** 1.1.1l-1ubuntu1 100
        100 /var/lib/dpkg/status

I have also openssl 3.0.2:
$ apt-cache policy openssl
openssl:
  Installed: 3.0.2-0ubuntu1.7
  Candidate: 3.0.2-0ubuntu1.7
  Version table:
 *** 3.0.2-0ubuntu1.7 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main s390x Packages
        500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main s390x Packages
        100 /var/lib/dpkg/status
     3.0.2-0ubuntu1 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy/main s390x Packages

And with that I can install 'systemd-coredump':

$ apt-cache policy systemd-coredump
systemd-coredump:
  Installed: (none)
  Candidate: 249.11-0ubuntu3.6
  Version table:
     249.11-0ubuntu3.6 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe s390x Packages
     249.11-0ubuntu3 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy/universe s390x Packages
$ sudo apt install systemd-coredump
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  apport-symptoms python3-apport python3-problem-report python3-systemd
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  apport
The following NEW packages will be installed:
  systemd-coredump
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 56.6 kB of archives.
After this operation, 495 kB disk space will be freed.
Do you want to continue? [Y/n] Y
Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe s390x systemd-coredump s390x 249.11-0ubuntu3.6 [56.6 kB]
Fetched 56.6 kB in 0s (151 kB/s)
(Reading database ... 173937 files and directories currently installed.)
Removing apport (2.20.11-0ubuntu82.2) ...
Selecting previously unselected package systemd-coredump.
(Reading database ... 173858 files and directories currently installed.)
Preparing to unpack .../systemd-coredump_249.11-0ubuntu3.6_s390x.deb ...
Unpacking systemd-coredump (249.11-0ubuntu3.6) ...
Setting up systemd-coredump (249.11-0ubuntu3.6) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.10.2-1) ...
Scanning processes...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date (ABI upgrades are not detected).

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.
$ apt-c...

[Frank Heimes (fheimes)]

Btw. before you retry, you may fix the broken packaging state of your system with:
sudo apt-get -y -f install
and then:
sudo apt update
...

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2022-11-24 12:16 EDT-------
Hello Frank,

thanks for getting back to me on this. I did freshly install jammy jellyfish on a z/VM guest system.
I had updated the package definitions before I tried to install the systemd-coredump package (and attached my sources.list file)

Cross-checked the repository priority selections for 'coredump'
# apt-cache policy systemd-coredump
systemd-coredump:
Installed: (none)
Candidate: 249.11-0ubuntu3.6
Version table:
249.11-0ubuntu3.6 500
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe s390x Packages
249.11-0ubuntu3 500
500 http://ports.ubuntu.com/ubuntu-ports jammy/universe s390x Packages

Next I followed the hint to clean up the package definitions. Updated all packages until I got 0 pacakges for any category:
# apt-get -y -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

# apt update
Hit:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease
Hit:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease
Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports jammy-security/main s390x Packages [273 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports jammy-security/main Translation-en [108 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe s390x Packages [398 kB]
Get:8 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe Translation-en [80.9 kB]
Fetched 969 kB in 1s (1,924 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

After these operations the installation process for the systemd-coredump package worked well, and the coredumpctl command was available. libssl3 (i.e. OpenSSL 3.0) remained to be the single available OpenSSL version.

[Frank Heimes (fheimes)]

Hmm, I just checked the changelog of the relevant packages (openssl and systemd), assuming to find a fix that might have landed in between your two attempts - but not much, mainly CVE fixes.

(I also assume you haven't installed any local packages either...)

And you've used the same packages than I did.

So right now I can't really say what happened...

Anyway, would you be okay with me closing this bug?

[Steve Langasek (vorlon)]

The issue here was a locally installed libep11 package that depended on old OpenSSL. The problem was reported the first time apt was run after installing libep11. The old libssl dependency had nothing to do with systemd-coredump.

[Frank Heimes (fheimes)]

Oh yes, makes sense - thanks for the hint!

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2022-11-28 12:42 EDT-------
Thanks for having a look Frank and Steve.
I am all right with closing.