June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1219841] New: dracut: segfault with rd.break option
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1219841 Bug ID: 1219841 Summary: dracut: segfault with rd.break option Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: dracut-maintainers(a)suse.de Reporter: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Commit https://github.com/openSUSE/dracut/commit/3950f801e26a3aeb1e3bc91e31c7fd459… fixed a regression with multiple `rd.break=` options set on the kernel command line. But, it detected a call to `strcmp` without checking that the arguments are not NULL first, which causes a segfault when passing the `rd.break` option without value on the kernel command line. > Feb 12 11:37:23 localhost systemd[1]: Starting dracut cmdline hook... > Feb 12 11:37:23 localhost dracut-cmdline[237]: dracut-059+suse.538.ge7a5cff9-1.3 > Feb 12 11:37:23 localhost dracut-cmdline[237]: Using kernel command line parameters: rd.driver.pre=btrfs resume=UUID=de0a0a36-ef3b-4935-aae6-209c689c0dd2 root=UUID=5594bae0-44c9-49e5-b17b-8ef41682899e rootfstype=btrfs rootflags=rw,relatime,discard=async,space_cache=v2,subvolid=266,subvol=/@/.snapshots/1/snapshot,subvol=@/.snapshots/1/snapshot BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=UUID=5594bae0-44c9-49e5-b17b-8ef41682899e console=tty0 console=ttyS0,9600 security=apparmor mitigations=auto rd.break > Feb 12 11:37:23 localhost kernel: dracut-getargs[279]: segfault at 0 ip 00007f88b1c88726 sp 00007ffc3fbefc98 error 4 in libc.so.6[7f88b1b31000+16d000] likely on CPU 0 (core 0, socket 0) > Feb 12 11:37:23 localhost kernel: Code: 1f 44 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 66 90 89 f8 09 f0 c1 e0 14 3d 00 00 00 f8 0f 87 1a 03 00 00 <62> e1 fe 28 6f 07 62 b2 7d 20 26 d0 62 f1 7d 22 74 0e c5 fb 93 c9 > Feb 12 11:37:23 localhost systemd-coredump[280]: Failed to connect to coredump service: No such file or directory > Feb 12 11:37:23 localhost systemd[1]: Finished dracut cmdline hook. > Feb 12 11:37:23 localhost systemd[1]: Starting dracut pre-udev hook... > Feb 12 11:37:23 localhost kernel: dracut-getargs[315]: segfault at 0 ip 00007f2d52753726 sp 00007ffd0a7f8f78 error 4 in libc.so.6[7f2d525fc000+16d000] likely on CPU 1 (core 0, socket 1) However these segfaults are not critical, because it happens on a separate C binary used to parse the kernel command line, so the system boots anyway. Fix to be backported: https://github.com/dracutdevs/dracut/pull/2607/commits/b9d395a373a1da0e869d… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1217083] New: snapshot 20231107 --> 20231108 boot fails
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1217083 Bug ID: 1217083 Summary: snapshot 20231107 --> 20231108 boot fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: roeland.jansen(a)sue.nl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recently I updated 23031107 to 20231108 on two laptops running legacy boot. Both hang some time at console plymouth stuff. dracut then comes up with the inability to find /dev/system/root. It ends up in the dracut emergency shell. in the shell, lvm pvscan will report no physical volumes. It also happens on a virtual machine. (also not UEFI). If I try to recover with an usb stick, no partitions are shown. If I show "all", the installed system is being identified als unknown, architecture unknown. (and yes it's a 64 bit TW stick). I could not recover them anymore. Also, on one of the laptops, grub does not show windosws anmore, the other does. I luckily have a snapshot on my work vm so I can revert back. The following packages are updated when this happens. alsa alsa-devel code kernel-firmware-all kernel-firmware-amdgpu kernel-firmware-ath10k kernel-firmware-ath11k kernel-firmware-atheros kernel-firmware-bluetooth kernel-firmware-bnx2 kernel-firmware-brcm kernel-firmware-chelsio kernel-firmware-dpaa2 kernel-firmware-i915 kernel-firmware-intel kernel-firmware-iwlwifi kernel-firmware-liquidio kernel-firmware-marvell kernel-firmware-media kernel-firmware-mediatek kernel-firmware-mellanox kernel-firmware-mwifiex kernel-firmware-network kernel-firmware-nfp kernel-firmware-nvidia kernel-firmware-platform kernel-firmware-prestera kernel-firmware-qcom kernel-firmware-qlogic kernel-firmware-radeon kernel-firmware-realtek kernel-firmware-serial kernel-firmware-sound kernel-firmware-ti kernel-firmware-ueagle kernel-firmware-usb-network libasound2 libatopology2 libbrotli-devel libbrotlicommon1 libbrotlicommon1-x86-64-v3 libbrotlidec1 libbrotlidec1-x86-64-v3 libbrotlienc1 libbrotlienc1-x86-64-v3 libbytesize-lang libbytesize1 libgusb2 libnghttp2-14 libsqlite3-0 libsqlite3-0-x86-64-v3 libsvn_auth_kwallet-1-0 libxxhash0 openSUSE-release openSUSE-release-appliance-custom openSUSE-release-ftp sqlite3-devel sqlite3-tcl subversion subversion-bash-completion subversion-perl sysuser-shadow ucode-amd wmctrl I tried by mounting in rescue, created a new grub.cfg where osprober does not show windows anymore. The interesting part is that dracut -f will as last line shows "adding boot menu entry for UEFI firmware settings" Basically I will end up in reinstalling windows and linux on both laptops. (in legacy boot) If needed, I can install the non-kernel parts and see what package eventualy triggers this. -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1219767] New: nullok option of pam_unix doesn't work as expected when logging in via a tty with an empty password
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1219767 Bug ID: 1219767 Summary: nullok option of pam_unix doesn't work as expected when logging in via a tty with an empty password Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- To allow a user to log in with an empty password, the option "nullok" of pam_unix is added in /etc/pam.d/common-auth: auth required pam_env.so auth optional pam_gnome_keyring.so auth required pam_unix.so try_first_pass nullok auth required pam_ecryptfs.so unwrap But when trying to log in via tty1 with user "foo" who has an empty password, login still prompts for a password. It appears that pam_gnome_keyring is interfering in the process of authentication cancelling the effect of nullok. Indeed after commenting the line with pam_gnome_keyring.so, the login process works as expect and there's no more password prompt. Please note that in this scenario gnome/gdm is not involved at all (the system was booted with multi-user.target target)so I don't really see why pam_gnome_keyring interferes here. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1216717] New: suse-module-tools: 60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1216717 Bug ID: 1216717 Summary: suse-module-tools: 60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: martin.wilck(a)suse.com Reporter: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Just in case this wasn't reported yet, this error is logged in the journal of a Tumbleweed system with crypto_LUKS devices: Oct 30 15:46:46 localhost (udev-worker)[724]: dm-0: /usr/lib/udev/rules.d/60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-0/queue/scheduler}, ignoring: No such file or directory Oct 30 15:46:48 localhost (udev-worker)[723]: dm-1: /usr/lib/udev/rules.d/60-io-scheduler.rules:37 Failed to write ATTR{/sys/devices/virtual/block/dm-1/queue/scheduler}, ignoring: No such file or directory # uname -r 6.5.9-1-default # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-1/queue /sys/devices/virtual/block/dm-0/queue # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue/scheduler /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler Not happening in systems with a similar setup using previous kernel versions: - ALP Dolomite Build6.8 localhost:~ # uname -r 6.4.11-1-default localhost:~ # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-0/queue localhost:~ # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler /sys/devices/virtual/block/dm-0/queue/scheduler - Leap 15.5 # uname -r 5.14.21-150500.53-default # find /sys/devices -name "queue" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue /sys/devices/virtual/block/dm-0/queue # find /sys/devices -name "scheduler" /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/queue/scheduler /sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/queue/scheduler /sys/devices/virtual/block/dm-0/queue/scheduler I don't know if it's a kernel bug or if the udev rule needs to be adjusted. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1215586] New: guestfs regression: non functional network due to missing sysconfig-netconfig
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1215586 Bug ID: 1215586 Summary: guestfs regression: non functional network due to missing sysconfig-netconfig Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- At some point in the past, virt-builder and other tools had proper networking with-in the appliance. This still works by luck in SLE15, but it broke in Tumbleweed. The reason is the transformation of appliance/packagelist.in into /usr/lib64/guestfs/supermin.d/packages. During build the packagelist is passed to supermin, which writes the packages file. In case a package is unavailable during build, it will be missing from the packages file. Also 'systemd' is transformed into 'systemd-mini' (which is not really an issue because other packages require 'systemd'). In case of networking: if the host does not have 'dhcp-client' installed, the network will not start inside the appliance. Once dhcp-client gets installed, it will be put into the appliance. But the dhcp-client scripts expect a functional /sbin/netconfig, which is provided by sysconfig-netconfig. That package is listed in packagelist.in, but will not be written to packages because it is not in BuildRequires. I think most packages from packagelist.in are "lost" during build because they are not in BuildRequires, or because nothing requires them. It feels wrong to put each and every binary which is potentially called by guestfsd into BuildRequires. Instead the "packages" file should be overwritten manually with the list of packages which may be used, if it is installed on the host. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1216355] New: Packman Discord package upgrade lockout defeat inoperative.
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1216355 Bug ID: 1216355 Summary: Packman Discord package upgrade lockout defeat inoperative. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: rskunath(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is a script in the Packman Discord srpm package (0.0.31-1699.98.pm.1) that is supposed to defeat the upgrade check that Discord does when they release a new version. This pops up a box to grab a deb or a tarball to update outside the Suse system. This script that is in the rpm spec file apparently has not worked for a while. I don't know if it can work, but it is in there and inoperative. The idea according to the script is to bypass the update check lockout and give the package maintainer time to update the Discord package without locking users out of Discord until that is done. This is a very good idea. In the last few Discord update cycles the box pops up and at that point you can't start Discord until the new package is released by the package maintainer. I did see a while ago a forum post about bumping the JSON file revision number by one version to get around this manually: (/usr/lib64/discord/resources and edit the build_info.json file) This appears to work but it's a kludge and the script is a better and a more appropriate way to do this if doing it is still possible. I'm just passing along the discovery and hoping defeating the lockout is still possible. I use Discord daily on the Suse Discord and users getting locked out is disconcerting. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219892] New: Try to generate xorg-x11-server-sdk package from xwayland sources
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1219892 Bug ID: 1219892 Summary: Try to generate xorg-x11-server-sdk package from xwayland sources Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- For the future I expect much more version updates for xwayland than for xorg-x11-server, since the former is still actively used and released, while for the latter only security fixes are released. Therefore we should figure out if it wouldn't be possible to extract the generic xserver sources (currently xorg-x11-server-sdk subpackage of xorg-x11-server) out of xwayland sources instead of xorg-x11-server sources. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1226930] New: libzypp-zypper won't install because LibreOffice is held back
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226930 Bug ID: 1226930 Summary: libzypp-zypper won't install because LibreOffice is held back Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: rrwidell(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875683 --> https://bugzilla.suse.com/attachment.cgi?id=875683&action=edit screenshots of failing update libzypp/zypper etc. won't install because I have held LibreOffice at 7.5.4. I have done this because there is an unresolved formatting error in 24.2 Since I have 7.5.4 protected, attempts to update LibreOffice to 24.2 fail, which is fine. But today, updates to libzypp, zypper & other related components failed because I'm holding back LibreOffice. See attached screenshots. Thanks, ron -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1222018] New: Flatpak is not showing up as an installation source in GNOME Software 46
by bugzilla_noreply＠suse.com 19 Aug '24

19 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1222018 Bug ID: 1222018 Summary: Flatpak is not showing up as an installation source in GNOME Software 46 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: 95kreaninw95(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading to GNOME 46, I can't install Flatpak apps as I can't choose the installation source to Flatpak (Flathub repo - dl.flathub.org) I have reported this issue at GNOME Software repo: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2443#note_2059899 But it seems everything on their side is normal. There's nothing wrong with the log. So, my conclusion is that openSUSE's GNOME Software package (https://build.opensuse.org/package/show/openSUSE:Factory/gnome-software) could be the cause of the issue. I tried reinstalling GNOME Software, but it didn't fix this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1227202] New: zypper: symbol lookup error: /usr/lib64/libzypp.so.1734: undefined symbol: _ZN6google8protobuf8internal14UntypedMapBase12TransferTreeEPN4absl12lts_202401169btree_mapINS1_10VariantKeyEPNS1_8NodeBaseESt4lessIS6_ENS1_12MapAllocatorISt4pairIKS6_S8_EEEEEPFS6_S
by bugzilla_noreply＠suse.com 17 Aug '24

17 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227202 Bug ID: 1227202 Summary: zypper: symbol lookup error: /usr/lib64/libzypp.so.1734: undefined symbol: _ZN6google8protobuf8internal14UntypedMapBase12Transfer TreeEPN4absl12lts_202401169btree_mapINS1_10VariantKeyE PNS1_8NodeBaseESt4lessIS6_ENS1_12MapAllocatorISt4pairI KS6_S8_EEEEEPFS6_S Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Critical Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: anton.smorodskyi(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- 1. Install this packages : ``` # rpm -qa --last | grep "Thu Jun 27" [17:14:56] libyui-ncurses-pkg16-4.5.3-150500.3.7.9.x86_64 Thu Jun 27 20:12:48 2024 PackageKit-backend-zypp-1.2.4-150400.3.17.10.x86_64 Thu Jun 27 20:12:48 2024 zypper-1.14.73-150500.6.2.1.x86_64 Thu Jun 27 20:12:47 2024 yast2-pkg-bindings-4.5.3-150500.3.7.17.x86_64 Thu Jun 27 20:12:47 2024 libzypp-17.34.1-150500.6.2.1.x86_64 Thu Jun 27 20:12:47 2024 libyui-qt-pkg16-4.5.3-150500.3.7.9.x86_64 Thu Jun 27 20:12:47 2024 libsolv-tools-base-0.7.29-150400.3.22.4.x86_64 Thu Jun 27 20:12:46 2024 libsolv-tools-0.7.29-150400.3.22.4.x86_64 Thu Jun 27 20:12:46 2024 ``` 2. ANY execution of zypper ( even zypper --help ) end up with error : zypper: symbol lookup error: /usr/lib64/libzypp.so.1734: undefined symbol: _ZN6google8protobuf8internal14UntypedMapBase12TransferTreeEPN4absl12lts_202401169btree_mapINS1_10VariantKeyEPNS1_8NodeBaseESt4lessIS6_ENS1_12MapAllocatorISt4pairIKS6_S8_EEEEEPFS6_S8_E -- You are receiving this mail because: You are on the CC list for the bug.

1 3