October 2023 - openSUSE Bugs - openSUSE Mailing Lists

[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 31 May '24

31 May '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 5

[Bug 1213915] New: Kernel panic - illegal instruction (4) at 7fffb6a4f874 nip 7fffb6a4f874 lr 7fffb6a4380c code 1 in ld64.so.2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213915 Bug ID: 1213915 Summary: Kernel panic - illegal instruction (4) at 7fffb6a4f874 nip 7fffb6a4f874 lr 7fffb6a4380c code 1 in ld64.so.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jrivrain(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868604 --> https://bugzilla.suse.com/attachment.cgi?id=868604&action=edit serial output All ppc64 Tumbleweed tests in Openqa are failing right now with a kernel panic. All the workers are on power8 cpus, this does not happen on a qemu emulated power9 cpu. Example of failing test: https://openqa.opensuse.org/tests/3476697 See attached serial output. -- You are receiving this mail because: You are on the CC list for the bug.

1 30

[Bug 1215172] New: VUL-0: croc: multiple security issues in croc
by bugzilla_noreply＠suse.com 28 May '24

28 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1215172 Bug ID: 1215172 Summary: VUL-0: croc: multiple security issues in croc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: jsmithfpv(a)gmail.com Reporter: matthias.gerstner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have reviewed the Croc codebase during the past month and have found a series of security issues, mostly in the area of a receiver of files which can be harmed by a malicious sender. There are now public GitHub issues about the most pressing issues: - possible creation of files in dangerous path location: https://github.com/schollz/croc/issues/593 - Interactive File Overwrite Prompt can be Circumvented by Sending ZIP file: https://github.com/schollz/croc/issues/594 - Escape Sequences in Filenames are not Filtered: https://github.com/schollz/croc/issues/595 - Use of Parts of the Shared Secret as Room Name: https://github.com/schollz/croc/issues/596 - Unencrypted "ips?" Message Leaks Information from the Sender Side: https://github.com/schollz/croc/issues/597 - Shared Secret Passed on Command Line Possibly Leaks to other Local Users: https://github.com/schollz/croc/issues/598 Nothing of this is currently fixed and it sounds like they also won't be fixed for a longer time, because the upstream author is lacking time to take care of this. As maintainers of croc you may be able to help out upstream to fix these issues or you may consider dropping this package from openSUSE until it becomes better. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1214653] New: yast2 keyboard do not allow to set bépo (french)
by bugzilla_noreply＠suse.com 27 May '24

27 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1214653 Bug ID: 1214653 Summary: yast2 keyboard do not allow to set bépo (french) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jonathan(a)mercier.paris QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Dear, I give a try to OpenSuse Leap 15, but I am unable to go further as they any way to set bépo layout kexyboard. I try from: 1. Leap installer : as bépo was missing I choose the french layout once installation has finished: 2. sudo yast2 keyboard: same layout proposal than given from installer 3. sudo yast2/zypper search : nothing relevant found The point (2) and (3) was done by trying to find each letter as I own only bépo keyboard. This layout is present on RHEL, RockyLinux 7,8,9 and Fedora. It would be much appreciate to add it Thanks best regards -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1214013] New: Shutdown did not finish (PC was not powered off, no obvious error logged)
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1214013 Bug ID: 1214013 Summary: Shutdown did not finish (PC was not powered off, no obvious error logged) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868645 --> https://bugzilla.suse.com/attachment.cgi?id=868645&action=edit Screenshot when shutdown should power off the PC Maybe the issue is related to an MD-RAID being verified (see Bug 1214004), but the system did not power off. The last message in journal were: Aug 05 01:47:01 pc.site systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Aug 05 01:47:01 pc.site systemd[1]: Stopping Device-mapper event daemon... Aug 05 01:47:01 pc.site dmeventd[1125]: dmeventd detected break while being idle for 0 second(s), exiting. Aug 05 01:47:01 pc.site dmeventd[1125]: dmeventd shutting down. Aug 05 01:47:01 pc.site systemd[1]: dm-event.service: Deactivated successfully. Aug 05 01:47:01 pc.site systemd[1]: Stopped Device-mapper event daemon. Aug 05 01:47:01 pc.site systemd[1]: Reached target System Shutdown. Aug 05 01:47:01 pc.site systemd[1]: Reached target Late Shutdown Services. Aug 05 01:47:01 pc.site systemd[1]: systemd-poweroff.service: Deactivated successfully. Aug 05 01:47:01 pc.site systemd[1]: Finished System Power Off. Aug 05 01:47:01 pc.site systemd[1]: Reached target System Power Off. Aug 05 01:47:01 pc.site systemd[1]: Shutting down. Aug 05 01:47:01 pc.site systemd-shutdown[1]: Syncing filesystems and block devices. Aug 05 01:47:03 pc.site systemd-shutdown[1]: Sending SIGTERM to remaining processes... Aug 05 01:47:03 pc.site haveged[1265]: haveged: Stopping due to signal 15 Aug 05 01:47:03 pc.site haveged[1265]: haveged starting up Aug 05 01:47:03 pc.site systemd-journald[1132]: Journal stopped I'm also adding a screenshot showing the last messages (that would last until I pressed the power button). Kernel was 5.14.21-150500.55.12-default The only other thing that looked unusual was this: ... Aug 05 01:46:59 pc.site systemd[1]: Stopped Record System Boot/Shutdown in UTMP. Aug 05 01:46:59 pc.site systemd[1]: Stopping Security Auditing Service... Aug 05 01:46:59 pc.site systemd-cryptsetup[3123]: Device cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 is still in use. Aug 05 01:46:59 pc.site systemd-cryptsetup[3123]: Failed to deactivate: Device or resource busy Aug 05 01:46:59 pc.site systemd[1]: systemd-cryptsetup@cr_md\x2duuid\x2dfe1588c4:a2140388:5b4117ba:4e4339b9\x2dpart5.service: Control process exited, code=exited, status=1> Aug 05 01:46:59 pc.site systemd[1]: systemd-cryptsetup@cr_md\x2duuid\x2dfe1588c4:a2140388:5b4117ba:4e4339b9\x2dpart5.service: Failed with result 'exit-code'. Aug 05 01:46:59 pc.site systemd[1]: Stopped Cryptography Setup for cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5. Aug 05 01:46:59 pc.site auditd[1679]: The audit daemon is exiting. Aug 05 01:46:59 pc.site kernel: kauditd_printk_skb: 50 callbacks suppressed Aug 05 01:46:59 pc.site kernel: audit: type=1305 audit(1691192819.741:562): op=set audit_pid=0 old=1679 auid=4294967295 ses=4294967295 subj=unconfined res=1 Aug 05 01:46:59 pc.site auditctl[3127]: enabled 0 Aug 05 01:46:59 pc.site auditctl[3127]: failure 1 Aug 05 01:46:59 pc.site auditctl[3127]: pid 0 Aug 05 01:46:59 pc.site auditctl[3127]: rate_limit 0 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_limit 64 Aug 05 01:46:59 pc.site auditctl[3127]: lost 0 Aug 05 01:46:59 pc.site auditctl[3127]: backlog 1 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_wait_time 15000 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_wait_time_actual 0 Aug 05 01:46:59 pc.site auditctl[3127]: No rules Aug 05 01:46:59 pc.site kernel: audit: type=1305 audit(1691192819.853:563): op=set audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=unconfined res=1 Aug 05 01:46:59 pc.site systemd[1]: auditd.service: Deactivated successfully. Aug 05 01:46:59 pc.site systemd[1]: Stopped Security Auditing Service. Aug 05 01:46:59 pc.site systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully. Aug 05 01:46:59 pc.site systemd[1]: Stopped Create Volatile Files and Directories. Aug 05 01:47:00 pc.site systemd[1]: dracut-shutdown.service: Deactivated successfully. Aug 05 01:47:00 pc.site systemd[1]: Stopped Restore /run/initramfs on shutdown. Aug 05 01:47:00 pc.site systemd[1]: Stopped target Local File Systems. Aug 05 01:47:00 pc.site systemd[1]: Unmounting /home... ... The LUKS device cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 contains the PV for the system VG, so it makes no sense trying to deactivate that before unmounting the system filesystems. Layout is like this: # pvs PV VG Fmt Attr PSize PFree /dev/mapper/cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 system lvm2 a-- 199,98g 3,88g # vgs VG #PV #LV #SN Attr VSize VFree system 1 6 0 wz--n- 199,98g 3,88g # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert android system Vwi-aotz-- 50,00g thinpool 55,19 floppies system Vwi-a-tz-- 1,00g thinpool 15,18 home system -wi-ao---- 50,00g root system -wi-ao---- 32,00g swap system -wi-ao---- 4,00g thinpool system twi-aotz-- 110,00g 25,23 22,76 (System was upgraded from Leap 15.4 where shutdown worked) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213055] New: locale problems in the default distrobox configuration
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213055 Bug ID: 1213055 Summary: locale problems in the default distrobox configuration Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: All OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Distrobox Assignee: rbrown(a)suse.com Reporter: shadenk30011(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Build Identifier: When creating a new container using "distrobox-create" the container fails to display directory names properly. For example the directory named "Stažené" shows up as "'Sta'$'\305\276''en'$'\303\251'" when using ls. Reproducible: Always Steps to Reproduce: 1. Use the czech locale 2. Create a directory inside the home that uses one of the offending symbols 3. Create a new distrobox container and run "ls" Actual Results: Directory name isn't properly displayed. Expected Results: Directory name is properly displayed. A workaround is to install the "glibc-locale" package. This can be automated by adding 'container_additional_packages="glibc-locale"' into the distrobox configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1215622] New: iscsiuio - Couldn't mmap registers: Invalid argument
by bugzilla_noreply＠suse.com 21 May '24

21 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1215622 Bug ID: 1215622 Summary: iscsiuio - Couldn't mmap registers: Invalid argument Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to set up an iscsi initiator (in yast) using a bnx2 offload engine, I wasn't getting very far, see bug#1215621. I kept getting this error: iscsiadm: Could not set host net params (err 29) I ran iscsiuio with debug level 4 and noticed the following error msg: Couldn't mmap registers: Invalid argument After some research, I rebooted the machine with "iomem=relaxed" - now it works: anton:~ # iscsiadm -m discovery -P 1 -t st -I eth4-bnx2i -p 10.42.8.10:3260 iscsiadm: Could not set host net params (err 29) iscsiadm: Connection to discovery portal 10.42.8.10 failed: operation failed but retry may succeed Target: iqn.2023-09.local.rz2:opensuse-mirror Portal: 10.42.8.10:3260,1 Iface Name: eth4-bnx2i Target: iqn.2023-09.local.rz2:webspace Portal: 10.42.8.10:3260,1 Iface Name: eth4-bnx2i -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1212897] New: Produce separate Aeon installation media
by bugzilla_noreply＠suse.com 18 May '24

18 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1212897 Bug ID: 1212897 Summary: Produce separate Aeon installation media Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Aeon requires install media separate from MicroOS -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215462] New: drbd.service: Failed at step EXEC spawning /lib/drbd/scripts/drbd: No such file or directory
by bugzilla_noreply＠suse.com 17 May '24

17 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1215462 Bug ID: 1215462 Summary: drbd.service: Failed at step EXEC spawning /lib/drbd/scripts/drbd: No such file or directory Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: nsinger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With the drbd-utils update to 9.19.0 on Mon Oct 11 09:43:25 UTC 2021 the /lib/drbd/scripts/drbd directory was moved to /usr (see line#130 in https://build.opensuse.org/package/view_file/network:ha-clustering:Factory/…). Soon later a fix for bsc#1203220 was introduced because drbd.service now fails with `drbd.service: Failed at step EXEC spawning /lib/drbd/scripts/drbd: No such file or directory` and a symlink to /usr was created. Apparently this fix never made it into Leap15.4 backports: ``` osiris-1:~ # cat /etc/os-release NAME="openSUSE Leap" VERSION="15.4" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.4" PRETTY_NAME="openSUSE Leap 15.4" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.4" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap" LOGO="distributor-logo-Leap" osiris-1:~ # LC_ALL=c zypper info drbd-utils Retrieving repository 'Update repository with updates from SUSE Linux Enterprise 15' metadata ......................................................................................................................................[done] Building repository 'Update repository with updates from SUSE Linux Enterprise 15' cache ...........................................................................................................................................[done] Loading repository data... Reading installed packages... Information for package drbd-utils: ----------------------------------- Repository : Update repository with updates from SUSE Linux Enterprise 15 Name : drbd-utils Version : 9.19.0-150400.3.17.1 Arch : x86_64 Vendor : SUSE LLC <https://www.suse.com/> Installed Size : 1.9 MiB Installed : Yes Status : up-to-date Source package : drbd-utils-9.19.0-150400.3.17.1.src Upstream URL : http://www.drbd.org/ Summary : Distributed Replicated Block Device Description : Drbd is a distributed replicated block device. It mirrors a block device over the network to another machine. Think of it as networked raid 1. It is a building block for setting up clusters. ``` Workaround: `mkdir -p /lib/drbd/ && ln -s /usr/lib/drbd/scripts /lib/drbd/scripts` -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215621] New: iscsi initiator setup problem
by bugzilla_noreply＠suse.com 16 May '24

16 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1215621 Bug ID: 1215621 Summary: iscsi initiator setup problem Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: per(a)computer.org QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I am trying to set up an iscsi initiator using a bnx2 offload device. I am seeing a couple of issues. a) IscsiClientLib.rb - uses ifconfig, which is deprecated. Line 1786. Can be worked around by installing "net-tools-deprecated". See also bug#1215537 b) when trying to connect to a target, I get this error: Connection to discovery portal 10.42.8.10 failed: internal error Error output: iscsiadm: Please set the iface.ipaddress for iface eth4-bnx2i, then retry the login command. c) after having set "iface.ipaddress" manually and retrying the connection: iscsiadm: Could not set host net params (err 29) I believe the above is due to an issue in iscsiuio, I'll open a separate ticket on that. -- You are receiving this mail because: You are on the CC list for the bug.

1 9