October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 1200962] New: binutils-gold drop affects ARM architectures
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1200962 Bug ID: 1200962 Summary: binutils-gold drop affects ARM architectures 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- there have been some "drop binutils-gold dependency cause it is unneeded" and "because it is unmaintained" submitrequests, and now ghc is broken: [ 31s] configure: error: Your linker is affected by binutils #16177, which [ 31s] critically breaks linkage of GHC objects. Please either upgrade [ 31s] binutils or supply a different linker with the LD environment [ 31s] variable. can you please include the patch then? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1188589] New: libbpf: failed to find valid kernel BTF
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1188589 Bug ID: 1188589 Summary: libbpf: failed to find valid kernel BTF 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: mrostecki(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the update to the TW snapshot with the kernel 5.13.2-1, I see the following errors when trying to load BPF CO-RE skeletons with libbpf: libbpf: failed to find valid kernel BTF libbpf: Error loading vmlinux BTF: -3 The full example - I'm trying to load BPF programs which I have in this project: https://github.com/rancher-sandbox/lockc and the full output is: �� sudo ./out/lockcd libbpf: elf: skipping unrecognized data section(9) .rodata.str1.1 libbpf: failed to find valid kernel BTF libbpf: Error loading vmlinux BTF: -3 libbpf: failed to load object 'lockc_bpf' libbpf: failed to load BPF skeleton 'lockc_bpf': -3 Error: libbpf error Caused by: System error, errno: 3 Most likely, the solution for them would be setting the following kernel parameters to "y": CONFIG_DEBUG_INFO_REDUCED CONFIG_DEBUG_INFO_SPLIT But I'm not entirely sure yet. trying to test that... -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1190539] New: scsi host0: uas_eh_device_reset_handler
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1190539 Bug ID: 1190539 Summary: scsi host0: uas_eh_device_reset_handler Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mkrapp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I got a new ASUS Zenbook 14 UM524UA. It has two USB-c and one USB-A sockets. An external SATA M2 disk connected to the USB-A Port does not mount, but uas_device_reset happens frequently and the disk is not usable: 22:43:03 susi kernel: usb 4-2: new SuperSpeed USB device number 6 using xhci_hcd 22:43:03 susi kernel: usb 4-2: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 22:43:03 susi kernel: usb 4-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 22:43:03 susi kernel: usb 4-2: Product: ASM105x 22:43:03 susi kernel: usb 4-2: Manufacturer: ASMT 22:43:03 susi kernel: usb 4-2: SerialNumber: ACDFD0000000000007B4 22:43:03 susi kernel: scsi host0: uas 22:43:03 susi kernel: scsi 0:0:0:0: Direct-Access ASMT 2115 0 PQ: 0 ANSI: 6 22:43:03 susi kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 22:43:03 susi kernel: sd 0:0:0:0: [sda] 937721856 512-byte logical blocks: (480 GB/447 GiB) 22:43:03 susi kernel: sd 0:0:0:0: [sda] Write Protect is off 22:43:03 susi kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 22:43:03 susi kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA 22:43:03 susi kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes 22:43:03 susi kernel: sda: sda1 22:43:03 susi kernel: sd 0:0:0:0: [sda] Attached SCSI disk 22:43:36 susi kernel: sd 0:0:0:0: [sda] tag#16 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 22:43:36 susi kernel: sd 0:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 00 00 00 78 00 00 08 00 22:43:36 susi kernel: scsi host0: uas_eh_device_reset_handler start 22:43:36 susi kernel: usb 4-2: reset SuperSpeed USB device number 6 using xhci_hcd 22:43:36 susi kernel: scsi host0: uas_eh_device_reset_handler success 22:44:04 susi systemd-udevd[713]: sda: Worker [14902] processing SEQNUM=4825 is taking a long time 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#4 CDB: Read(10) 28 00 00 00 01 08 00 00 f8 00 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 00 00 00 88 00 00 78 00 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN 22:44:06 susi kernel: sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 00 00 00 48 00 00 30 00 22:44:07 susi kernel: scsi host0: uas_eh_device_reset_handler start 22:44:07 susi kernel: usb 4-2: reset SuperSpeed USB device number 6 using xhci_hcd 22:44:07 susi kernel: scsi host0: uas_eh_device_reset_handler success 22:44:37 susi kernel: scsi host0: uas_eh_device_reset_handler start 22:44:37 susi kernel: sd 0:0:0:0: [sda] tag#1 uas_zap_pending 0 uas-tag 2 inflight: CMD 22:44:37 susi kernel: sd 0:0:0:0: [sda] tag#1 CDB: Read(10) 28 00 00 00 00 88 00 00 78 00 22:44:37 susi kernel: sd 0:0:0:0: [sda] tag#2 uas_zap_pending 0 uas-tag 3 inflight: CMD 22:44:37 susi kernel: sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 00 00 01 08 00 00 f8 00 22:44:37 susi kernel: usb 4-2: reset SuperSpeed USB device number 6 using xhci_hcd 22:44:37 susi kernel: scsi host0: uas_eh_device_reset_handler success 22:45:08 susi kernel: scsi host0: uas_eh_device_reset_handler start 22:45:08 susi kernel: sd 0:0:0:0: [sda] tag#3 uas_zap_pending 0 uas-tag 1 inflight: CMD 22:45:08 susi kernel: sd 0:0:0:0: [sda] tag#3 CDB: Read(10) 28 00 00 00 01 08 00 00 f8 00 22:45:08 susi kernel: sd 0:0:0:0: [sda] tag#5 uas_zap_pending 0 uas-tag 2 inflight: CMD 22:45:08 susi kernel: sd 0:0:0:0: [sda] tag#5 CDB: Read(10) 28 00 00 00 00 88 00 00 78 00 22:45:08 susi kernel: usb 4-2: reset SuperSpeed USB device number 6 using xhci_hcd 22:45:08 susi kernel: scsi host0: uas_eh_device_reset_handler success /dev/sda1 is not mountable (xfs) and fdisk hangs, disk is not usable -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1202395] New: BTRFS subvolume attr change even if subvolume is set to RO
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1202395 Bug ID: 1202395 Summary: BTRFS subvolume attr change even if subvolume is set to RO Classification: openSUSE Product: openSUSE Leap Micro Version: 5.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: screening-team-bugs(a)suse.de Reporter: rgoldwyn(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- From bug#1156421c#40 Plain openSUSE MicroOS installation with SELinux enabled (default), the root filesystem is a read-only btrfs subvolume: microos:~ # mount -o remount,rw / microos:~ # /sbin/restorecon -F -R -v /usr/ Relabeled /usr/lib64/gconv/gconv-modules.cache from unconfined_u:object_r:lib_t:s0 to system_u:object_r:lib_t:s0 microos:~ # touch /usr/lib64/gconv/gconv-modules.cache touch: cannot touch '/usr/lib64/gconv/gconv-modules.cache': Read-only file system microos:~ # ls -alFZ /usr/lib64/gconv/gconv-modules.cache -rw-r--r--. 1 root root system_u:object_r:lib_t:s0 26988 Aug 11 09:02 /usr/lib64/gconv/gconv-modules.cache Also, on my system, the following happens: # mount -o remount,rw / # setfattr -n "security.selinux" -v "system_u:object_r:lib_t:s0" /usr/lib64/gconv/gconv-modules.cache micro2:/home/goldwyn # btrfs property get / ro ro=true -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1198731] New: libmount: when moving a mounted tree, all mounted sub tree entries in utab should also be updated
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1198731 Bug ID: 1198731 Summary: libmount: when moving a mounted tree, all mounted sub tree entries in utab should also be updated 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 Found By: --- Blocker: --- This has been reported to upstream too: https://github.com/systemd/systemd/issues/15266 I created this bug to make sure that both openSUSE distros and SLE ones will be fixed once it will be solved by upstream. The problem has been discovered when addressing bsc#1175850, which depends on the resolution of the reported issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 19