September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1192624] New: ltp_nfs nfs05 (NFS stress test with make) fails
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1192624 Bug ID: 1192624 Summary: ltp_nfs nfs05 (NFS stress test with make) fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed Build 20211110 kernel 5.14.14-2-default (2b5383f) [1] (but it might have been failing in 5.13 and older kernels) fails to run all nfs*_05 tests which run shell script nfs05 [2] which runs nfs05_make_tree.c [3] (NFS stress test with make). Test output: # nfs05 -v 4 -t tcp; echo "### TEST nfs4_05 COMPLETE >>> $?" nfs05 1 TINFO: timeout per run is 0h 5m 0s nfs05 1 TINFO: setup NFSv4, socket type tcp nfs05 1 TINFO: Mounting NFS: mount -v -t nfs -o proto=tcp,vers=4 10.0.0.2:/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp /tmp/LTP_nfs05.G8q7DLN0j0/4/0 nfs05 1 TINFO: start nfs05_make_tree -d 20 -f 50 -t 8 tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s Test timed out, sending SIGTERM! If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 Terminated nfs05 1 TBROK: test terminated nfs05 1 TINFO: Cleaning up testcase umount.nfs4: /tmp/LTP_nfs05.G8q7DLN0j0/4/0: device is busy Test is still running... 10 Test is still running... 9 Test is still running... 8 make[6]: *** No rule to make target '26445.6.20.c', needed by '26445.6.20'. Stop. make[5]: *** [makefile:9: dir] Error 2 make[4]: *** [makefile:9: dir] Error 2 make[3]: *** [makefile:9: dir] Error 2 make[2]: *** [makefile:9: dir] Error 2 make[1]: *** [makefile:9: dir] Error 2 make: *** [makefile:9: dir] Error 2 tst_cmd.c:109: TBROK: 'make' exited with a non-zero code 2 at tst_cmd.c:109 Test is still running... 7 ... make: *** [makefile:9: dir] Error 2 Test is still running... 1 rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26445/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26446/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26447/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26448/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26449/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26450/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26452/dir/dir/dir/dir/dir/dir': Directory not empty rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/tcp/susetest.26451/dir/dir/dir/dir/dir/dir': Directory not empty make[6]: *** No rule to make target '26451.6.46.c', needed by '26451.6.46'. Stop. make[5]: *** [makefile:9: dir] Error 2 make[4]: *** [makefile:9: dir] Error 2 make[3]: *** [makefile:9: dir] Error 2 make[2]: *** [makefile:9: dir] Error 2 make[1]: *** [makefile:9: dir] Error 2 make: *** [makefile:9: dir] Error 2 rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/0': Device or resource busy rm: cannot remove '/tmp/LTP_nfs05.G8q7DLN0j0/4/0': Is a directory There is probably no stack trace in dmesg related to this test (in attached dmesg there is really long Call Trace related to FCNTL_LOCKTESTS reported in #1192623). [1] https://openqa.opensuse.org/tests/2029105 [2] https://github.com/linux-test-project/ltp/blob/master/testcases/network/nfs… [3] https://github.com/linux-test-project/ltp/blob/master/testcases/network/nfs… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1197369] New: Screenlocker does not work using frameworks unstable
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1197369 Bug ID: 1197369 Summary: Screenlocker does not work using frameworks unstable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: robby.engelmann(a)r-engelmann.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Screenlocker just do not work since approx 1-2 weeks using the KDE unstable repos. Operating System: openSUSE Tumbleweed 20220320 KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.16.15-1-default (64-bit) Graphics Platform: Wayland Processors: 8 �� Intel�� Core�� i7-10510U CPU @ 1.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel�� UHD Graphics -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1199549] New: plasmashell unusable in frameworks master builds
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199549 Bug ID: 1199549 Summary: plasmashell unusable in frameworks master builds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: robby.engelmann(a)r-engelmann.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- plasmashell shows 100% CPU since last friday update of frameworks-unstable repo. This can be seen starting from yakuake after having plasmashell killed: xx@linux-6mz9:~> plasmashell& [1] 4491 xx@linux-6mz9:~> kf.plasma.quick: Applet preload policy set to 1 file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: QML Connections: Detected function "onConfigurationChanged" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name. file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:70:5: QML Connections: Detected function "onRepaintNeeded" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name. file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:67: TypeError: Cannot read property 'wallpaper' of null file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:71: TypeError: Cannot read property 'wallpaper' of null file:///usr/share/plasma/plasmoids/org.kde.plasma.notes/contents/ui/main.qml:152:13: QML TextArea: Binding loop detected for property "implicitWidth" org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1166005] New: 20s to unlock fully encrypted partition
by bugzilla_noreply＠novell.com 25 Jan '23

25 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1166005 Bug ID: 1166005 Summary: 20s to unlock fully encrypted partition Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: axel.braun(a)gmx.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I have a new TW installation with a 940GB encrypted root partition (including /boot, excluding /boot/efi). When starting the machine, grub asks in text mode for the passphrase. After entering the passphrase, it takes about 20s until the graphical boot screen appears. X1E:/home/test # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 953,9G 0 disk ├─nvme0n1p1 259:1 0 500M 0 part /boot/efi ├─nvme0n1p2 259:2 0 937G 0 part │ └─cr_root 254:0 0 937G 0 crypt / └─nvme0n1p3 259:3 0 16,4G 0 part [SWAP] linux:/home/test # cryptsetup luksDump /dev/nvme0n1p2 LUKS header information for /dev/nvme0n1p2 Version: 1 Cipher name: aes Cipher mode: xts-plain64 Hash spec: sha256 Payload offset: 4096 MK bits: 512 MK digest: c3 b3 b9 a1 4b cd 08 8d 93 47 59 be f1 b8 f3 24 5f ae 81 75 MK salt: 8b 87 eb c4 bd 43 4e af 57 ef eb 9f 3c 38 a9 8a f4 c5 63 2f 1b f6 98 1a 49 62 36 e0 9e 12 8a db MK iterations: 153840 UUID: 720864c9-f8ed-405e-9a17-ccfa1d2f347b Key Slot 0: ENABLED Iterations: 1229280 Salt: 5f 9b 38 6b 29 b4 2e b0 80 35 c5 bd 88 9f 77 61 29 6c 34 00 54 3c af a5 5a d4 f6 15 7e e4 8d c4 Key material offset: 8 AF stripes: 4000 Key Slot 1: DISABLED Key Slot 2: DISABLED Key Slot 3: DISABLED Key Slot 4: DISABLED Key Slot 5: DISABLED Key Slot 6: DISABLED Key Slot 7: DISABLED It is an i7-9750H machine, so CPU power should not be an issue... -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1184069] New: GRUB on a crypted partition takes > 10 seconds to unlock the filesystem
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1184069 Bug ID: 1184069 Summary: GRUB on a crypted partition takes > 10 seconds to unlock the filesystem Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: p.heinlein(a)heinlein-support.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed 15.2 plain vanilla on a Thinkpad X1.Extreme Gen.3 with a ~2 TB NVME and I set a crypto disc password during installation (in YaST). Grub needs > 10 seconds to unlock the key, so booting is very slow. It's very similar to https://unix.stackexchange.com/questions/369414/grub-takes-too-long-to-unlo… https://bbs.archlinux.org/viewtopic.php?id=228865 so I also think, that the crypto or number of iterations is way to expensive here and needs too much time. Maybe the SUSE team should/could look for a similar safe, but faster method (SHA256?) here? -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1190738] New: kernel-default-base does not contain kernel changelog
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190738 Bug ID: 1190738 Summary: kernel-default-base does not contain kernel changelog Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jeos-internal(a)suse.de Found By: --- Blocker: --- kernel-default-base is built from a separate set of .spec and .changes files, making use of the kernel-subpackage facilities. This however means that the changelog of the original kernel packages (kernel-default, -vanilla, etc.) does not end up in the changelog of kernel-default-base. This is especially visible in updates, which only change the binary content and the version number in an unobvious way. There is no mention of any relevant fixed bugs (bsc#, CVE-). It would be very useful to include the kernel changelog in the kernel-default-base package. I don't think it can (or should) be interleaved with the subpackage .changes file, but it could be included as file. The target systems usually have excludedocs enabled though, so marking the file as %doc means it won't get installed. That makes it more complex and annoying... -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1176026] New: bond interface should not invent mac address by default
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1176026 Bug ID: 1176026 Summary: bond interface should not invent mac address by default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- since 5.8.4 (unsure about last digit): when setting up a bond if kernel chooses a random mac removing and readding the slave gets back to the used behaviour: obs-arm-1:~ # modprobe bonding 3: enP2p1s0v1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 1c:1b:0d:60:ee:8b brd ff:ff:ff:ff:ff:ff 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 9e:29:55:da:aa:0e brd ff:ff:ff:ff:ff:ff obs-arm-1:~ # echo +enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 9e:29:55:da:aa:0e brd ff:ff:ff:ff:ff:ff obs-arm-1:~ # echo -enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves obs-arm-1:~ # echo +enP2p1s0v1 > /sys/class/net/bond0/bonding/slaves 7: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 1c:1b:0d:60:ee:8b brd ff:ff:ff:ff:ff:ff -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1193417] New: using a Bluetooth keyboard slows down going to sleep for a few seconds
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1193417 Bug ID: 1193417 Summary: using a Bluetooth keyboard slows down going to sleep for a few seconds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: suse(a)rop.cx QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- when I have a Bluetooth keyboard connected and I press the switch to sleep mode, then at first the screen simply locks, stays in this state for about 4-6 seconds and only then goes to sleep mode Kernel logs: 06/12/2021 01:57 systemd-logind Power key pressed. 06/12/2021 01:57 dbus-daemon [session uid=1000 pid=1840] Activating service name='org.kde.LogoutPrompt' requested by ':1.13' (uid=1000 pid=1991 comm="/usr/bin/ksmserver ") 06/12/2021 01:57 dbus-daemon [session uid=1000 pid=1840] Successfully activated service 'org.kde.LogoutPrompt' 06/12/2021 01:57 NetworkManager <info> [1638745075.7552] manager: sleep: sleep requested (sleeping: no enabled: yes) 06/12/2021 01:57 ModemManager <info> [sleep-monitor] system is about to suspend 06/12/2021 01:57 kded5 bluedevil: About to suspend 06/12/2021 01:57 kded5 plasma-nm: Unhandled active connection state change: 3 06/12/2021 01:57 dbus-daemon [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1166 comm="/usr/sbin/NetworkManager --no-daemon ") 06/12/2021 01:57 dbus-daemon [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.53' (uid=1000 pid=2018 comm="/usr/bin/plasmashell ") 06/12/2021 01:57 systemd Starting Network Manager Script Dispatcher Service... 06/12/2021 01:57 systemd Starting PackageKit Daemon... 06/12/2021 01:57 PackageKit daemon start 06/12/2021 01:57 dbus-daemon [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 06/12/2021 01:57 systemd Started Network Manager Script Dispatcher Service. 06/12/2021 01:57 kernel wlp0s20f3: deauthenticating from f8:f0:82:6d:a9:5a by local choice (Reason: 3=DEAUTH_LEAVING) 06/12/2021 01:57 dbus-daemon [system] Successfully activated service 'org.freedesktop.PackageKit' 06/12/2021 01:57 plasmashell plasma-pk-updates: Daemon changed 06/12/2021 01:57 kscreenlocker_greet Qt: Session management error: networkIdsList argument is NULL 06/12/2021 01:57 kded5 plasma-nm: Not emitting connection deactivated notification as we're about to suspend 06/12/2021 01:57 kded5 plasma-nm: Network connectivity limited, scheduling notification 06/12/2021 01:57 kscreenlocker_greet file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:47:9: Unable to assign [undefined] to bool 06/12/2021 01:57 systemd Reached target Sleep. 06/12/2021 01:57 systemd Starting System Suspend... 06/12/2021 01:57 kscreenlocker_greet file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:535: TypeError: Cannot read property 'longName' of undefined 06/12/2021 01:57 systemd-sleep INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 06/12/2021 01:57 systemd-sleep Entering sleep state 'suspend'... 06/12/2021 01:57 kernel PM: suspend entry (s2idle) 06/12/2021 01:57 kernel Filesystems sync: 0.008 seconds 06/12/2021 01:57 kscreenlocker_greet qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_GB" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts") 06/12/2021 01:57 org_kde_powerdevil QObject::disconnect: Unexpected nullptr parameter 06/12/2021 01:57 org_kde_powerdevil QObject::disconnect: Unexpected nullptr parameter 06/12/2021 02:00 kernel Bluetooth: hci0: Timed out waiting for suspend events 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend timeout bit: 6 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend notifier action (3) failed: -110 06/12/2021 02:00 kernel Freezing user space processes ... (elapsed 0.003 seconds) done. 06/12/2021 02:00 kernel OOM killer disabled. 06/12/2021 02:00 kernel Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 06/12/2021 02:00 kernel printk: Suspending console(s) (use no_console_suspend to debug) 06/12/2021 02:00 kernel ACPI: EC: interrupt blocked 06/12/2021 02:00 kernel ACPI: EC: interrupt unblocked 06/12/2021 02:00 kernel OOM killer enabled. 06/12/2021 02:00 kernel Restarting tasks ... 06/12/2021 02:00 kernel mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) 06/12/2021 02:00 bluetoothd Controller resume with wake event 0x0 06/12/2021 02:00 systemd-sleep System returned from sleep state. 06/12/2021 02:00 systemd Started Timeline of Snapper Snapshots. 06/12/2021 02:00 kernel done. 06/12/2021 02:00 kernel PM: suspend exit 06/12/2021 02:00 systemd-sleep INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend 06/12/2021 02:00 systemd systemd-suspend.service: Deactivated successfully. 06/12/2021 02:00 systemd Finished System Suspend. 06/12/2021 02:00 systemd Stopped target Sleep. 06/12/2021 02:00 systemd Reached target Suspend. 06/12/2021 02:00 systemd Stopped target Suspend. 06/12/2021 02:00 systemd-logind Operation 'sleep' finished. So, probably problem in: 06/12/2021 02:00 kernel Bluetooth: hci0: Timed out waiting for suspend events 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend timeout bit: 6 06/12/2021 02:00 kernel Bluetooth: hci0: Suspend notifier action (3) failed: -110 (timed out) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1190411] New: USB devices missing after kexec reboot with XHCI enabled
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190411 Bug ID: 1190411 Summary: USB devices missing after kexec reboot with XHCI enabled Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: roger.whittaker(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852446 --> https://bugzilla.suse.com/attachment.cgi?id=852446&action=edit hwinfo, dmesg, usb-devices and lsusb with and without XHCI enabled in BIOS, normal boot and kexec boot Hardware is an Intel NUC (D54250WYK). With XHCI enabled in the UEFI BIOS, USB devices are not available after a kexec reboot. Hence the boot failed in the initrd when I had USB attached disks referenced in /etc/fstab. When I commented these out, the boot succeeded but the keyboard and mouse did not work after a kexec reboot. With XHCI disabled in the BIOS, kexec works as expected. On this hardware using Tumbleweed at some time in the past (but I'm afraid I don't know when) kexec worked with XHCI enabled. Linux jabberwock 5.14.0-1-default #1 SMP Mon Aug 30 07:01:36 UTC 2021 (dc06e24) x86_64 x86_64 x86_64 GNU/Linux NAME="openSUSE Tumbleweed" # VERSION="20210908" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20210908" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20210908" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo" -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1194187] New: openssl broken
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1194187 Bug ID: 1194187 Summary: openssl broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dleuenberger(a)suse.com Found By: --- Blocker: --- found this while debugging why my dehydrated job is erroring out. up2date Tumbleweed rpm -qa \*openssl\* libopenssl1_0_0-1.0.2u-6.2.x86_64 libopenssl1_0_0-steam-1.0.2u-6.2.x86_64 libopenssl1_0_0-steam-32bit-1.0.2u-6.2.x86_64 libopenssl1_1-32bit-1.1.1l-4.1.x86_64 openssl-1_1-1.1.1l-4.1.x86_64 libopenssl1_1-1.1.1l-4.1.x86_64 openssl-1.1.1l-1.2.noarch ``` Error configuring OpenSSL modules 139707710848960:error:08064066:object identifier routines:OBJ_create:oid exists:crypto/objects/obj_dat.c:698: 139707710848960:error:0D0AE0AB:asn1 encoding routines:oid_module_init:adding object:crypto/asn1/asn_moid.c:38: 139707710848960:error:0E07606D:configuration file routines:module_run:module initialization error:crypto/conf/conf_mod.c:177:module=oid_section, value=new_oids, retcode=-1 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 11