March 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1240405] New: unexpected "Unit Not Ready" for USB-attached NVME SSD
by bugzilla_noreply＠suse.com 08 May '25

08 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1240405 Bug ID: 1240405 Summary: unexpected "Unit Not Ready" for USB-attached NVME SSD Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have an external USB NVME SSD that unexpectedly reports a "Unit Not Ready" like this: kernel: usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0562, bcdDevice=31.02 ... kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) ... kernel: usbcore: registered new interface driver usb-storage ... kernel: scsi host0: uas ... kernel: scsi 0:0:0:0: Direct-Access Lexar 25 6GB SSD 3102 PQ: 0 ANSI: 6 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 kernel: sd 0:0:0:0: [sda] Unit Not Ready kernel: sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] kernel: sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 ... kernel: sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK kernel: sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] kernel: sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 kernel: usb 1-9: new full-speed USB device number 4 using xhci_hcd kernel: usb 1-9: New USB device found, idVendor=2ce3, idProduct=9563, bcdDevice= 1.20 kernel: usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0 kernel: usb 1-9: Product: EMV Smartcard Reader kernel: usb 1-9: Manufacturer: Generic kernel: sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK kernel: sd 0:0:0:0: [sda] Sense Key : Hardware Error [current] kernel: sd 0:0:0:0: [sda] ASC=0x44 <<vendor>>ASCQ=0x81 kernel: sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B) kernel: sd 0:0:0:0: [sda] 0-byte physical blocks kernel: typec port1: bound usb1-port6 (ops connector_ops [usbcore]) kernel: typec port1: bound usb4-port2 (ops connector_ops [usbcore]) kernel: usb 1-14: new full-speed USB device number 5 using xhci_hcd kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) kernel: usb 1-14: New USB device found, idVendor=8087, idProduct=0033, bcdDevice= 0.00 kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0 kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) kernel: sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled kernel: sd 0:0:0:0: [sda] Asking for cache data failed kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes not a multiple of physical block size (0 bytes) kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes) kernel: sd 0:0:0:0: [sda] Attached SCSI disk ... The device is connected to a Thunderbold 4 port using a Thunderbolt 4 cable. After re-plugging the device I saw: kernel: usb 4-1: USB disconnect, device number 2 kernel: usb 4-1: new SuperSpeed Plus Gen 2x1 USB device number 3 using xhci_hcd kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0562, bcdDevice=31.02 kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: usb 4-1: Product: USB 3.1 Storage Device kernel: usb 4-1: Manufacturer: JMicron kernel: usb 4-1: SerialNumber: XXXXXXXXXX kernel: scsi host0: uas kernel: scsi 0:0:0:0: Direct-Access Lexar 25 6GB SSD 3102 PQ: 0 ANSI: 6 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 kernel: sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB) kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks kernel: sd 0:0:0:0: [sda] Write Protect is off kernel: sd 0:0:0:0: [sda] Mode Sense: 5f 00 00 08 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes) kernel: sda: sda1 sda2 sda3 sda4 kernel: sd 0:0:0:0: [sda] Attached SCSI disk boltd[2462]: probing: started [1000] mtp-probe[13605]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/0000:20:00.0/0000:21:02.0/0000:48:00.0/usb4/4-1" boltd[2462]: probing: timeout, done: [2990661] (2000000) mtp-probe[13605]: bus: 4, device: 3 was not an MTP device boltd[2462]: probing: started [1000] mtp-probe[13654]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/0000:20:00.0/0000:21:02.0/0000:48:00.0/usb4/4-1" mtp-probe[13654]: bus: 4, device: 3 was not an MTP device ... So after re-plugging it worked. Maybe the BIOS of the laptop set the device into the mode it had on boot. Some details on the USB bridge: us 004 Device 002: ID 152d:0562 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.20 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x152d JMicron Technology Corp. / JMicron USA Technology Corp. idProduct 0x0562 JMS567 SATA 6Gb/s bridge bcdDevice 31.02 iManufacturer 1 JMicron iProduct 2 USB 3.1 Storage Device ... Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 1 bNumEndpoints 4 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 98 iInterface 10 MSC USB Attached SCSI Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 0 Command pipe (0x01) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 0 MaxStreams 32 Status pipe (0x02) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 MaxStreams 32 Data-in pipe (0x03) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 MaxStreams 32 Data-out pipe (0x04) Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 0x002a bNumDeviceCaps 3 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType 16 bDevCapabilityType 2 bmAttributes 0x00000f0e BESL Link Power Management (LPM) Supported BESL value 3840 us SuperSpeed USB Device Capability: bLength 10 bDescriptorType 16 bDevCapabilityType 3 bmAttributes 0x00 wSpeedsSupported 0x000e Device can operate at Full Speed (12Mbps) Device can operate at High Speed (480Mbps) Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 1 Lowest fully-functional device speed is Full Speed (12Mbps) bU1DevExitLat 10 micro seconds bU2DevExitLat 32 micro seconds SuperSpeedPlus USB Device Capability: bLength 20 bDescriptorType 16 bDevCapabilityType 10 bmAttributes 0x00000001 Sublink Speed Attribute count 1 Sublink Speed ID count 0 wFunctionalitySupport 0x1100 bmSublinkSpeedAttr[0] 0x000a4030 Speed Attribute ID: 0 10Gb/s Symmetric RX SuperSpeedPlus bmSublinkSpeedAttr[1] 0x000a40b0 Speed Attribute ID: 0 10Gb/s Symmetric TX SuperSpeedPlus Device Status: 0x000c (Bus Powered) U1 Enabled U2 Enabled Some data from the NVME: === START OF INFORMATION SECTION === Model Number: Lexar 256GB SSD Serial Number: KXXXXXXXXXXXX Firmware Version: V1.10.1 PCI Vendor ID: 0x1b4b PCI Vendor Subsystem ID: 0x1d97 IEEE OUI Identifier: 0x000000 Total NVM Capacity: 256,060,514,304 [256 GB] Unallocated NVM Capacity: 0 Controller ID: 0 NVMe Version: 1.3 Number of Namespaces: 1 Namespace 1 Size/Capacity: 256,060,514,304 [256 GB] Namespace 1 Formatted LBA Size: 512 Local Time is: Mon Mar 31 20:27:10 2025 CEST Firmware Updates (0x02): 1 Slot Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x0045): Comp DS_Mngmt Timestmp Log Page Attributes (0x0a): Cmd_Eff_Lg Telmtry_Lg Maximum Data Transfer Size: 32 Pages Warning Comp. Temp. Threshold: 84 Celsius Critical Comp. Temp. Threshold: 91 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 7.00W - - 0 0 0 0 5 5 1 + 5.20W - - 1 1 1 1 10 10 2 + 4.30W - - 2 2 2 2 15 15 3 - 1.40W - - 3 3 3 3 500 500 4 - 0.0080W - - 4 4 4 4 8000 10000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 44 Celsius Available Spare: 100% Available Spare Threshold: 10% Percentage Used: 4% Data Units Read: 7,762,320 [3.97 TB] Data Units Written: 4,868,483 [2.49 TB] Host Read Commands: 127,512,974 Host Write Commands: 52,503,969 Controller Busy Time: 0 Power Cycles: 228 Power On Hours: 390 Unsafe Shutdowns: 185 Media and Data Integrity Errors: 0 Error Information Log Entries: 0 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Error Information (NVMe Log 0x01, 16 of 64 entries) No Errors Logged Self-test Log (NVMe Log 0x06) Self-test status: No self-test in progress No Self-tests Logged -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1228595] New: TW installation with bootloader sdboot missing NVRAM, MBR, and Secure Boot options
by bugzilla_noreply＠suse.com 08 May '25

08 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1228595 Bug ID: 1228595 Summary: TW installation with bootloader sdboot missing NVRAM, MBR, and Secure Boot options Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mario_bz(a)mgtech.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When installing TW and sdboot is selected as the boot loader, three options are missing that are present in the grub2 selection. 1. Do not update NVRAM, this is needed on multiboot systems that have a common boot manager that must not be modified. In this case, Refind/Refind Plus. They are used to boot various Linux systems as well as macOS. I also use the Opencore BM to boot unsupported macOS systems, it resides along Refind Plus. Installing TW with sdboot changes NVRAM to replace the default BM so multiboot is no longer possible without re-setup. 2. Secure Boot, this is also missing, in my case, and I am sure others, it is not needed. 3. Do not change MBR. This option is needed since in cases like mine (using a Mac) this is not wanted. This issue is an extension of issue #1226122 missing /boot files. https://bugzilla.opensuse.org/show_bug.cgi?id=1226122 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1226101] New: Joystick and steering wheel not found in system settings
by bugzilla_noreply＠suse.com 08 May '25

08 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1226101 Bug ID: 1226101 Summary: Joystick and steering wheel not found in system settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Michael.Zapf(a)mizapf.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The Plasma System Settings do not show any game controllers, although there is a digital joystick (connected via a Hexagons USB adapter) and a Logitech G25 steering wheel connected. It only shows a XBox game controller when plugged it. The settings were present for the Joystick and the steering wheel in some earlier release (unknown). The devices are found by the system (as dmesg states) and are usable in games, but cannot be configured in KDE. Contrary to the advice in the help file, there is no way to add a non-detected device in the settings. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1240065] New: emacs default font has changed to "Adwaita Mono 11" if Gnome is installed
by bugzilla_noreply＠suse.com 08 May '25

08 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1240065 Bug ID: 1240065 Summary: emacs default font has changed to "Adwaita Mono 11" if Gnome is installed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since a very recent update of TW I noticed that my emacs font was different and bigger. After investigation I found it is now using "Adwaita Mono 11" instead of "Mono" (at size 10, the emacs default) which I have configured to Consolas. "Adwaita Mono" comes from package adwaita-fonts which is a recent new dependency of Gnome (or some part of it) since it is the new Gnome default font. I use i3 instead of Gnome, although I have Gnome also installed. I learned that emacs try to use the default Gnome font as returned by 'gsettings get org.gnome.desktop.interface monospace-font-name' (which now returns "Adwaita Mono 11"). If it cannot find this font (not installed) it fallbacks to its default of "Mono 10". - If you do not care about "Adwaita Mono" simply remove package adwaita-fonts and add a lock for it with zypper. This is what I did and emacs uses glorious "Mono 10" again (Gnome as well). - If you want to keep "Adwaita Mono" as the default mono font for Gnome but not emacs you'll have to configure the font explicitly for emacs - of you want to change the mono font for Gnome and emacs you'll have to configure it in Gnome font panel (or via gsettings set org.gnome.desktop.interface monospace-font-name <font>) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1228836] New: scrcpy contains pre-built binaries
by bugzilla_noreply＠suse.com 08 May '25

08 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1228836 Bug ID: 1228836 Summary: scrcpy contains pre-built binaries Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: munix9(a)googlemail.com Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- scrcpy seems to contain pre-built binaries: URL: https://github.com/Genymobile/scrcpy Source0: %{url}/archive/refs/tags/v%{version}.tar.gz#/%{name}-%{version}.tar.gz Source1: %{url}/releases/download/v%{version}/scrcpy-server-v%{version} $ file scrcpy-server-v2.6.1 scrcpy-server-v2.6.1: Android package (APK), with gradle app-metadata.properties https://github.com/Genymobile/scrcpy/blob/master/doc/build.md#build https://github.com/Genymobile/scrcpy/blob/master/doc/build.md#option-2-use-… This appears to be in violation of packaging policy: https://en.opensuse.org/openSUSE:Packaging_guidelines#No_inclusion_of_pre-b… If the package can be made functional without this BLOB, please do so. If not, built the binary from sources either in the package or as a separate package. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1233961] New: VUL-0: CVE-2024-11738: gstreamer-plugins-rs: rustls: accept`
by bugzilla_noreply＠suse.com 08 May '25

08 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1233961 https://bugzilla.suse.com/show_bug.cgi?id=1233961#c1 Bug ID: 1233961 Summary: VUL-0: CVE-2024-11738: gstreamer-plugins-rs: rustls: accept` Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/430408/ OS: Other Status: NEW Whiteboard: CVSSv3.1:SUSE:CVE-2024-11738:5.9:(AV:N/AC:H/PR:N/UI:N/ S:U/C:N/I:N/A:H) Severity: Normal Priority: P5 - None Component: Security Assignee: bjorn.lie(a)gmail.com Reporter: emanuele.cappello(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1233897 Target Milestone: --- Found By: --- Blocker: --- --- Comment #1 from Emanuele Cappello <emanuele.cappello(a)suse.com> --- A bug introduced in rustls 0.23.13 leads to a panic if the received TLS ClientHello is fragmented. Only servers that use `rustls::server::Acceptor::accept()` are affected. Servers that use `tokio-rustls`'s `LazyConfigAcceptor` API are affected. Servers that use `tokio-rustls`'s `TlsAcceptor` API are not affected. Servers that use `rustls-ffi`'s `rustls_acceptor_accept` API are affected. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-11738 https://bugzilla.redhat.com/show_bug.cgi?id=2328732 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1236944] New: Latest screen does not work without terminal anymore
by bugzilla_noreply＠suse.com 08 May '25

08 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1236944 Bug ID: 1236944 Summary: Latest screen does not work without terminal anymore Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- For several packages I use screen to emulate terminals for the configure checks of e.g. clisp ... With latest change I now see in the logs: [ 136s] + screen -D -m setarch x86_64 -R ./configure build '' --prefix=/usr --exec-prefix=/usr --libdir=/usr/lib64 --vimdir=/usr/share/vim/site/after/syntax --fsstnd=suse --with-readline --with-dynamic-modules --with-ffcall --with-gettext --with-module=asdf --with-module=dbus --with-module=editor --with-module=fastcgi --with-module=queens --with-module=gdbm --with-module=gtk2 --with-module=pari --with-module=pcre --with-module=rawsock --with-module=zlib --with-module=libsvm --with-module=bindings/glibc --with-module=clx/new-clx --with-module=berkeley-db --with-module=postgresql --config CC=gcc 'CFLAGS=-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -funwind-tables -fasynchronous-unwind-tables -Werror=return-type -flto=auto -ffat-lto-objects -g3 -D_GNU_SOURCE -D_DEFAULT_SOURCE -D_XOPEN_SOURCE -fno-strict-aliasing -fPIC -pipe -Wa,--noexecstack -Wno-unused -Wno-uninitialized -Wno-implicit-fallthrough -Wno-volatile-register-var -Wno-address -Wno-clobbered -Wno-dangling-pointer -Wno-unused-result -Wno-missing-declarations -Wno-cast-function-type -fno-gcse -I/usr/include/fastcgi' 'LDFLAGS= -Wl,--as-needed -Wl,-z,relro -Wl,-z,noexecstack' and indeed abuild@noether:/home/abuild/rpmbuild/BUILD/clisp-2.49.93-build/clisp-2.49.93+git20240704.f5acef38> strace -o log screen -D -m abuild@noether:/home/abuild/rpmbuild/BUILD/clisp-2.49.93-build/clisp-2.49.93+git20240704.f5acef38> tail log geteuid() = 399 getegid() = 399 connect(3, {sa_family=AF_UNIX, sun_path="/home/abuild/rpmbuild/BUILD/clisp-2.49.93-build/clisp-2.49.93+git20240704.f5acef38/screen.F3iznH/2590861..n"}, 115) = -1 EINVAL (Invalid argument) unlink("/home/abuild/rpmbuild/BUILD/clisp-2.49.93-build/clisp-2.49.93+git20240704.f5acef38/screen.F3iznH/2590861..noether") = -1 ENOENT (No such file or directory) bind(3, {sa_family=AF_UNIX, sun_path="/home/abuild/rpmbuild/BUILD/clisp-2.49.93-build/clisp-2.49.93+git20240704.f5acef38/screen.F3iznH/2590861..n"}, 115) = -1 EINVAL (Invalid argument) fstat(1, {st_mode=S_IFCHR|0666, st_rdev=makedev(0x1, 0x3), ...}) = 0 ioctl(1, TCGETS, 0x7ffeaa2e0820) = -1 ENOTTY (Inappropriate ioctl for device) write(1, "bind (/home/abuild/rpmbuild/BUIL"..., 140) = 140 exit_group(1) = ? +++ exited with 1 +++ -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1235829] New: [Build 20250108-SELinux] openQA test fails in systemd_nspawn
by bugzilla_noreply＠suse.com 07 May '25

07 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1235829 Bug ID: 1235829 Summary: [Build 20250108-SELinux] openQA test fails in systemd_nspawn Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4762579/modules/syst emd_nspawn/steps/142 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: cathy.hu(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1230118 Target Milestone: --- Found By: openQA Blocker: Yes Reproducer: zypper -n in systemd-container zypper -n --root /var/lib/machines/test1 --gpg-auto-import-keys addrepo http://openqa.opensuse.org/assets/repo/openSUSE-Tumbleweed-oss-x86_64-Snaps… defaultrepo zypper -n --root /var/lib/machines/test1 --gpg-auto-import-keys refresh zypper -n --root /var/lib/machines/test1 install --no-recommends -ly systemd shadow zypper openSUSE-release systemctl --no-pager start systemd-nspawn\@test1 systemctl --no-pager status systemd-nspawn\@test1 systemd-run -tM test1 /bin/bash -c date journalctl -n10 -M test1 | grep 'Reached target Multi-User System' ---- time->Tue Jan 14 09:48:55 2025 type=AVC msg=audit(1736844535.757:1171): avc: denied { read } for pid=862 comm="dbus-broker" path="/" dev="vda2" ino=257 scontext=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:systemd_machined_var_lib_t:s0 tclass=dir permissive=0 ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_textmode@64bit fails in [systemd_nspawn](https://openqa.opensuse.org/tests/4762579/modules/systemd_n… ## Test suite description Maintainer: slindomansilla(a)suse.de. Mainly post-installation console extra tests. ## Reproducible Fails since (at least) Build [20240702](https://openqa.opensuse.org/tests/4315747) ## Expected result Last good: [20240611](https://openqa.opensuse.org/tests/4267371) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228540] New: [SELinux] avc during boot for int-xenstore-d and qemu-system-i386
by bugzilla_noreply＠suse.com 07 May '25

07 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1228540 Bug ID: 1228540 Summary: [SELinux] avc during boot for int-xenstore-d and qemu-system-i386 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: conde.philippe(a)skynet.be QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876364 --> https://bugzilla.suse.com/attachment.cgi?id=876364&action=edit output of commande ausearch I have a server with latest openSUSE tumbleweed and with KDE. I have a VM (with opensuse tumbleweed also) that I start with virtmgr when needed. I have activated selinux in permissive mode on the host following your advice: https://en.opensuse.org/Portal:SELinux/Setup#Tumbleweed hpprol2:~ # sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: permissive Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 33 hpprol2:~ # hpprol2:~ # zypper info selinux-policy Loading repository data... Reading installed packages... Information for package selinux-policy: --------------------------------------- Repository : security:SELinux Name : selinux-policy Version : 20240729-249.1 Arch : noarch Vendor : obs://build.opensuse.org/security:SELinux Installed Size : 28.3 KiB Installed : Yes Status : up-to-date Source package : selinux-policy-20240729-249.1.src Upstream URL : https://github.com/fedora-selinux/selinux-policy.git Summary : SELinux policy configuration I boot the xen kernel and receive the errors during boot. as far as I see the problem is with directory /var/lib/xen which is labeled as hpprol2:~ # ls -dZ /var/lib/xen system_u:object_r:xend_var_lib_t:s0 /var/lib/xen hpprol2:~ # ls -lZ /var/lib/xen/* -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 209 Jul 30 10:24 /var/lib/xen/userdata-d.0.00000000-0000-0000-0000-000000000000.libxl-json -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 209 Jul 30 10:24 /var/lib/xen/userdata-d.1.00000000-0000-0000-0000-000000000000.libxl-json -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2257 Jul 5 22:43 /var/lib/xen/userdata-d.2.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libvirt-xml -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2121 Jul 5 22:43 /var/lib/xen/userdata-d.2.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libxl-json -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2257 Jul 5 12:01 /var/lib/xen/userdata-d.3.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libvirt-xml -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2181 Jul 5 12:01 /var/lib/xen/userdata-d.3.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libxl-json -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2257 Mar 17 11:47 /var/lib/xen/userdata-d.4.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libvirt-xml -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2121 Mar 17 11:47 /var/lib/xen/userdata-d.4.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libxl-json -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2257 Oct 20 2023 /var/lib/xen/userdata-d.8.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libvirt-xml -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2121 Oct 20 2023 /var/lib/xen/userdata-d.8.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libxl-json I attach the ausearch -ts today -m avc output related to this problem version of xen-tools Information for package xen-tools: ---------------------------------- Repository : Main Repository (OSS) Name : xen-tools Version : 4.18.2_06-2.1 Arch : x86_64 Vendor : openSUSE Installed Size : 2.8 MiB Installed : Yes (automatically) Status : up-to-date Source package : xen-4.18.2_06-2.1.src Upstream URL : http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ Summary : Xen Virtualization: Control tools for domain 0 My vm défintion /etc/libvirt/libxl/opensusetumbleweed.xml  <domain type="xen"> <name>opensusetumbleweed</name> <uuid>c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad</uuid> <metadata> <libosinfo:libosinfo> <libosinfo:os id="http://opensuse.org/opensuse/tumbleweed"/> </libosinfo:libosinfo> </metadata> <memory unit="KiB">2097152</memory> <currentMemory unit="KiB">2097152</currentMemory> <vcpu placement="static">2</vcpu> <os> <type arch="x86_64" machine="xenfv">hvm</type> <loader type="rom">/usr/lib/xen/boot/hvmloader</loader> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset="utc"/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/lib/xen/bin/qemu-system-i386</emulator> <disk type="block" device="disk"> <driver name="phy" type="raw"/> <source dev="/dev/disk/by-id/scsi-3600508b1001c21d488c454a46bc39f22-part1"/> <target dev="hda" bus="ide"/> <address type="drive" controller="0" bus="0" target="0" unit="0"/> </disk> <disk type="block" device="cdrom"> <driver name="qemu" type="raw"/> <source dev="/dev/sr0"/> <target dev="hdb" bus="ide"/> <readonly/> <address type="drive" controller="0" bus="0" target="0" unit="1"/> </disk> <controller type="xenbus" index="0"/> <controller type="ide" index="0"/> <interface type="bridge"> <mac address="00:16:3e:9c:13:3e"/> <source bridge="br0"/> </interface> <serial type="pty"> <target port="0"/> </serial> <console type="pty"> <target type="serial" port="0"/> </console> <input type="mouse" bus="ps2"/> <input type="keyboard" bus="ps2"/> <graphics type="vnc" port="-1" autoport="yes"> <listen type="address"/> </graphics> <video> <model type="vga" vram="16384" heads="1" primary="yes"/> </video> <memballoon model="xen"/> </devices> </domain> -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1236217] New: go1.24 release tracking
by bugzilla_noreply＠suse.com 07 May '25

07 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1236217 Bug ID: 1236217 Summary: go1.24 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- go1.24 (expected February 2025) is a major release of Go. Minor releases of go1.24.x will be provided through February 2026. This issue tracks go1.24.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 10