*Participation Requested*
MicroOS Desktop Use to Help with ALP Feedback
-
 Re: Upgrade 15.2 to 15.3 leads to libhandle.so.1.0.3 conflict
I've repeated the process but the end result is the same, installing systemd results in restarting the system.
So after doing the following steps:
Code:
# all repos with priority 99
zypper --releasever=15.3 ref
rpm -e --nodeps libhandle1
zypper --releasever=15.3 -v in --download-in-advance zypper libzypp libsolv-tools rpm libproxy1 libmodman1 curl openSUSE-release coreutils filesystem systemd udev aaa_base
# then reboot
zypper ref
zypper --releasever=15.3 -v dup --allow-vendor-change
There were no conflicts after the last command but installing systemd resulted in reboot.
Code:
(1208/5003) Installing: suse-module-tools-15.3.15-3.17.1.x86_64 .......................................................................................................................................................................................................................................................[done]
(1209/5003) Installing: kmod-29-4.15.1.x86_64 .........................................................................................................................................................................................................................................................................[done]
(1210/5003) Installing: systemd-246.16-150300.7.45.1.x86_64 ........................................................................................................................................................................................................................................................<100%>[-]Timeout, server
journalctl -fb shows some stack traces:
Code:
May 18 20:22:26 loginupgrade systemd-journald[602]: Forwarding to syslog missed 812 messages.
May 18 20:22:26 loginupgrade nscd[823]: 823 monitored file `/etc/group` was written to
May 18 20:22:26 loginupgrade nscd[823]: 823 monitored file `/etc/group` was moved into place, adding watch
May 18 20:22:26 loginupgrade groupadd[4540]: group added to /etc/group: name=audit, GID=475
May 18 20:22:26 loginupgrade nscd[823]: 823 monitoring file `/etc/passwd` (1)
May 18 20:22:26 loginupgrade nscd[823]: 823 monitoring directory `/etc` (2)
May 18 20:23:01 loginupgrade cron[4545]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:23:01 loginupgrade systemd-journald[602]: Forwarding to syslog missed 6 messages.
May 18 20:23:01 loginupgrade cron[4545]: PAM adding faulty module: /lib64/security/pam_unix.so
May 18 20:23:01 loginupgrade cron[4545]: PAM unable to dlopen(/lib64/security/pam_krb5.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:23:01 loginupgrade cron[4545]: PAM adding faulty module: /lib64/security/pam_krb5.so
May 18 20:23:01 loginupgrade kernel: cron[4545]: segfault at 8a96 ip 0000000000008a96 sp 00007fffe9e99f38 error 14 in cron[56384e267000+10000]
May 18 20:23:01 loginupgrade kernel: Code: Bad RIP value.
May 18 20:23:01 loginupgrade systemd[1]: Started Process Core Dump (PID 4546/UID 0).
May 18 20:23:06 loginupgrade systemd-coredump[4547]: Process 4545 (cron) of user 0 dumped core.
Stack trace of thread 4545:
#0 0x0000000000008a96 n/a (n/a)
May 18 20:23:37 loginupgrade systemd-journald[602]: Forwarding to syslog missed 5 messages.
May 18 20:24:01 loginupgrade cron[4557]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:24:01 loginupgrade cron[4557]: PAM adding faulty module: /lib64/security/pam_unix.so
May 18 20:24:01 loginupgrade cron[4557]: PAM unable to dlopen(/lib64/security/pam_krb5.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:24:01 loginupgrade cron[4557]: PAM adding faulty module: /lib64/security/pam_krb5.so
May 18 20:24:01 loginupgrade kernel: cron[4557]: segfault at 8a96 ip 0000000000008a96 sp 00007fffe9e99f38 error 14 in cron[56384e267000+10000]
May 18 20:24:01 loginupgrade kernel: Code: Bad RIP value.
May 18 20:24:01 loginupgrade systemd[1]: Started Process Core Dump (PID 4558/UID 0).
May 18 20:24:06 loginupgrade systemd-coredump[4559]: Process 4557 (cron) of user 0 dumped core.
Stack trace of thread 4557:
#0 0x0000000000008a96 n/a (n/a)
May 18 20:24:07 loginupgrade systemd-journald[602]: Forwarding to syslog missed 6 messages.
May 18 20:25:01 loginupgrade cron[4567]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:25:01 loginupgrade systemd-journald[602]: Forwarding to syslog missed 1 messages.
May 18 20:25:01 loginupgrade kernel: cron[4567]: segfault at 8a96 ip 0000000000008a96 sp 00007fffe9e99f38 error 14 in cron[56384e267000+10000]
May 18 20:25:01 loginupgrade kernel: Code: Bad RIP value.
May 18 20:25:01 loginupgrade cron[4567]: PAM adding faulty module: /lib64/security/pam_unix.so
May 18 20:25:01 loginupgrade cron[4567]: PAM unable to dlopen(/lib64/security/pam_krb5.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:25:01 loginupgrade cron[4567]: PAM adding faulty module: /lib64/security/pam_krb5.so
May 18 20:25:01 loginupgrade systemd[1]: Started Process Core Dump (PID 4568/UID 0).
May 18 20:25:06 loginupgrade systemd-coredump[4569]: Process 4567 (cron) of user 0 dumped core.
Stack trace of thread 4567:
#0 0x0000000000008a96 n/a (n/a)
May 18 20:26:01 loginupgrade cron[4580]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:26:01 loginupgrade systemd-journald[602]: Forwarding to syslog missed 9 messages.
May 18 20:26:01 loginupgrade kernel: cron[4580]: segfault at 8a96 ip 0000000000008a96 sp 00007fffe9e99f38 error 14 in cron[56384e267000+10000]
May 18 20:26:01 loginupgrade kernel: Code: Bad RIP value.
May 18 20:26:01 loginupgrade cron[4580]: PAM adding faulty module: /lib64/security/pam_unix.so
May 18 20:26:01 loginupgrade cron[4580]: PAM unable to dlopen(/lib64/security/pam_krb5.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:26:01 loginupgrade cron[4580]: PAM adding faulty module: /lib64/security/pam_krb5.so
May 18 20:26:01 loginupgrade systemd[1]: Started Process Core Dump (PID 4581/UID 0).
May 18 20:26:06 loginupgrade systemd-coredump[4582]: Process 4580 (cron) of user 0 dumped core.
Stack trace of thread 4580:
#0 0x0000000000008a96 n/a (n/a)
May 18 20:26:35 loginupgrade systemd-journald[602]: Forwarding to syslog missed 5 messages.
May 18 20:27:01 loginupgrade cron[4590]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:27:01 loginupgrade cron[4590]: PAM adding faulty module: /lib64/security/pam_unix.so
May 18 20:27:01 loginupgrade kernel: cron[4590]: segfault at 8a96 ip 0000000000008a96 sp 00007fffe9e99f38 error 14 in cron[56384e267000+10000]
May 18 20:27:01 loginupgrade kernel: Code: Bad RIP value.
May 18 20:27:01 loginupgrade cron[4590]: PAM unable to dlopen(/lib64/security/pam_krb5.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:27:01 loginupgrade cron[4590]: PAM adding faulty module: /lib64/security/pam_krb5.so
May 18 20:27:01 loginupgrade systemd[1]: Started Process Core Dump (PID 4591/UID 0).
May 18 20:27:06 loginupgrade systemd-coredump[4592]: Process 4590 (cron) of user 0 dumped core.
Stack trace of thread 4590:
#0 0x0000000000008a96 n/a (n/a)
May 18 20:27:06 loginupgrade systemd-journald[602]: Forwarding to syslog missed 6 messages.
May 18 20:28:01 loginupgrade cron[4601]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:28:01 loginupgrade systemd-journald[602]: Forwarding to syslog missed 1 messages.
May 18 20:28:01 loginupgrade cron[4601]: PAM adding faulty module: /lib64/security/pam_unix.so
May 18 20:28:01 loginupgrade cron[4601]: PAM unable to dlopen(/lib64/security/pam_krb5.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:28:01 loginupgrade cron[4601]: PAM adding faulty module: /lib64/security/pam_krb5.so
May 18 20:28:01 loginupgrade kernel: cron[4601]: segfault at 8a96 ip 0000000000008a96 sp 00007fffe9e99f38 error 14 in cron[56384e267000+10000]
May 18 20:28:01 loginupgrade kernel: Code: Bad RIP value.
May 18 20:28:01 loginupgrade systemd[1]: Started Process Core Dump (PID 4602/UID 0).
May 18 20:28:06 loginupgrade systemd-coredump[4603]: Process 4601 (cron) of user 0 dumped core.
Stack trace of thread 4601:
#0 0x0000000000008a96 n/a (n/a)
May 18 20:28:45 loginupgrade systemd-journald[602]: Forwarding to syslog missed 5 messages.
May 18 20:29:01 loginupgrade cron[4611]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:29:01 loginupgrade cron[4611]: PAM adding faulty module: /lib64/security/pam_unix.so
May 18 20:29:01 loginupgrade cron[4611]: PAM unable to dlopen(/lib64/security/pam_krb5.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:29:01 loginupgrade cron[4611]: PAM adding faulty module: /lib64/security/pam_krb5.so
May 18 20:29:01 loginupgrade kernel: cron[4611]: segfault at 8a96 ip 0000000000008a96 sp 00007fffe9e99f38 error 14 in cron[56384e267000+10000]
May 18 20:29:01 loginupgrade kernel: Code: Bad RIP value.
May 18 20:29:01 loginupgrade systemd[1]: Started Process Core Dump (PID 4612/UID 0).
May 18 20:29:06 loginupgrade systemd-coredump[4613]: Process 4611 (cron) of user 0 dumped core.
Stack trace of thread 4611:
#0 0x0000000000008a96 n/a (n/a)
May 18 20:29:38 loginupgrade systemd-journald[602]: Forwarding to syslog missed 6 messages.
May 18 20:30:01 loginupgrade cron[4622]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:30:01 loginupgrade cron[4622]: PAM adding faulty module: /lib64/security/pam_unix.so
May 18 20:30:01 loginupgrade cron[4622]: PAM unable to dlopen(/lib64/security/pam_krb5.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:30:01 loginupgrade cron[4622]: PAM adding faulty module: /lib64/security/pam_krb5.so
May 18 20:30:01 loginupgrade kernel: cron[4622]: segfault at 8a96 ip 0000000000008a96 sp 00007fffe9e99f38 error 14 in cron[56384e267000+10000]
May 18 20:30:01 loginupgrade kernel: Code: Bad RIP value.
May 18 20:30:01 loginupgrade systemd[1]: Started Process Core Dump (PID 4624/UID 0).
May 18 20:30:06 loginupgrade systemd-coredump[4625]: Process 4622 (cron) of user 0 dumped core.
Stack trace of thread 4622:
#0 0x0000000000008a96 n/a (n/a)
May 18 20:30:13 loginupgrade systemd-journald[602]: Forwarding to syslog missed 6 messages.
May 18 20:31:01 loginupgrade cron[4657]: PAM unable to dlopen(/lib64/security/pam_unix.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:31:01 loginupgrade systemd-journald[602]: Forwarding to syslog missed 1 messages.
May 18 20:31:01 loginupgrade cron[4657]: PAM adding faulty module: /lib64/security/pam_unix.so
May 18 20:31:01 loginupgrade kernel: cron[4657]: segfault at 8a96 ip 0000000000008a96 sp 00007fffe9e99f38 error 14 in cron[56384e267000+10000]
May 18 20:31:01 loginupgrade kernel: Code: Bad RIP value.
May 18 20:31:01 loginupgrade cron[4657]: PAM unable to dlopen(/lib64/security/pam_krb5.so): /lib64/libpthread.so.0: symbol __sigtimedwait, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
May 18 20:31:01 loginupgrade cron[4657]: PAM adding faulty module: /lib64/security/pam_krb5.so
May 18 20:31:01 loginupgrade systemd[1]: Started Process Core Dump (PID 4658/UID 0).
May 18 20:31:07 loginupgrade systemd-coredump[4659]: Process 4657 (cron) of user 0 dumped core.
Stack trace of thread 4657:
#0 0x0000000000008a96 n/a (n/a)
May 18 20:31:34 loginupgrade systemd-journald[602]: Forwarding to syslog missed 5 messages.
Tomorrow I can provide more journalctl if required.
-
Re: Upgrade 15.2 to 15.3 leads to libhandle.so.1.0.3 conflict
 Originally Posted by derDaywalker
It seems that systemd fails to start but logs are suppressed. Could you boot with the following additional kernel parameters:
Code:
printk.devkmsg=on plymouth.enable=0
and post screenshot again? Hopefully it will contain more information.
-
Re: Upgrade 15.2 to 15.3 leads to libhandle.so.1.0.3 conflict
Originally Posted by arvidjaar
It seems that systemd fails to start but logs are suppressed. Could you boot with the following additional kernel parameters:
Code:
printk.devkmsg=on plymouth.enable=0
and post screenshot again? Hopefully it will contain more information.
Hi
I've added the boot parameter: https://susepaste.org/95d7c70c
But the boot message is the same: https://susepaste.org/19401028
I'm really grateful for all your efforts to solve this issue! It's really hard and I'm totally lost without your help! So thank you all again!
-
Re: Upgrade 15.2 to 15.3 leads to libhandle.so.1.0.3 conflict
Whenever this appears here, and unless the conflict relates directly to the package management system, I force remove the older package(s) with rpm -e --nodeps packagename, then try again, letting zypper resolve any remaining deps or conflicts.
Reg. Linux User 211409 *** multibooting since 1992
Primary: 15.3, TW, 15.1 & 13.1 on Haswell @earthlink.net
Secondary: eComStation (OS/2) &15.2 on i965P/Radeon
Tertiary: Debian, Fedora, Mageia, more on Rocket Lake & older Intel, AMD, NVidia....
-
Re: Upgrade 15.2 to 15.3 leads to libhandle.so.1.0.3 conflict
Hi,
Thank you for your reply!
My following post is after resolving the first conflict and installing the packages like suggested earlier with the following commands:
Code:
zypper --releasever=15.3 ref
rpm -e --nodeps libhandle1
zypper --releasever=15.3 -v in --download-in-advance zypper libzypp libsolv-tools rpm libproxy1 libmodman1 curl openSUSE-release coreutils filesystem systemd udev aaa_base
# then reboot
After the reboot the system starts successfully. When I then issue a zypper up -l then I get the git conflict again plus a plymouth conflict:
Code:
Checking for file conflicts: ........................................................................................................................[error]
Detected 19 file conflicts:
File /usr/bin/rpcgen
from install of
rpcgen-1.4.2-1.46.x86_64 (oss)
conflicts with file from package
glibc-devel-2.26-lp152.26.12.1.x86_64 (@System)
File /usr/lib/perl5/vendor_perl/5.26.1/Git.pm
from install of
perl-Git-2.35.3-150300.10.12.1.x86_64 (Update repository with updates from SUSE Linux Enterprise 15)
conflicts with file from install of
git-core-2.26.2-3.34.1.x86_64 (oss)
[ + a lot of other perl / git conflicts ]
File /usr/share/plymouth/plymouthd.defaults
from install of
plymouth-branding-openSUSE-15.3.20210112-lp153.1.26.noarch (oss)
conflicts with file from package
plymouth-0.9.4+git20190304.ed9f201-lp152.4.4.x86_64 (@System)
Then I remove the plymouth:
Code:
# rpm -e --nodeps plymouth-0.9.4+git20190304.ed9f201-lp152.4.4.x86_64
warning: /etc/plymouth/plymouthd.conf saved as /etc/plymouth/plymouthd.conf.rpmsave
But I can't find anything about the perl-git but about git-core:
Code:
# rpm -qa | grep -i git-core
git-core-2.26.2-lp152.2.12.1.x86_64
#
# rpm -qa | grep -i perl-git
#
After removing the git-core too, there are no further conflicts but while installing the package I get concerning errors, which could explain why I can't boot afterwards:
Code:
Executing %posttrans script 'login_defs-4.8.1-150300.4.3.8.noarch.rpm' ----------------------------------------------------------------------------------[-]
Output of xfsprogs-4.15.0-4.52.1.x86_64.rpm %posttrans script:
Creating initrd: /boot/initrd-5.3.18-150300.59.68-default
dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force --force-drivers "thermal pata_amd mptsas ata_generic amd74xx ide_pci_generic processor fan xennet xenblk" /boot/initrd-5.3.18-150300.59.68-default 5.3.18-150300.59.68-default
/usr/lib/systemd/systemd: /lib64/libapparmor.so.1: version `APPARMOR_2.13' not found (required by /usr/lib/systemd/systemd)
/usr/lib/systemd/systemd: /lib64/libapparmor.so.1: version `APPARMOR_2.10' not found (required by /usr/lib/systemd/systemd)
dracut: systemd version is not a number ()
Creating initrd: /boot/initrd-5.3.18-59.10-default
dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force --force-drivers "thermal pata_amd mptsas ata_generic amd74xx ide_pci_generic processor fan xennet xenblk" /boot/initrd-5.3.18-59.10-default 5.3.18-59.10-default
/usr/lib/systemd/systemd: /lib64/libapparmor.so.1: version `APPARMOR_2.13' not found (required by /usr/lib/systemd/systemd)
/usr/lib/systemd/systemd: /lib64/libapparmor.so.1: version `APPARMOR_2.10' not found (required by /usr/lib/systemd/systemd)
dracut: systemd version is not a number ()
Creating initrd: /boot/initrd-5.3.18-lp152.106-default
dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force --force-drivers "thermal pata_amd mptsas ata_generic amd74xx ide_pci_generic processor fan xennet xenblk" /boot/initrd-5.3.18-lp152.106-default 5.3.18-lp152.106-default
/usr/lib/systemd/systemd: /lib64/libapparmor.so.1: version `APPARMOR_2.13' not found (required by /usr/lib/systemd/systemd)
/usr/lib/systemd/systemd: /lib64/libapparmor.so.1: version `APPARMOR_2.10' not found (required by /usr/lib/systemd/systemd)
dracut: systemd version is not a number ()
Generating /boot/initrd-5.3.18-150300.59.68-default /boot/initrd-5.3.18-59.10-default /boot/initrd-5.3.18-lp152.106-default targets failed
Warning: xfsprogs-4.15.0-4.52.1.x86_64.rpm %posttrans script failed (returned 1)
Executing %posttrans script 'raleway-fonts-3.0-1.22.noarch.rpm' <5%>=====================================================================================[|]
Output of dmraid-1.0.0.rc16-3.26.x86_64.rpm %posttrans script:
Updating /etc/sysconfig/dmraid ...
Executing %posttrans scripts .........................................................................................................................[done]
There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.
Since the last system boot core libraries or services have been updated.
Reboot is suggested to ensure that your system benefits from these updates.
While installing I also get worrisome messages like:
Code:
(2031/4654) Installing: irqbalance-1.4.0-12.6.1.x86_64 ...............................................................................................[done]Additional rpm output:
Updating /etc/sysconfig/irqbalance ...
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
or
Code:
(2950/4654) Installing: kernel-default-5.3.18-150300.59.68.1.x86_64 ..................................................................................[done]
Additional rpm output:
Creating initrd: /boot/initrd-5.3.18-150300.59.68-default
dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force --force-drivers "thermal pata_amd mptsas ata_generic amd74xx ide_pci_generic processor fan xennet xenblk" /boot/initrd-5.3.18-150300.59.68-default 5.3.18-150300.59.68-default
/usr/lib/systemd/systemd: /lib64/libapparmor.so.1: version `APPARMOR_2.13' not found (required by /usr/lib/systemd/systemd)
/usr/lib/systemd/systemd: /lib64/libapparmor.so.1: version `APPARMOR_2.10' not found (required by /usr/lib/systemd/systemd)
dracut: systemd version is not a number ()
Generating /boot/initrd-5.3.18-150300.59.68-default targets failed
warning: %post(kernel-default-5.3.18-150300.59.68.1.x86_64) scriptlet failed, exit status 1
After that I can't boot of course...
Resetting to the first state and instead of zypper up -l just installing systemd via zypper in systemd I also get the cryptsetup error:
Code:
( 16/100) Installing: systemd-246.13-5.1.x86_64 .......................................................................................................................................................................................................................................................................[done]
Additional rpm output:
warning: /etc/systemd/journald.conf created as /etc/systemd/journald.conf.rpmnew
warning: /etc/systemd/system.conf created as /etc/systemd/system.conf.rpmnew
/usr/bin/systemd-sysusers: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/lib/systemd/systemd-random-seed: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/journalctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemd-tmpfiles: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
At least it doesn't just boot while installing systemd which might be a progress but the end result is the same that the system can't boot. So maybe I should include some libs? But I thought that installing systemd will take care of what it needs.
Fun fact, after installation is complete I can't reboot properly:
Code:
# reboot
reboot: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
Thus I reboot with echo "b" > /proc/sysrq-trigger
Resetting again to the first state and just issuing the same command then before (
Code:
zypper --releasever=15.3 -v in --download-in-advance zypper libzypp libsolv-tools rpm libproxy1 libmodman1 curl openSUSE-release coreutils filesystem systemd udev aaa_base
) leads to the same result of non-bootable system and cryptsetup error, but at least no conflicts: https://susepaste.org/88192019
The conclusion is, starting from the above setup using zypper up -l results in not booting with the cryptsetup error message (and others), just issuing zypper in systemd produces the cryptsetup error messages and renders a non-bootable system. And issuing zypper dup -l results in auto rebooting while installing systemd and thus not all packages are installed plus the system renders also non-bootable. And just issuing a second time the zypper in command results in the same state. I guess I did every trial-and-error possibility and I'm totally lost.
-
Re: Upgrade 15.2 to 15.3 leads to libhandle.so.1.0.3 conflict
Am I understanding right that after issuing:
Code:
# zypper --releasever=15.3 -v in --download-in-advance zypper libzypp libsolv-tools rpm libproxy1 libmodman1 curl openSUSE-release coreutils filesystem systemd udev aaa_base
your next step is to reboot? That makes no sense. The next step should be to finish the upgrade:
Code:
# zypper dup --releasever=15.3
or as I do
Code:
# zypper -v up
# zypper -v dup
(My repo URIs all include 15.3 rather than $releasever.)
Reg. Linux User 211409 *** multibooting since 1992
Primary: 15.3, TW, 15.1 & 13.1 on Haswell @earthlink.net
Secondary: eComStation (OS/2) &15.2 on i965P/Radeon
Tertiary: Debian, Fedora, Mageia, more on Rocket Lake & older Intel, AMD, NVidia....
-
Re: Upgrade 15.2 to 15.3 leads to libhandle.so.1.0.3 conflict
Originally Posted by derDaywalker
When I then issue a zypper up -l
You cannot upgrade between releases using "zypper up", You must use zypper dup.
-
Re: Upgrade 15.2 to 15.3 leads to libhandle.so.1.0.3 conflict
Hi,
okay, I did go back to square one. So completely from the beginning of my first snapshot without doing anything before.
Then I issued the following commands:
Code:
sed -i 's/$releasever\|15.2/15.3/' /etc/zypp/repos.d/*.repo
sed -i '/priority\=/d' /etc/zypp/repos.d/*.repo
zypper ref
rpm -e --nodeps libhandle1
zypper al texlive*
The sed commands set it straight to 15.3 and removed all priorities. Then I removed the libhandle1 because this always leads to the conflict. Then I locked all texlive packages in order to reduce the download and install size, because every try costs around 30 minutes.
Thats the base for the next two tries.
After the above commands I issued :
Code:
zypper -v in --download-in-advance zypper libzypp libsolv-tools rpm libproxy1 libmodman1 curl openSUSE-release coreutils filesystem systemd udev aaa_base
Thats the result: https://susepaste.org/e4b9b54e
I guess the dracut messages are not that bad plus it complains about newer packages versions with other vendors.
And then directly after that (without rebooting) I issued
Thats the result: https://susepaste.org/203474d6
No error messages which sounds good, but the result is, that while installing systemd package the system rebooted instantly. I guess its not really common that the system reboots while installing the package if there are over 2000 packages left to install.
Because the first install command complained about newer packages with newer vendors I decided to do it all over again and allow vendor changes.
Code:
zypper -v in --allow-vendor-change --download-in-advance zypper libzypp libsolv-tools rpm libproxy1 libmodman1 curl openSUSE-release coreutils filesystem systemd udev aaa_base
Result: https://pastebin.com/5C5V6vQF
(For any reason, susepaste always says I'm a spammer when I want to paste the output of that command, thus I had to use pastebin for that)
The dracut errors seems to be way heavier and there are undefined symbol errors with the cryptsetup error I mentioned before.
And after that without rebooting:
Code:
zypper dup -l --allow-vendor-change
Result: https://susepaste.org/ea12e144
And crash: https://susepaste.org/f3d0e8a3
The result is the same, their are cryptsetup errors and it reboots while installing systemd.
-
Re: Upgrade 15.2 to 15.3 leads to libhandle.so.1.0.3 conflict
Originally Posted by derDaywalker
Code:
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
The crypt_activate_by_signed_key is provided by libcryptsetup12 in Leap 15.3, but is missing in libcryptsetup12 in Leap 15.2. Unfortunately package metadata for both libraries is identical, so nothing tells rpm/zypper it needs to update this library first.
There is probably some other reason in case of full dup, because according to your log libcryptsetup12 is installed before systemd. Still, full dup log shows
Code:
warning: /var/cache/zypp/packages/packman/Essentials/x86_64/libgstphotography-1_0-0-1.16.3-pm153.3.6.5.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 1abd1afb: NOKEY
which means you have third-party repositories and performing unrestricted "zypper dup --allow-vendor-change" in presence of third party repositories is rather unpredictable.
As the last resort I would disable all non-openSUSE repositories (except openSUSE GA and update), ensure that all packages come from openSUSE and you have the latest updates and try zypper dup again. If that works you can add other repositories and packages later. If that fails too ... well, clean install is probably more simple.
-
Re: Upgrade 15.2 to 15.3 leads to libhandle.so.1.0.3 conflict
Okay, that explanation sounds good to me, why it fails with the libcrypt. Which repos do you have in mind? The packman repo?
Because I did this:
Code:
# zypper mr -d 3
Repository 'packman' has been successfully disabled.
#
# zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
--+----------------+----------------+---------+-----------+---------+----------+--------+-------------------------------------------------------------------+--------
1 | non-oss | non-oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/ |
2 | oss | oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.3/repo/oss/ |
3 | packman | packman | No | ---- | ---- | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.3/ |
4 | update-non-oss | update-non-oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.3/non-oss/ |
5 | update-oss | update-oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.3/oss/ |
#
# rpm -e --nodeps libhandle1
#
# zypper al texlive*
Specified lock has been successfully added.
#
# zypper -v in --allow-vendor-change --download-in-advance zypper libzypp libsolv-tools rpm libproxy1 libmodman1 curl openSUSE-release coreutils filesystem systemd udev aaa_base
With --allow-vendor-change the result is the same: https://pastebin.com/vhc7Y3kH
Code:
( 27/117) Installing: systemd-246.13-5.1.x86_64 .......................................................................................................................................................................................................................................................................[done]
Additional rpm output:
warning: /etc/systemd/journald.conf created as /etc/systemd/journald.conf.rpmnew
warning: /etc/systemd/system.conf created as /etc/systemd/system.conf.rpmnew
/usr/bin/systemd-sysusers: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/lib/systemd/systemd-random-seed: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/journalctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemd-tmpfiles: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
/usr/bin/systemctl: symbol lookup error: /usr/lib/systemd/libsystemd-shared-246.so: undefined symbol: crypt_activate_by_signed_key, version CRYPTSETUP_2.0
zypper dup -l afterwards of course suffer from the same issue. Their aren't any other repos installed like you see. Maybe I should somehow remove libcryptsetup12 manually and install the newest version before and then do the zypper in command listed above?
I also searched for any updates for 15.2, but their are non, or I have to change the mirror URL?
Code:
# sed -i 's/$releasever\|15.3/15.2/' /etc/zypp/repos.d/*.repo
#
#
# zypper ref
Retrieving repository 'non-oss' metadata ..............................................................................................................................................................................................................................................................................[done]
Building repository 'non-oss' cache ...................................................................................................................................................................................................................................................................................[done]
Retrieving repository 'oss' metadata ..................................................................................................................................................................................................................................................................................[done]
Building repository 'oss' cache .......................................................................................................................................................................................................................................................................................[done]
Retrieving repository 'update-non-oss' metadata .......................................................................................................................................................................................................................................................................[done]
Building repository 'update-non-oss' cache ............................................................................................................................................................................................................................................................................[done]
Retrieving repository 'update-oss' metadata ...........................................................................................................................................................................................................................................................................[done]
Building repository 'update-oss' cache ................................................................................................................................................................................................................................................................................[done]
All repositories have been refreshed.
#
# zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
--+----------------+----------------+---------+-----------+---------+----------+--------+-------------------------------------------------------------------+--------
1 | non-oss | non-oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.2/repo/non-oss/ |
2 | oss | oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.2/repo/oss/ |
3 | packman | packman | No | ---- | ---- | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.2/ |
4 | update-non-oss | update-non-oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.2/non-oss/ |
5 | update-oss | update-oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.2/oss/ |
# zypper up -l
Loading repository data...
Warning: Repository 'update-non-oss' appears to be outdated. Consider using a different mirror or server.
Warning: Repository 'update-oss' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...
Nothing to do.
Unfortunately installing a clean 15.3 isn't really an option because its a complicated legacy setup for NFSv4 and custom scripts etc. Thats why I spend that much time into it saving the setup, otherwise of course it would be easier to install a new system. Thus thank you again for all your time so far.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
| 
