March 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1235876] New: VUL-0: CVE-2024-53263: git-lfs: Git LFS permits exfiltration of credentials via crafted HTTP URLs
by bugzilla_noreply＠suse.com 12 May '25

12 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1235876 Bug ID: 1235876 Summary: VUL-0: CVE-2024-53263: git-lfs: Git LFS permits exfiltration of credentials via crafted HTTP URLs Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/436637/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: abergmann(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Git LFS is a Git extension for versioning large files. When Git LFS requests credentials from Git for a remote host, it passes portions of the host's URL to the `git-credential(1)` command without checking for embedded line-ending control characters, and then sends any credentials it receives back from the Git credential helper to the remote host. By inserting URL-encoded control characters such as line feed (LF) or carriage return (CR) characters into the URL, an attacker may be able to retrieve a user's Git credentials. This problem exists in all previous versions and is patched in v3.6.1. All users should upgrade to v3.6.1. There are no workarounds known at this time. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-53263 https://www.cve.org/CVERecord?id=CVE-2024-53263 https://github.com/git-lfs/git-lfs/commit/0345b6f816e611d050c0df67b61f00229… https://github.com/git-lfs/git-lfs/releases/tag/v3.6.1 https://github.com/git-lfs/git-lfs/security/advisories/GHSA-q6r2-x2cc-vrp7 https://bugzilla.redhat.com/show_bug.cgi?id=2338002 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228659] New: Snapshot 20240730 - unbootable after transactional-update dup
by bugzilla_noreply＠suse.com 12 May '25

12 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1228659 Bug ID: 1228659 Summary: Snapshot 20240730 - unbootable after transactional-update dup Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Transactional Update Assignee: aplanas(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- All Aeon installations (and I suspect all MicroOS systemd-boot installations) are failing to boot after a transactional-update dup to the latest snapshot I suspect the cause is the misbehaviour of the sdbootutil plugin reported during the transactional-update Example logs below: (25/41) Installing: kernel-default-6.10.2-1.1.x86_64 [... Error: No ESP detected. Legacy system? ................................................................................................... Error: No ESP detected. Legacy system? Error: No ESP detected. Legacy system? dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.10.2-1-default 6.10.2-1-default dracut[I]: Module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: 35network-legacy: Could not find any command of 'dhclient wicked'! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'pcsc' will not be installed, because command 'pcscd' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut[I]: 95nfs: Could not find any command of 'rpcbind portmap'! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: 35network-legacy: Could not find any command of 'dhclient wicked'! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'pcsc' will not be installed, because command 'pcscd' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut[I]: 95nfs: Could not find any command of 'rpcbind portmap'! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: *** Including module: systemd *** dracut[I]: *** Including module: systemd-initrd *** dracut[I]: *** Including module: i18n *** dracut[I]: No KEYMAP configured. dracut[I]: *** Including module: drm *** dracut[I]: *** Including module: health-checker *** dracut-install: ERROR: installing 'grub2-editenv' dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.kGpiZ2/initramfs -a date btrfs awk grub2-editenv dracut[I]: *** Including module: pcr-signature *** dracut[I]: *** Including module: transactional-update *** dracut[I]: *** Including module: btrfs *** dracut[I]: *** Including module: kernel-modules *** udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory dracut[I]: *** Including module: kernel-modules-extra *** dracut[I]: *** Including module: rootfs-block *** dracut[I]: *** Including module: suse-btrfs *** dracut[I]: *** Including module: suse-xfs *** dracut[I]: *** Including module: terminfo *** dracut[I]: *** Including module: udev-rules *** udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory dracut[E]: Failed to detect udev version! dracut[I]: *** Including module: dracut-systemd *** dracut[I]: *** Including module: ostree *** dracut[I]: *** Including module: selinux-microos *** dracut[I]: *** Including module: usrmount *** dracut[I]: *** Including module: base *** dracut[I]: *** Including module: fs-lib *** dracut[I]: *** Including module: shutdown *** dracut[I]: *** Including module: suse *** dracut[I]: *** Including module: suse-initrd *** dracut[I]: *** Including modules done *** dracut[I]: *** Installing kernel module dependencies *** dracut[I]: *** Installing kernel module dependencies done *** dracut[I]: *** Resolving executable dependencies *** dracut[I]: *** Resolving executable dependencies done *** dracut[I]: *** Hardlinking files *** dracut[I]: *** Hardlinking files done *** dracut[I]: *** Generating early-microcode cpio image *** dracut[I]: *** Store current command line parameters *** dracut[I]: Stored kernel commandline: dracut[I]: rd.driver.pre=btrfs dracut[I]: rd.driver.pre=overlay dracut[I]: root=UUID=42fc02eb-e038-424f-b5a5-aed45173338d rootfstype=btrfs rootflags=rw,relatime,seclabel,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=403,subvol=/@/.snapshots/98/snapshot,subvol=@/.snapshots/98/snapshot dracut[I]: *** Stripping files *** dracut[I]: *** Stripping files done *** dracut[I]: *** Creating image file '/boot/initrd-6.10.2-1-default' *** dracut[I]: *** Creating initramfs image file '/boot/initrd-6.10.2-1-default' done *** /usr/lib/bootloader/bootloader_entry: line 117: /etc/sysconfig/bootloader: No such file or directory CA enrolled. Skip /etc/uefi/certs/1F673297.crt Error: No ESP detected. Legacy system? ... Error: No ESP detected. Legacy system? Error: No ESP detected. Legacy system? /usr/lib/bootloader/bootloader_entry: line 117: /etc/sysconfig/bootloader: No such file or directory done] -- You are receiving this mail because: You are on the CC list for the bug.

1 42

[Bug 1237564] New: not able to boot after update to 20250222
by bugzilla_noreply＠suse.com 12 May '25

12 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1237564 Bug ID: 1237564 Summary: not able to boot after update to 20250222 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: mcaj(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 880557 --> https://bugzilla.suse.com/attachment.cgi?id=880557&action=edit boot screen Hi, Today, I have updated my TW machine to the version 20250222. The update was without any errors via classic `zypper ref && zypper dup` commands. After the reboot I sow just a splash screen that never finish. Only help was reboot the machines. I'm using encrypted home disk that has a record in /etc/crypttab Usually the cryptsetup.target start and ask me for the password in the TW spash screen. This time there was not pop up for the password... By default I have in grub this settings: splash=silent quiet so there is not much to see. When I boot for the second time se change it to: debug and see that systemd is ruuning Cryptography setup for my home / aka cr-auto1 I tried to enter my password but on the feedback it looks like only every second key that I pressed was there see as * I looks like some other systemd service is overtaking it and does not allow me to correctly add the password. As you can see on the picture there ware * and . that I did not put a dot into my password - I never sow this so far as feedback when I enter the disk password was * only. After that it end up in Dracut Emergency Shell, where I was able to unlock encrypted disk an continue with boot. Once the system "boot" into X I see this: ``` # systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION * measure-pcr-validator.service not-found failed failed measure-pcr-validator.service # systemctl status measure-pcr-validator.service x measure-pcr-validator.service Loaded: not-found (Reason: Unit measure-pcr-validator.service not found.) Active: failed (Result: signal) since Mon 2025-02-24 14:09:43 CET; 59min ago Duration: 2.851s Invocation: e8d8642facab45fcb977f9604fb3b5df Main PID: 502 (code=exited, status=0/SUCCESS) CPU: 7ms Feb 24 14:09:42 fl systemd[1]: Serializing sd-executor-state to memfd. Feb 24 14:09:42 fl systemd[1]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy Feb 24 14:09:42 fl systemd[1]: measure-pcr-validator.service: Forked /bin/sh as 711 (via CLONE_INTO_CGROUP) Feb 24 14:09:42 fl systemd[1]: measure-pcr-validator.service: Changed exited -> stop-post Feb 24 14:09:42 fl systemd[1]: Stopping Validate LUKS2 devices... Feb 24 14:09:42 fl (sh)[711]: Found container virtualization none. Feb 24 14:09:42 fl (sh)[711]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy Feb 24 14:09:42 fl (sh)[711]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy Feb 24 14:09:42 fl (sh)[711]: measure-pcr-validator.service: Executing: /bin/sh -c "/usr/bin/plymouth quit 2>/dev/null || :" Feb 24 14:09:43 fl systemd[1]: measure-pcr-validator.service: Installed new job measure-pcr-validator.service/stop as 395 # systemctl status cryptsetup.target * cryptsetup.target - Local Encrypted Volumes Loaded: loaded (/usr/lib/systemd/system/cryptsetup.target; static) Active: active since Mon 2025-02-24 14:09:39 CET; 1h 0min ago Invocation: 3ceb5efdd4e14e4db61ad2be9cd95511 Docs: man:systemd.special(7) Feb 24 14:09:39 fl systemd[1]: cryptsetup.target: Changed dead -> active Feb 24 14:09:39 fl systemd[1]: cryptsetup.target: Job 20 cryptsetup.target/start finished, result=done Feb 24 14:09:39 fl systemd[1]: Reached target Local Encrypted Volumes. Feb 24 14:09:42 fl systemd[1]: cryptsetup.target: Installed new job cryptsetup.target/stop as 134 Feb 24 14:09:42 fl systemd[1]: cryptsetup.target: stopping held back, waiting for: measure-pcr-validator.service ``` Martin ps how 20250222 passed the openqa test for boot with encrypted disk ? I hope you are also testing this case. -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1222044] New: zypper %posttrans fails with "Failed to start jobs"
by bugzilla_noreply＠suse.com 09 May '25

09 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1222044 Bug ID: 1222044 Summary: zypper %posttrans fails with "Failed to start jobs" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873853 --> https://bugzilla.suse.com/attachment.cgi?id=873853&action=edit zypper.log Upgrading from TW Snapshot 20240321 to 20240325 with zypper -v dup had the following output at the end: Ausgabe des Skripts %posttrans(zypper-1.14.70-1.1.x86_64): Failed to start jobs: Failed to enqueue some jobs, see logs for details: No such file or directory Nach-Transaktions-Skripte werden ausgeführt ..............................................................................................................................................................................................[fertig] CommitResult (total 432, done 432, error 0, skipped 0, updateMessages 0) -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1236709] New: qemu-aarch64 invoked via binfmt_misc dumps core
by bugzilla_noreply＠suse.com 09 May '25

09 May '25

https://bugzilla.suse.com/show_bug.cgi?id=1236709 Bug ID: 1236709 Summary: qemu-aarch64 invoked via binfmt_misc dumps core Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: dimitrios.bouras(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 880083 --> https://bugzilla.suse.com/attachment.cgi?id=880083&action=edit ELF 64-bit LSB core file ARM aarch64, version 1 (SYSV), SVR4-style, from '/mnt/usr/sbin/ldconfig --help' Running an aarch64 binary on x86_64 (via binfmt_misc) under Leap 15.6 (kernel 6.4.0-150600.23.33-default) dumps core. The same works just fine on Leap 15.5 (kernel 5.14.21-150500.55.88-default). Discovered it when running dpkg on a /dev/loop mounted ext4 root filesystem for RPi OS / Debian 11. Example steps to reproduce: % wget -nv -O - https://downloads.raspberrypi.com/raspios_oldstable_lite_arm64/images/raspi… | xz -dc > /tmp/raspios_arm64.img 2025-01-31 22:04:53 URL:https://downloads.raspberrypi.com/raspios_oldstable_lite_arm64/images/r… [327266544/327266544] -> "-" [1] % sudo losetup --show -Pf /tmp/raspios_arm64.img /dev/loop20 % sudo mount /dev/loop20p2 /mnt % ll /mnt/usr/sbin/ldconfig -rwxr-xr-x 1 root root 654272 Sep 2 08:10 /mnt/usr/sbin/ldconfig* % file /mnt/usr/sbin/ldconfig /mnt/usr/sbin/ldconfig: ELF 64-bit LSB shared object, ARM aarch64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=ba7bda9fe65bee96a338ac9873025e0a98ee7b03, for GNU/Linux 3.7.0, stripped % /mnt/usr/sbin/ldconfig --help Segmentation fault (core dumped) On OpenSuSE Leap 15.5: % /mnt/usr/sbin/ldconfig --help Usage: ldconfig [OPTION...] Configure Dynamic Linker Run Time Bindings. -c, --format=FORMAT Format to use: new (default), old, or compat -C CACHE Use CACHE as cache file -f CONF Use CONF as configuration file -i, --ignore-aux-cache Ignore auxiliary cache file -l Manually link individual libraries. -n Only process directories specified on the command line. Don't build cache. -N Don't build cache -p, --print-cache Print cache -r ROOT Change to and use ROOT as root directory -v, --verbose Generate verbose messages -X Don't update symbolic links -?, --help Give this help list --usage Give a short usage message -V, --version Print program version Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options. For bug reporting instructions, please see: <http://www.debian.org/Bugs/>. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[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