January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1214614] New: [suggested] add "sane-backends" in default install
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214614 Bug ID: 1214614 Summary: [suggested] add "sane-backends" in default install Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: christophe.durand(a)my.mail.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0 Build Identifier: Usb Scanners are not recognized by default Aeon installation. Simple-scan flatpak complains about missing drivers. To have fonctionnal usb scanner, I need to add san-backends and san-backends-autoconfig. Reproducible: Always Steps to Reproduce: install simple-scan flatpak try to use USB scanner Actual Results: missing drivers Expected Results: USB scanner should work out of the box (at least for a desktop environnement) no Scanner drivers installed by default in Aeon. Can be solved with sane-backends installation. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1218510] New: Microphone (Alder Lake PCH-P) not working due to alsa missing
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218510 Bug ID: 1218510 Summary: Microphone (Alder Lake PCH-P) not working due to alsa missing Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: 0xdopice(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On my Alder Lake based Lenovo Thinkpad X1 Carbon Gen 10 the microphone is not working out of the box. This is due to alsa not being installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1212951] New: AUDIT-1: nqptp: precision time protocol daemon
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1212951 Bug ID: 1212951 Summary: AUDIT-1: nqptp: precision time protocol daemon 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: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- nqptp is a Precision Time Protocol daemon. Upstream: https://github.com/mikebrady/nqptp This daemon runs as root and, according to upstream: > nqptp has not been checked or audited for security issues. Note that it must run in root mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218260] New: kernel-longterm: 6.6 update tracker for Factory
by bugzilla_noreply＠suse.com 12 Apr '24

12 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218260 Bug ID: 1218260 Summary: kernel-longterm: 6.6 update tracker for Factory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: rfrohl(a)suse.com Reporter: rfrohl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Tracker bug for updates to the 6.6 longterm kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1219031] New: Multiple cross-arm-none-gcc13 bugs
by bugzilla_noreply＠suse.com 12 Apr '24

12 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219031 Bug ID: 1219031 Summary: Multiple cross-arm-none-gcc13 bugs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: rguenther(a)suse.com Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- 1. the package does not require libisl23 libmpc3 so the binary does not run. 2. package not required to provide required headers: ``` Compiling: keyboards/moonlander/matrix.c In file included from ./lib/chibios/os/hal/osal/rt-nil/osal.h:29, from ./lib/chibios/os/hal/include/hal.h:30, from platforms/chibios/platform_deps.h:18, from quantum/quantum.h:18, from keyboards/moonlander/moonlander.h:21, from keyboards/moonlander/matrix.c:19: /usr/lib64/gcc/arm-none-eabi/13/include/stdint.h:9:16: fatal error: stdint.h: No such file or directory 9 | # include_next <stdint.h> | ^~~~~~~~~~ compilation terminated. [ERRORS] | | | gmake[1]: *** [builddefs/common_rules.mk:361: .build/obj_moonlander_darix-v3/matrix.o] Error 1 Make finished with errors gmake: *** [Makefile:392: moonlander:darix-v3] Error 1 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1219033] New: U-boot u-boot-rpiarm64-2024.01-1.1 fails on RPI4b
by bugzilla_noreply＠suse.com 12 Apr '24

12 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219033 Bug ID: 1219033 Summary: U-boot u-boot-rpiarm64-2024.01-1.1 fails on RPI4b Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: David(a)WalkerStreet.info QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872044 --> https://bugzilla.suse.com/attachment.cgi?id=872044&action=edit Screenshot of failed boot After upgrading from Tumbleweed ARM 20240109 to 20240118, my RPI4b failed to boot from USB, then attempted to boot via tftp. I've attached a photo of the screen. I fixed the problem by copying /boot/efi/u-boot.bin from a working RPI4b to the failing system's /boot/efi. Not being sure of the function of /boot/vc, I also copied the working u-boot.bin to the failing system's /boot/vc. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218274] New: xfreerdp 2.4.0 Release 150400.3.23.1 fails with [ERROR][com.freerdp.core.fastpath]
by bugzilla_noreply＠suse.com 11 Apr '24

11 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218274 Bug ID: 1218274 Summary: xfreerdp 2.4.0 Release 150400.3.23.1 fails with [ERROR][com.freerdp.core.fastpath] Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: haenig(a)cosifan.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0 Build Identifier: after updating freerdp to Release 150400.3.23.1 I am no longer able to connect to rdp Servers. After entering my password a window showing a fancy MS image as well as my logon name opens for a short time and then closes again on its own. the update has been done yesterday (2023-12-19) via 'zypper up' and therefore changed/updated other packages as well. Reproducible: Always Steps to Reproduce: 1. launch new rdp session (see details) 2. enter password Actual Results: # initiate session openconnect-leap:~> xfreerdp /kbd:0x00000407 /u:myusername /d:mydomain /v:myserverip [13:43:00:529] [6614:6615] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state [13:43:00:529] [6614:6615] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr [13:43:00:529] [6614:6615] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd [13:43:00:529] [6614:6615] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [13:43:00:843] [6614:6615] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized [13:43:00:845] [6614:6615] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state [13:43:00:845] [6614:6615] [INFO][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state [13:43:00:102] [6614:6615] [WARN][com.freerdp.crypto] - Certificate verification failure 'self signed certificate (18)' at stack position 0 [13:43:00:103] [6614:6615] [WARN][com.freerdp.crypto] - CN = myservername.mydomain Password: [13:43:07:261] [6614:6615] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32 [13:43:07:262] [6614:6615] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [13:43:07:279] [6614:6615] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem [13:43:07:287] [6614:6615] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd [13:43:14:705] [6614:6615] [ERROR][com.freerdp.core.fastpath] - Fastpath update Bitmap [1] failed, status 0 [13:43:14:705] [6614:6615] [ERROR][com.freerdp.core.fastpath] - fastpath_recv_update_data: fastpath_recv_update() - -1 [13:43:14:705] [6614:6615] [ERROR][com.freerdp.core.fastpath] - fastpath_recv_update_data() fail [13:43:14:706] [6614:6615] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -3 [13:43:14:706] [6614:6615] [ERROR][com.freerdp.core] - freerdp_check_fds() failed - 0 [13:43:14:706] [6614:6615] [INFO][com.freerdp.client.common] - Network disconnect! [13:43:14:706] [6614:6615] [ERROR][com.freerdp.client.x11] - Failed to check FreeRDP file descriptor Expected Results: working rdesktop session with freerdp 2.4.0 Release 150400.3.20.1 everything was working O.K. Example: lverm@openvpn-leap:~> xfreerdp /kbd:0x00000407 /u:myusername /d:mydomain /v:myserverip [13:49:37:746] [3026:3027] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state [13:49:37:746] [3026:3027] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr [13:49:37:746] [3026:3027] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd [13:49:37:746] [3026:3027] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr [13:49:37:066] [3026:3027] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized [13:49:37:068] [3026:3027] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state [13:49:37:068] [3026:3027] [INFO][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state [13:49:37:274] [3026:3027] [WARN][com.freerdp.crypto] - Certificate verification failure 'self signed certificate (18)' at stack position 0 [13:49:37:274] [3026:3027] [WARN][com.freerdp.crypto] - CN = myservername.mydomain Password: [13:49:50:584] [3026:3027] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32 [13:49:50:584] [3026:3027] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16 [13:49:50:617] [3026:3027] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem [13:49:50:637] [3026:3027] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd [13:49:55:507] [3026:3027] [INFO][com.freerdp.client.x11] - Logon Error Info SESSION_ID [LOGON_MSG_SESSION_CONTINUE] => here I have window open with a working rdp session -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1218998] New: cannot abort build/restart build/wipe binaries for multibuild packages
by bugzilla_noreply＠suse.com 10 Apr '24

10 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218998 Bug ID: 1218998 Summary: cannot abort build/restart build/wipe binaries for multibuild packages Classification: Internal Novell Products Product: openSUSE Build Service Version: master Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: webui Assignee: hvogel(a)suse.com Reporter: msuchanek(a)suse.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- The Abort build/Restart build/wipe binaries buttons don't work in the web UI https://github.com/openSUSE/open-build-service/issues/12913 https://github.com/openSUSE/open-build-service/issues/7866 https://github.com/openSUSE/open-build-service/issues/7156 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215846] New: Bluetooth under TW will not pair with other devices, although they are discovered
by bugzilla_noreply＠suse.com 09 Apr '24

09 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1215846 Bug ID: 1215846 Summary: Bluetooth under TW will not pair with other devices, although they are discovered Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This hits a ASUS dongle with Bus 001 Device 004: ID 0b05:184c ASUSTek Computer, Inc. 802.11ac NIC which is also WLAN (WLAN/BT). The device can see the other but cannot pair. Neither is a window opened when the PC tries to connect to the device (pairing aborts prematurely), nor is it opened when a device tries to connect to the PC (no device found) although the BT device is shown with name. On Leap 15.4 the very same device pairs flawlessly. So the issue is restricted as it appears to TW. in journalctl I find the protocol of "timeout": 16:43:19 localhost bluedevil-wizard[19224]: kf.bluezqt: PendingCall Error: "Authentication Timeout" set 30 16:43:03 localhost systemd[6683]: Started Aggiungi dispositivo Bluetooth - Aggiungi dispositivo Bluetooth. set 30 16:42:22 localhost akonadi_pop3_resource[7978]: DIGEST-MD5 common mech free set 30 16:42:20 localhost akonadi_pop3_resource[7976]: DIGEST-MD5 common mech free set 30 16:41:08 localhost systemsettings[19149]: Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. set 30 16:41:08 localhost systemsettings[19149]: Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. set 30 16:41:08 localhost systemsettings[19149]: Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. set 30 16:41:08 localhost systemsettings[19149]: Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. set 30 16:41:08 localhost systemsettings[19149]: Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. set 30 16:41:08 localhost systemsettings[19149]: Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. set 30 16:41:08 localhost systemsettings[19149]: QQmlEngine::setContextForObject(): Object already has a QQmlContext set 30 16:41:08 localhost systemsettings[19149]: file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "width" set 30 16:41:08 localhost systemsettings[19149]: file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "width" set 30 16:41:08 localhost systemd[6683]: Started Impostazioni di sistema - Impostazioni di sistema. set 30 16:40:35 localhost plasmashell[6920]: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/PopupDialog.qml:49: TypeError: Cannot read property 'right' of null set 30 16:40:35 localhost plasmashell[6920]: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/PopupDialog.qml:48: TypeError: Cannot read property 'left' of null set 30 16:40:35 localhost plasmashell[6920]: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/PopupDialog.qml:49: TypeError: Cannot read property 'right' of null set 30 16:40:35 localhost plasmashell[6920]: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/PopupDialog.qml:48: TypeError: Cannot read property 'left' of null set 30 16:40:35 localhost plasmashell[6920]: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/PopupDialog.qml:49: TypeError: Cannot read property 'right' of null set 30 16:40:35 localhost plasmashell[6920]: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/PopupDialog.qml:48: TypeError: Cannot read property 'left' of null set 30 16:40:35 localhost plasmashell[6920]: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/PopupDialog.qml:49: TypeError: Cannot read property 'right' of null set 30 16:40:35 localhost plasmashell[6920]: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/PopupDialog.qml:48: TypeError: Cannot read property 'left' of null set 30 16:40:35 localhost plasmashell[6920]: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/PopupDialog.qml:49: TypeError: Cannot read property 'right' of null set 30 16:40:35 localhost plasmashell[6920]: file:///usr/share/plasma/plasmoids/org.papylhomme.diskmonitor/contents/ui/PopupDialog.qml:48: TypeError: Cannot read property 'left' of null set 30 16:43:28 localhost dbus-daemon[1608]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.277" (uid=1000 pid=7050 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=1607 c> set 30 16:43:28 localhost dbus-daemon[1608]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.277" (uid=1000 pid=7050 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=1607 c> set 30 16:43:28 localhost dbus-daemon[1608]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.277" (uid=1000 pid=7050 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=1607 c> set 30 16:43:28 localhost dbus-daemon[1608]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.277" (uid=1000 pid=7050 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=1607 c> set 30 16:43:28 localhost dbus-daemon[1608]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.277" (uid=1000 pid=7050 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=1607 c> set 30 16:43:28 localhost dbus-daemon[1608]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.277" (uid=1000 pid=7050 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=1607 c> set 30 16:43:28 localhost dbus-daemon[1608]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.277" (uid=1000 pid=7050 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=1607 c> set 30 16:43:28 localhost dbus-daemon[1608]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.277" (uid=1000 pid=7050 comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=1607 c> set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/opus_05_duplex set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSink/opus_05_duplex set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/opus_05 set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSink/opus_05 set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/faststream_duplex set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/faststream set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/aptx_ll_0 set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/aptx_ll_1 set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/sbc_xq set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSink/sbc_xq set 30 16:43:28 localhost systemd[1]: Starting Load/Save RF Kill Switch Status... set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/sbc set 30 16:43:28 localhost systemsettings[19149]: file:///usr/share/kpackage/kcms/kcm_bluetooth/contents/ui/General.qml:35: TypeError: Cannot read property 'name' of null set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSink/sbc set 30 16:43:28 localhost systemsettings[19149]: file:///usr/share/kpackage/kcms/kcm_bluetooth/contents/ui/General.qml:41: TypeError: Cannot read property 'address' of null set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/aac set 30 16:43:28 localhost systemsettings[19149]: file:///usr/share/kpackage/kcms/kcm_bluetooth/contents/ui/General.qml:47: TypeError: Cannot read property 'powered' of null set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSink/aac set 30 16:43:28 localhost systemsettings[19149]: file:///usr/share/kpackage/kcms/kcm_bluetooth/contents/ui/General.qml:53: TypeError: Cannot read property 'discoverable' of null set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/aptx set 30 16:43:28 localhost systemsettings[19149]: file:///usr/share/kpackage/kcms/kcm_bluetooth/contents/ui/General.qml:24:9: Unable to assign [undefined] to QObject* set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSink/aptx set 30 16:43:28 localhost systemsettings[19149]: file:///usr/share/kpackage/kcms/kcm_bluetooth/contents/ui/General.qml:24:9: Unable to assign [undefined] to QObject* set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/aptx_hd set 30 16:43:28 localhost systemd-udevd[1083]: /etc/udev/rules.d/55-brother-libsane-type1-inst.rules:14 Invalid key 'SYSFS'. set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSink/aptx_hd set 30 16:43:28 localhost systemd-udevd[1083]: /etc/udev/rules.d/55-brother-brscan4-libsane-type1.rules:9 Invalid key 'SYSFS'. set 30 16:43:28 localhost bluetoothd[1607]: Endpoint unregistered: sender=:1.277 path=/MediaEndpoint/A2DPSource/ldac set 30 16:43:28 localhost plasmashell[6920]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" set 30 16:43:28 localhost plasmashell[6920]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment" set 30 16:43:28 localhost kernel: usb 1-1.7: USB disconnect, device number 6 set 30 16:43:19 localhost bluedevil-wizard[19224]: kf.bluezqt: PendingCall Error: "Authentication Timeout" set 30 16:43:03 localhost systemd[6683]: Started Aggiungi dispositivo Bluetooth - Aggiungi dispositivo Bluetooth. So it is currently not possible to pair certain devices (in particular ones following older BT protocols (here a Samsung GPS/UMTS phone). I doubt the problem is only given by the dongle, it appears it also hits other hardware BT like Cambridge Silicon Radio BT dongle. So changing dongle does not change the issue in TW. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1216969] New: Recent Applications and Recent Files are no longer updated
by bugzilla_noreply＠suse.com 08 Apr '24

08 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1216969 Bug ID: 1216969 Summary: Recent Applications and Recent Files are no longer updated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent Applications and Recent Files are no longer updated in KDE's Application menu. The links are existing in .local/share/RecentDocuments, though. Didn't find any directory for Recent Apps. Operating System: openSUSE Tumbleweed 20231106 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1217342] New: VirtualBox: Starting VM hangs if hosts system uses newer kernel
by bugzilla_noreply＠suse.com 08 Apr '24

08 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1217342 Bug ID: 1217342 Summary: VirtualBox: Starting VM hangs if hosts system uses newer kernel Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: ceggers(a)arri.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870854 --> https://bugzilla.suse.com/attachment.cgi?id=870854&action=edit dmesg output after trying to start a VirtualBox VM Machine: DELL Precision 5680 In order to get sound on this machine running, I was forced to install a contemporary kernel (6.6.0-lp155.8) from the Kernel:stable:Backport:standard repository (sound works fine after installing this kernel, latest Alsa libs AND sof-firmware). Unfortunately, VirtualBox runs not fine at all. I installed the KMP (in the same version) from Kernel:stable:Backport:KMP:standard and VirtualBox starts without complaining about missing modules (and I see vboxnetadp, vboxnetflt and vboxdrv in the output of lsmod). But when I try to run a virtual machine, the sidebar shows only a progress bar "VM hochfahren ..." , stuck at 20%. Additionally I get much output in the kernel log (see attached file). I have the same problem with different virtual machines (Windows 11, openSUSE). When booting the host system with the openSUSE Leap 15.5 stock kernel (currently 5.14.21), VirtualBox VMs run fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215337] New: python-onnx does not build s390x
by bugzilla_noreply＠suse.com 07 Apr '24

07 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1215337 Bug ID: 1215337 Summary: python-onnx does not build s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: azouhr(a)opensuse.org QA Contact: qa-bugs(a)suse.de CC: ada.lovelace(a)gmx.de, ihno(a)suse.com Target Milestone: --- Found By: --- Blocker: --- python-onnx does not build on openSUSE:Factory:zSystems for quite some time: osc buildhistory openSUSE:Factory:zSystems python-onnx standard s390x TIME SRCMD5 VER-REL.BUILD# REV DURATION 2019-11-26 15:59:51 c7251471230f79907f69762d42f620a6 1.6.0-1.1 1 414 2019-12-24 10:29:50 c7251471230f79907f69762d42f620a6 1.6.0-1.2 1 821 2020-01-07 20:22:00 c7251471230f79907f69762d42f620a6 1.6.0-1.3 1 138 2020-01-08 17:02:51 0147179dbf202fdba63d0887ccf75400 1.6.0-2.1 2 192 2020-01-11 08:08:49 0147179dbf202fdba63d0887ccf75400 1.6.0-2.2 2 137 2020-01-21 18:59:45 0147179dbf202fdba63d0887ccf75400 1.6.0-2.3 2 135 2020-02-05 07:12:05 0147179dbf202fdba63d0887ccf75400 1.6.0-2.4 2 668 2020-02-07 20:58:34 0147179dbf202fdba63d0887ccf75400 1.6.0-2.5 2 178 2020-02-16 16:40:23 0147179dbf202fdba63d0887ccf75400 1.6.0-2.6 2 280 2020-02-18 13:51:04 0147179dbf202fdba63d0887ccf75400 1.6.0-2.7 2 227 2020-02-19 17:01:33 0147179dbf202fdba63d0887ccf75400 1.6.0-2.8 2 264 This package is needed in order to prepare a container for onnx-mlir which is the platform that also supports IBM Telum processors on Mainframe. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1214795] New: [Build 518.1] openQA test fails in sshfs - sshfs can not be installed on s390x
by bugzilla_noreply＠suse.com 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214795 Bug ID: 1214795 Summary: [Build 518.1] openQA test fails in sshfs - sshfs can not be installed on s390x Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: S/390-64 URL: https://openqa.opensuse.org/tests/3534841/modules/sshf s/steps/19 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation sshfs tests are failing during the installation of sshfs on s390x. The capability can not be found: 2023-08-29 14:32:30 <2> susetest(39392) [zypper:req] SolverRequester.cc(install):325 sshfs cap:sshfs not found 2023-08-29 14:32:30 <5> susetest(39392) [zypp-core] Exception.cc(log):186 installremove.cc(handleFeedback):41 THROW: name or capability not found 2023-08-29 14:32:30 <5> susetest(39392) [zypp-core] Exception.cc(log):186 basecommand.cc(run):281 CAUGHT: name or capability not found at opensuse/lib/utils.pm line 675. openQA test in scenario opensuse-15.6-DVD-s390x-textmode-server@s390x-zVM-vswitch-l2 fails in [sshfs](https://openqa.opensuse.org/tests/3534841/modules/sshfs/steps/19) ## Test suite description The base test suite is used for job templates defined in YAML documents. It has no settings of its own. ## Reproducible Fails since (at least) Build [507.2](https://openqa.opensuse.org/tests/3505261) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1216042] New: Kernels fail to build in Kernel:stable:Backport
by bugzilla_noreply＠suse.com 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1216042 Bug ID: 1216042 Summary: Kernels fail to build in Kernel:stable:Backport Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The recently updated binutils in openSUSE_Leap_15.4 generate new DT_ tags which dwarves does not know about: [ 1122s] Unsupported DW_TAG_unspecified_type(0x3b) [ 1122s] Encountered error while encoding BTF. osc branch --nodevelproject openSUSE:Factory dwarves Kernel:stable:Backport would probably solve this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1216871] New: Thinkpad P16 with Open GPU kernel modules does not resume after sleep/hibernate (BUG: kernel NULL pointer dereference, address: 0000000000000008)
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1216871 Bug ID: 1216871 Summary: Thinkpad P16 with Open GPU kernel modules does not resume after sleep/hibernate (BUG: kernel NULL pointer dereference, address: 0000000000000008) 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This is similar to #1211950, but I don't use nouveau but these packages nvidia-open-driver-G06-signed-kmp-default kernel-firmware-nvidia-gsp-G06 nvidia-open-driver-G06-signed-kmp suggested in [1]. I tried both of these [2], but although sleep worked it did not resume: sudo systemctl suspend sudo systemctl hibernate (I searched to [2] due errors reported in dmesg after trying to suspend with echo mem > /sys/power/state). suspend is ok: [ 0.000000] Linux version 6.5.9-1-default (geeko@buildhost) (gcc (SUSE Linux) 13.2.1 20230912 [revision b96e66fd4ef3e36983969fb8cdd1956f551a074b], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.40.0.20230412-5) #1 SMP PREEMPT_DYNAMIC Wed Oct 25 10:31:37 UTC 2023 (29edc7c) [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.9-1-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap mitigations=auto quiet security=apparmor nosimplefb=1 ... [ 247.802155] NVRM nvAssertFailedNoLog: Assertion failed: 0 @ mem_list.c:293 [ 247.802161] NVRM nvAssertOkFailedNoLog: Assertion failed: Call not supported [NV_ERR_NOT_SUPPORTED] (0x00000056) returned from pRmApi->Alloc(pRmApi, pMemoryManager->hClient, pMemoryManager->hSubdevice, pHandle, hClass, &listAllocParams, sizeof(listAllocParams)) @ mem_desc.c:4790 [ 247.802163] NVRM serverFreeResourceTree: hObject 0xcaf00003 not found for client 0xc1e00003 [ 247.802164] NVRM nvAssertOkFailedNoLog: Assertion failed: Call not supported [NV_ERR_NOT_SUPPORTED] (0x00000056) returned from memdescSendMemDescToGSP(pGpu, pFbsr->pSysMemDesc, &hSysMem) @ fbsr_gm107.c:113 [ 247.802165] NVRM nvAssertOkFailedNoLog: Assertion failed: Call not supported [NV_ERR_NOT_SUPPORTED] (0x00000056) returned from _fbsrInitGsp(pGpu, pFbsr) @ fbsr_gm107.c:548 [ 248.155408] PM: suspend entry (s2idle) [ 248.167460] Filesystems sync: 0.012 seconds [ 248.386725] Freezing user space processes [ 248.387547] Freezing user space processes completed (elapsed 0.000 seconds) [ 248.387549] OOM killer disabled. [ 248.387550] Freezing remaining freezable tasks [ 248.388805] Freezing remaining freezable tasks completed (elapsed 0.001 seconds) [ 248.388808] printk: Suspending console(s) (use no_console_suspend to debug) [ 248.801471] ACPI: EC: interrupt blocked [ 262.602984] ACPI: EC: interrupt unblocked [ 263.174146] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination [ 263.252329] nvme nvme0: 24/0/0 default/read/poll queues ... [ 263.524598] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 263.719374] OOM killer enabled. [ 263.719375] Restarting tasks ... [ 263.719441] usb 1-3: USB disconnect, device number 3 [ 263.719734] done. [ 263.719738] random: crng reseeded on system resumption [ 263.788084] PM: suspend exit ... [ 264.672684] NVRM: GPU at PCI:0000:01:00: GPU-80c21799-19c6-1198-2255-31aa55463b1e [ 264.672688] NVRM: Xid (PCI:0000:01:00): 45, pid=1781, name=modprobe, Ch 00000000 [ 264.673536] NVRM: Xid (PCI:0000:01:00): 45, pid=1781, name=modprobe, Ch 00000001 [ 264.674314] NVRM: Xid (PCI:0000:01:00): 45, pid=2788, name=Xorg.bin, Ch 00000002 [ 264.675135] NVRM: Xid (PCI:0000:01:00): 45, pid=2788, name=Xorg.bin, Ch 00000003 [ 264.676290] NVRM kbusVerifyBar2_GM107: MMUTest BAR0 window offset 0x70d000 returned garbage 0x0 [ 264.676296] NVRM nvAssertOkFailedNoLog: Assertion failed: Generic memory error [NV_ERR_MEMORY_ERROR] (0x00000072) returned from kbusVerifyBar2_HAL(pGpu, pKernelBus, NULL, NULL, 0, 0) @ kern_bus_gm107.c:457 [ 264.676299] NVRM nvAssertOkFailedNoLog: Assertion failed: Generic memory error [NV_ERR_MEMORY_ERROR] (0x00000072) returned from gpuStateLoad(pGpu, IS_GPU_GC6_STATE_EXITING(pGpu) ? GPU_STATE_FLAGS_PRESERVING | GPU_STATE_FLAGS_PM_TRANSITION | GPU_STATE_FLAGS_GC6_TRANSITION : GPU_STATE_FLAGS_PRESERVING | GPU_STATE_FLAGS_PM_TRANSITION) @ gpu_suspend.c:247 [ 264.678312] NVRM: Xid (PCI:0000:01:00): 45, pid=1781, name=modprobe, Ch 00000000 [ 264.679493] NVRM: Xid (PCI:0000:01:00): 45, pid=1781, name=modprobe, Ch 00000001 [ 264.680580] NVRM: Xid (PCI:0000:01:00): 45, pid=2788, name=Xorg.bin, Ch 00000002 [ 264.681653] NVRM: Xid (PCI:0000:01:00): 45, pid=2788, name=Xorg.bin, Ch 00000003 [ 264.690483] NVRM nvCheckOkFailedNoLog: Check failed: Failure: Generic Error [NV_ERR_GENERIC] (0x0000FFFF) returned from pRmApi->Control(pRmApi, nv->rmapi.hClient, nv->rmapi.hSubDevice, NV2080_CTRL_CMD_INTERNAL_DISPLAY_UNIX_CONSOLE, &unixConsoleParams, sizeof(unixConsoleParams)) @ unix_console.c:105 [ 264.690775] NVRM rpcRmApiAlloc_GSP: GspRmAlloc failed: hClient=0xc1d00001; hParent=0x00010001; hObject=0x00010011; hClass=0x0000c670; paramsSize=0x00000000; paramsStatus=0x00000062; status=0x00000062 [ 264.690781] nvidia-modeset: ERROR: GPU:0: Failed to initialize display engine: 0x62 (Reset required [NV_ERR_RESET_REQUIRED]) [ 264.690799] NVRM serverFreeResourceTree: hObject 0x10011 not found for client 0xc1d00001 [ 264.691195] NVRM nvCheckOkFailedNoLog: Check failed: Failure: Generic Error [NV_ERR_GENERIC] (0x0000FFFF) returned from pRmApi->Control(pRmApi, nv->rmapi.hClient, nv->rmapi.hSubDevice, NV2080_CTRL_CMD_INTERNAL_DISPLAY_UNIX_CONSOLE, &unixConsoleParams, sizeof(unixConsoleParams)) @ unix_console.c:105 [ 264.691372] NVRM rpcRmApiAlloc_GSP: GspRmAlloc failed: hClient=0xc1d00001; hParent=0x00010001; hObject=0x00010011; hClass=0x0000c670; paramsSize=0x00000000; paramsStatus=0x00000062; status=0x00000062 [ 264.691375] nvidia-modeset: ERROR: GPU:0: Failed to initialize display engine: 0x62 (Reset required [NV_ERR_RESET_REQUIRED]) [ 264.691386] NVRM serverFreeResourceTree: hObject 0x10011 not found for client 0xc1d00001 [ 264.691889] NVRM unixCallVideoBIOS: int10h(4f02, 0000) vesa call failed! (4f02, 0000) [ 264.692482] NVRM nvCheckOkFailedNoLog: Check failed: Failure: Generic Error [NV_ERR_GENERIC] (0x0000FFFF) returned from pRmApi->Control(pRmApi, nv->rmapi.hClient, nv->rmapi.hSubDevice, NV2080_CTRL_CMD_INTERNAL_DISPLAY_POST_RESTORE, &restoreParams, sizeof(restoreParams)) @ unix_console.c:197 [ 264.721179] NVRM rpcRmApiAlloc_GSP: GspRmAlloc failed: hClient=0xc1d0000b; hParent=0x01000001; hObject=0x01000012; hClass=0x0000c56f; paramsSize=0x00000168; paramsStatus=0x00000062; status=0x00000062 [ 264.721182] NVRM nvAssertFailedNoLog: Assertion failed: status == NV_OK @ kernel_channel.c:2588 [ 264.721185] NVRM nvAssertOkFailedNoLog: Assertion failed: Reset required [NV_ERR_RESET_REQUIRED] (0x00000062) returned from _kchannelSendChannelAllocRpc(pKernelChannel, pChannelGpfifoParams, pKernelChannelGroup, bFullSriov) @ kernel_channel.c:863 But the problem is with resume: ... [ 268.636544] wlp0s20f3: authenticated [ 268.654389] wlp0s20f3: associated [ 276.745060] BUG: kernel NULL pointer dereference, address: 0000000000000008 [ 276.745071] #PF: supervisor read access in kernel mode [ 276.745074] #PF: error_code(0x0000) - not-present page [ 276.745077] PGD 0 P4D 0 [ 276.745081] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 276.745086] CPU: 6 PID: 2788 Comm: Xorg.bin Tainted: G OE 6.5.9-1-default #1 openSUSE Tumbleweed eb5faaeb0a34bed614de16eec67e50ac769ec453 [ 276.745092] Hardware name: LENOVO 21D7S22N08/21D7S22N08, BIOS N3FET36W (1.21 ) 05/31/2023 [ 276.745095] RIP: 0010:EvoIsChannelMethodPendingC3+0x22/0xc0 [nvidia_modeset] [ 276.745174] Code: 00 00 00 00 00 00 00 00 f3 0f 1e fa 41 55 89 d0 49 89 cd 41 b8 14 00 00 00 41 54 49 89 c4 55 48 89 fd 53 48 89 f3 48 83 ec 28 <8b> 56 08 48 c7 44 24 14 00 00 00 00 48 8d 4c 24 08 48 c1 e2 20 48 [ 276.745177] RSP: 0018:ffffa72880d57b30 EFLAGS: 00010286 [ 276.745182] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffa72880d57b8f [ 276.745184] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff933cb01c2008 [ 276.745185] RBP: ffff933cb01c2008 R08: 0000000000000014 R09: ffffa72882ccd008 [ 276.745187] R10: ffffa72881921008 R11: 000000000003f0e0 R12: 0000000000000000 [ 276.745189] R13: ffffa72880d57b8f R14: ffffa72880d57d30 R15: 0000000000000001 [ 276.745191] FS: 00007f743ce03980(0000) GS:ffff93434f700000(0000) knlGS:0000000000000000 [ 276.745193] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 276.745195] CR2: 0000000000000008 CR3: 0000000107780000 CR4: 0000000000f50ee0 [ 276.745197] PKRU: 55555554 [ 276.745199] Call Trace: [ 276.745202] <TASK> [ 276.745205] ? __die+0x23/0x70 [ 276.745212] ? page_fault_oops+0x14d/0x490 [ 276.745217] ? EvoIsModePossibleC3+0xe1/0x5b0 [nvidia_modeset 2547d6f3000deb268fd07ecb612b5ef73687c832] [ 276.745269] ? exc_page_fault+0x71/0x160 [ 276.745275] ? asm_exc_page_fault+0x26/0x30 [ 276.745279] ? EvoIsChannelMethodPendingC3+0x22/0xc0 [nvidia_modeset 2547d6f3000deb268fd07ecb612b5ef73687c832] [ 276.745326] nvRMIdleBaseChannel+0x6b/0xf0 [nvidia_modeset 2547d6f3000deb268fd07ecb612b5ef73687c832] [ 276.745385] nvSetDispModeEvo+0x12c9/0x42f0 [nvidia_modeset 2547d6f3000deb268fd07ecb612b5ef73687c832] [ 276.745442] ? Flip+0xf0/0xf0 [nvidia_modeset 2547d6f3000deb268fd07ecb612b5ef73687c832] [ 276.745501] nvKmsIoctl+0xdc/0x220 [nvidia_modeset 2547d6f3000deb268fd07ecb612b5ef73687c832] [ 276.745557] nvkms_ioctl+0x109/0x170 [nvidia_modeset 2547d6f3000deb268fd07ecb612b5ef73687c832] [ 276.745587] nvidia_frontend_unlocked_ioctl+0x3c/0x60 [nvidia ce71fbe41fb2be9720a1b7ffb01074e41d182b8e] [ 276.745757] __x64_sys_ioctl+0x94/0xd0 [ 276.745763] do_syscall_64+0x5d/0x90 [ 276.745768] ? do_user_addr_fault+0x179/0x640 [ 276.745772] ? exit_to_user_mode_prepare+0x133/0x1f0 [ 276.745778] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 [ 276.745781] RIP: 0033:0x7f743cd139cf [ 276.745839] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 276.745842] RSP: 002b:00007ffc7c213670 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 276.745845] RAX: ffffffffffffffda RBX: 00000000c0106d00 RCX: 00007f743cd139cf [ 276.745846] RDX: 00007ffc7c2136d0 RSI: 00000000c0106d00 RDI: 0000000000000014 [ 276.745848] RBP: 00007ffc7c2136d0 R08: 0000000000000000 R09: 0000555aa6b25490 [ 276.745849] R10: 00007ffc7c22aa40 R11: 0000000000000246 R12: 0000000000000014 [ 276.745851] R13: 00007f743c41cbc8 R14: 00007ffc7c215fd8 R15: 0000000000000003 [ 276.745854] </TASK> [ 276.745855] Modules linked in: ccm cmac algif_hash algif_skcipher af_alg af_packet joydev nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct bnep nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security btusb btrtl btbcm btintel btmtk bluetooth nfnetlink uvcvideo videobuf2_vmalloc uvc videobuf2_memops videobuf2_v4l2 ebtable_filter ebtables videodev ip6table_filter videobuf2_common ip6_tables ecdh_generic iptable_filter bpfilter qrtr nvidia_drm(OE) nvidia_modeset(OE) nvidia_uvm(OE) binfmt_misc snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_usb_audio snd_usbmidi_lib snd_ump snd_rawmidi snd_seq_device mc snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic xfs snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink [ 276.745909] soundwire_cadence snd_sof_intel_hda nls_iso8859_1 snd_sof_pci nls_cp437 snd_sof_xtensa_dsp vfat snd_sof fat snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus iwlmvm snd_soc_core intel_uncore_frequency intel_uncore_frequency_common snd_compress intel_tcc_cooling snd_pcm_dmaengine mac80211 libarc4 x86_pkg_temp_thermal intel_powerclamp snd_hda_intel coretemp snd_intel_dspcfg snd_intel_sdw_acpi kvm_intel snd_hda_codec nvidia(OE) iwlwifi spi_nor snd_hda_core iTCO_wdt think_lmi mei_wdt pmt_telemetry processor_thermal_device_pci intel_pmc_bxt kvm mei_hdcp mei_pxp mtd iTCO_vendor_support processor_thermal_device snd_hwdep intel_rapl_msr pmt_class igc irqbypass pcspkr thunderbolt cfg80211 firmware_attributes_class wmi_bmof thinkpad_acpi processor_thermal_rfim i2c_i801 snd_pcm mei_me processor_thermal_mbox spi_intel_pci ledtrig_audio processor_thermal_rapl spi_intel i2c_smbus platform_profile snd_timer mei intel_rapl_common rfkill [ 276.745959] thermal intel_vsec fan snd int3403_thermal soundcore ac int340x_thermal_zone intel_hid int3400_thermal intel_pmc_core acpi_pad sparse_keymap acpi_thermal_rel acpi_tad tiny_power_button fuse efi_pstore configfs dmi_sysfs ip_tables x_tables dm_crypt essiv authenc trusted asn1_encoder tee hid_logitech_hidpp hid_logitech_dj hid_generic usbhid crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel xhci_pci rtsx_pci_sdmmc sha512_ssse3 xhci_pci_renesas mmc_core xhci_hcd aesni_intel ucsi_acpi nvme typec_ucsi crypto_simd cryptd usbcore nvme_core roles rtsx_pci typec button video battery wmi pinctrl_alderlake serio_raw br_netfilter btrfs bridge stp llc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sd_mod t10_pi sg scsi_mod blake2b_generic libcrc32c scsi_common crc32c_intel xor msr raid6_pq dm_mirror dm_region_hash dm_log dm_mod bbswitch(O) efivarfs [ 276.746018] CR2: 0000000000000008 [ 276.746021] ---[ end trace 0000000000000000 ]--- [ 276.746023] RIP: 0010:EvoIsChannelMethodPendingC3+0x22/0xc0 [nvidia_modeset] [ 276.746071] Code: 00 00 00 00 00 00 00 00 f3 0f 1e fa 41 55 89 d0 49 89 cd 41 b8 14 00 00 00 41 54 49 89 c4 55 48 89 fd 53 48 89 f3 48 83 ec 28 <8b> 56 08 48 c7 44 24 14 00 00 00 00 48 8d 4c 24 08 48 c1 e2 20 48 [ 276.746073] RSP: 0018:ffffa72880d57b30 EFLAGS: 00010286 [ 276.746076] RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffa72880d57b8f [ 276.746077] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff933cb01c2008 [ 276.746079] RBP: ffff933cb01c2008 R08: 0000000000000014 R09: ffffa72882ccd008 [ 276.746080] R10: ffffa72881921008 R11: 000000000003f0e0 R12: 0000000000000000 [ 276.746082] R13: ffffa72880d57b8f R14: ffffa72880d57d30 R15: 0000000000000001 [ 276.746083] FS: 00007f743ce03980(0000) GS:ffff93434f700000(0000) knlGS:0000000000000000 [ 276.746085] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 276.746087] CR2: 0000000000000008 CR3: 0000000107780000 CR4: 0000000000f50ee0 [ 276.746089] PKRU: 55555554 [ 276.746090] note: Xorg.bin[2788] exited with irqs disabled $ rpm -qa |grep -i -e nvidia kernel-firmware-nvidia-gsp-G06-525.116.04-2.1.x86_64 kernel-firmware-nvidia-gspx-G06-535.113.01-1.1.x86_64 nvidia-compute-G06-32bit-535.129.03-15.1.x86_64 libva-nvidia-driver-0.0.9-1.10.x86_64 libnvidia-egl-wayland1-1.1.12-1.2.x86_64 nvidia-compute-G06-535.129.03-15.1.x86_64 kernel-firmware-nvidia-gsp-G06-535.54.03-1.1.x86_64 nvidia-gl-G06-535.129.03-15.1.x86_64 nvidia-gl-G06-32bit-535.129.03-15.1.x86_64 nvidia-open-driver-G06-signed-kmp-default-535.129.03_k6.5.9_1-55.2.x86_64 nvidia-video-G06-32bit-535.129.03-15.1.x86_64 nvidia-open-driver-G06-signed-kmp-default-535.113.01_k6.5.6_1-51.3.x86_64 kernel-firmware-nvidia-gspx-G06-535.129.03-11.1.x86_64 nvidia-video-G06-535.129.03-15.1.x86_64 kernel-firmware-nvidia-20231019-1.1.noarch $ lspci |grep -i vga 01:00.0 VGA compatible controller: NVIDIA Corporation GA107GLM [RTX A1000 Laptop GPU] (rev a1) $ lsgpu card0 10de:25b9 drm:/dev/dri/card0 └─renderD128 drm:/dev/dri/renderD128 [1] https://sndirsch.github.io/nvidia/2022/06/07/nvidia-opengpu.html [2] https://download.nvidia.com/XFree86/Linux-x86_64/535.129.03/README/powerman… -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1218114] New: modprobe wireguard broken on ppc64le
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218114 Bug ID: 1218114 Summary: modprobe wireguard broken on ppc64le Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Networking Assignee: kernel-bugs(a)suse.de Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- It's not possible to modprobe wireguard on Tumbleweed ppc64le: Failure started with kernel 6.6 (first failure on 6.6.1, last ok was in 6.5.9). # modprobe wireguard; echo $? modprobe: ERROR: could not insert 'wireguard': No such device 1 Module exists and modinfo works: $ rpm -ql kernel-default |grep wireguard /usr/lib/modules/6.6.6-1-default/kernel/drivers/net/wireguard /usr/lib/modules/6.6.6-1-default/kernel/drivers/net/wireguard/wireguard.ko.zst $ modinfo wireguard; echo $? filename: /usr/lib/modules/6.6.6-1-default/kernel/drivers/net/wireguard/wireguard.ko.zst alias: net-pf-16-proto-16-family-wireguard ... 0 # modprobe -v wireguard insmod /usr/lib/modules/6.6.6-1-default/kernel/lib/crypto/libpoly1305.ko.zst insmod /usr/lib/modules/6.6.6-1-default/kernel/lib/crypto/libchacha.ko.zst insmod /usr/lib/modules/6.6.6-1-default/kernel/lib/crypto/libcurve25519-generic.ko.zst insmod /usr/lib/modules/6.6.6-1-default/kernel/net/ipv4/udp_tunnel.ko.zst insmod /usr/lib/modules/6.6.6-1-default/kernel/net/ipv6/ip6_udp_tunnel.ko.zst insmod /usr/lib/modules/6.6.6-1-default/kernel/arch/powerpc/crypto/chacha-p10-crypto.ko.zst modprobe: ERROR: could not insert 'wireguard': No such device We have in our ppc64le CONFIG_CRYPTO_CHACHA20_P10=m # strace modprobe -v wireguard openat(AT_FDCWD, "/sys/module/ip6_udp_tunnel/initstate", O_RDONLY|O_CLOEXEC) = 3 read(3, "live\n", 31) = 5 read(3, "", 26) = 0 close(3) = 0 openat(AT_FDCWD, "/sys/module/chacha_p10_crypto/initstate", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) newfstatat(AT_FDCWD, "/sys/module/chacha_p10_crypto", 0x7fffdd858a38, 0) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/modules/6.6.6-1-default/kernel/arch/powerpc/crypto/chacha-p10-crypto.ko.zst", O_RDONLY|O_CLOEXEC) = 3 read(3, "(\265/\375d[", 6) = 6 _llseek(3, 0, [0], SEEK_SET) = 0 read(3, "(\265/\375d", 5) = 5 mmap(NULL, 196608, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fff980f0000 read(3, "[S\315\343\0", 5) = 5 brk(0x10036350000) = 0x10036350000 read(3, "\312h\25RY \216\271;kv(\357b\343\324\263\310\250\306\227\3169\224\362\303\326\\\22+(\301"..., 7289) = 7289 mremap(0x7fff980f0000, 196608, 327680, MREMAP_MAYMOVE) = 0x7fff980a0000 read(3, " y&\220", 4) = 4 read(3, "", 4) = 0 brk(0x10036340000) = 0x10036340000 brk(0x10036330000) = 0x10036330000 init_module(0x7fff980a0010, 21595, "") = -1 ENODEV (No such device) write(2, "modprobe: ERROR: could not inser"..., 62modprobe: ERROR: could not insert 'wireguard': No such device ) = 62 I looked also at chacha-p10-crypto.ko.zst (the dependency), it's also installed but cannot be loaded: # modprobe -v chacha-p10-crypto; echo $? insmod /usr/lib/modules/6.6.6-1-default/kernel/arch/powerpc/crypto/chacha-p10-crypto.ko.zst modprobe: ERROR: could not insert 'chacha_p10_crypto': No such device 1 # strace modprobe chacha-p10-crypto ... openat(AT_FDCWD, "/sys/module/chacha_p10_crypto/initstate", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) newfstatat(AT_FDCWD, "/sys/module/chacha_p10_crypto", 0x7fffc922d618, 0) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/modules/6.6.6-1-default/kernel/arch/powerpc/crypto/chacha-p10-crypto.ko.zst", O_RDONLY|O_CLOEXEC) = 3 read(3, "(\265/\375d[", 6) = 6 _llseek(3, 0, [0], SEEK_SET) = 0 read(3, "(\265/\375d", 5) = 5 mmap(NULL, 196608, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fff88680000 read(3, "[S\315\343\0", 5) = 5 read(3, "\312h\25RY \216\271;kv(\357b\343\324\263\310\250\306\227\3169\224\362\303\326\\\22+(\301"..., 7289) = 7289 mremap(0x7fff88680000, 196608, 327680, MREMAP_MAYMOVE) = 0x7fff88630000 read(3, " y&\220", 4) = 4 read(3, "", 4) = 0 init_module(0x7fff88630010, 21595, "") = -1 ENODEV (No such device) write(2, "modprobe: ERROR: could not inser"..., 70modprobe: ERROR: could not insert 'chacha_p10_crypto': No such device ) = 70 I wonder if this can be related to bsc#1217990 (wireguard works on aarch64 and x86_64, that's because chacha-p10-crypto is ppc64le specific module): ls -la /usr/lib/sysctl.d/ /etc/sysctl.conf ls: cannot access '/etc/sysctl.conf': No such file or directory /usr/lib/sysctl.d/: total 384 drwxr-xr-x 1 root root 156 Dec 13 16:03 . dr-xr-xr-x 1 root root 988 Dec 13 18:16 .. -rw-r--r-- 1 root root 1816 Dec 12 14:01 50-coredump.conf -rw-r--r-- 1 root root 2280 Oct 23 03:13 50-default.conf -rw-r--r-- 1 root root 252 Oct 23 03:13 51-network.conf -rw-r--r-- 1 root root 951 Oct 23 03:13 52-yama.conf lrwxrwxrwx 1 root root 24 Dec 12 14:03 99-sysctl.conf -> ../../../etc/sysctl.conf -rw-r--r-- 1 root root 387 Dec 12 02:27 README For a record, found with ltp_net_features test https://openqa.opensuse.org/tests/3810783, where I also did the debugging. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1214160] New: libvirt-routed firewalld zone not functional
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214160 Bug ID: 1214160 Summary: libvirt-routed firewalld zone not functional Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a recent update of my virtual machines host (sorry for being fuzzy) I started seeing connections being dropped between the VMs and the host, specifically NFS. The interfaces are assigned to the libvirt-routed interface contributed by libvirt-daemon-driver-network. # firewall-cmd --get-active-zones (...) libvirt-routed interfaces: kubic-net-br virbr1 # rpm -qf /usr/lib/firewalld/zones/libvirt-routed.xml libvirt-daemon-driver-network-9.0.0-150500.6.11.1.x86_64 Once enabling firewalld dropped packages logging I see log entries such as Aug 10 13:08:02 vmhost002 kernel: "filter_IN_policy_libvirt-to-host_REJECT: "IN=virbr1 OUT= MAC=52:54:00:33:68:12:52:54:00:ce:5c:25:08:00 SRC=10.25.1.6 DST=10.25.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=54291 DF PROTO=TCP SPT=943 DPT=2049 WINDOW=64240 RES=0x00 SYN URGP=0 The nfs service should be allowed # firewall-cmd --info-zone=libvirt-routed | grep services services: http mountd mysql nfs rpc-bind # firewall-cmd --info-service=nfs nfs ports: 2049/tcp protocols: source-ports: modules: destination: includes: helpers: What is worrying me and pointing to a bug are the following messages from the system journal which point to the firewalld zone not being functional Aug 09 13:12:36 vmhost002 firewalld[17692]: ERROR: Calling pre func <bound method Firewall.full_check_config of <class 'firewall.core.fw.Firewall'>(True, True, True, 'RUNNING', False, 'public', {'nf_nat_tftp': 4}, [], True, True, True, False, 'all')>(()) failed: INVALID_ZONE: 'libvirt-routed' not among existing zones Aug 09 13:12:36 vmhost002 firewalld[17692]: ERROR: Calling pre func <bound method Firewall.full_check_config of <class 'firewall.core.fw.Firewall'>(True, True, True, 'RUNNING', False, 'public', {'nf_nat_tftp': 4}, [], True, True, True, False, 'all')>(()) failed: INVALID_ZONE: 'libvirt-routed' not among existing zones Aug 09 13:13:33 vmhost002 firewalld[17692]: ERROR: Calling pre func <bound method Firewall.full_check_config of <class 'firewall.core.fw.Firewall'>(True, True, True, 'INIT', False, 'public', {}, [], True, True, True, False, 'all')>(()) failed: INVALID_ZONE: 'libvirt-routed' not among existing zones Aug 09 13:13:33 vmhost002 firewalld[17692]: ERROR: Calling pre func <bound method Firewall.full_check_config of <class 'firewall.core.fw.Firewall'>(True, True, True, 'INIT', False, 'public', {'nf_nat_tftp': 1}, [], True, True, True, False, 'all')>(()) failed: INVALID_ZONE: 'libvirt-routed' not among existing zones Happy to provide more information if needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1217751] New: PETSc packaging is broken
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1217751 Bug ID: 1217751 Summary: PETSc packaging is broken 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: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This is partly a rant, partly a cry for help brought about by trying to build a package that depends on petsc as it appears in Factory. TL;DR it is hell! The various flavours of the PETSc package install their headers and libraries to multiple non-standard locations (even after accounting for mpi paths). For example: * petsc-serial - Headers are in the `/usr/lib64/petsc/3.18.5/linux-gnu-c-opt/include/` dir, they should be somewhere in `/usr/include` - Shared lib is in `/usr/lib64/petsc/3.18.5/linux-gnu-c-opt/lib/`; should be in `/usr/lib64/petsc` at worst. - Pkgconfig file is in `/usr/lib64/petsc/3.18.5/linux-gnu-c-opt/lib/pkgconfig/` where pkgconfig does not even look. Not surprisingly, installing petsc-devel and doing `pkgconfig --libs petsc` does not work. Side note: there is also a bonus 0 byte PETSc.pc file in the same dir. `petsc.pc` should be installed to `/usr/lib64/pkgconfig` - There is a supposedly-arch independent `share` dir in `/usr/lib64/petsc/3.18.5/linux-gnu-c-opt` * petsc-openmpi4-devel (and other mpi/hpc flavours I have not dared to look into) - Headers: `/usr/lib64/mpi/gcc/openmpi4/lib64/petsc/3.18.5/linux-gnu-c-opt/include/` - Shared lib and pkgconfig file: `/./usr/lib64/mpi/gcc/openmpi4/lib64/petsc/3.18.5/linux-gnu-c-opt/lib/` ... You get the idea. There is no predictability to determining paths to headers and libraries when using petsc as a dependency. Obviously, with the above setup, pkg-config goes out of the window and there is nothing to make up for it, no petsc-config binary or such. Imagine that petsc gets update to version 3.20.0, dependent packages have to modify their specfiles to get the include path right again. And please don't tell me to use gymnastics like: ``` %define petsc_version %(rpm -q --queryformat="%%{version}" petsc-openmpi4-devel) %define petsc_path %{openmpi_prefix}/%{_lib}/petsc/%{petsc_version}/linux-gnu-c-opt ``` Partly, I was looking into updating petsc to version 3.20.0, but the specfile scared me a little bit, I won't lie. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215981] New: Black Screen during boot on both internal and external screen in kernel 6.5.4-1 on Thinkpad P16 (Discrete Graphics mode)
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1215981 Bug ID: 1215981 Summary: Black Screen during boot on both internal and external screen in kernel 6.5.4-1 on Thinkpad P16 (Discrete Graphics mode) 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have similar problem to #1213693, but on newer kernel 6.5.4-1, which should contain the fix. #1213693 was broken by commit ca62297b2085 ("drm/edid: Fix csync detailed mode parsing") in v6.4-rc1, which was fixed by revert it in 50b6f2c82977 ("Revert "drm/edid: Fix csync detailed mode parsing"") in v6.5-rc7. In my case I'm not able to see anything after kernel being loaded. I have Tumbleweed kernel 6.5.4-1 and 6.5.2-1. Problem is on Thinkpad P16 with 2 GPU: 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-HX GT1 [UHD Graphics 770] (rev 0c) 01:00.0 VGA compatible controller: NVIDIA Corporation GA107GLM [RTX A1000 Laptop GPU] (rev a1) The problem is on "Discrete Graphics" (Nvidia only) mode. "Hybrid Graphics" (Intel + Nvidia) works, but I need for external screen to use "Discrete Graphics" as it's the only way to get external screens working (because external output is wired only to nvidia): i.e. on Discrete Graphics there is only Intel card being used $ drm_info |grep -i node: -A1 Node: /dev/dri/card0 Driver: i915 (Intel Graphics) version 1.6.0 (20201103) I tested with internal screen only and with internal screen + 2 external GPU. I tested to disable plymouth with rd.plymouth=0 plymouth.enable=0 plymouth=0 cmdline args, also tried fbcon=map:1 also boot to runlevel 1 and 3 instead the default. None helped. $ rpm -qa |grep -i -e nouveau -e intel -e ^kernel kernel-firmware-nvidia-gsp-G06-525.116.04-2.1.x86_64 kernel-firmware-nvidia-gspx-G06-535.113.01-1.1.x86_64 kernel-firmware-serial-20230829-1.1.noarch libdrm_nouveau2-2.4.116-2.1.x86_64 intel-vaapi-driver-2.4.1-5.11.x86_64 kernel-firmware-mwifiex-20230829-1.1.noarch xf86-video-intel-2.99.917.916_g31486f40-3.6.x86_64 kernel-firmware-platform-20230829-1.1.noarch kernel-firmware-intel-20230829-1.1.noarch kernel-firmware-iwlwifi-20230829-1.1.noarch kernel-firmware-all-20230829-1.1.noarch intel-media-driver-23.3.3-1.1.x86_64 ucode-intel-20230808-1.1.x86_64 kernel-firmware-nvidia-gsp-G06-535.54.03-1.1.x86_64 kernel-firmware-amdgpu-20230829-1.1.noarch kernel-firmware-usb-network-20230829-1.1.noarch kernel-firmware-i915-20230829-1.1.noarch kernel-macros-6.5.4-1.1.noarch kernel-firmware-qcom-20230829-1.1.noarch libvulkan_intel-23.2.0-1699.360.pm.1.x86_64 intel-gpu-tools-1.27.1-2.3.x86_64 kernel-firmware-sound-20230829-1.1.noarch kernel-firmware-ath10k-20230829-1.1.noarch libvdpau_nouveau-23.2.0-1699.360.pm.1.x86_64 kernel-firmware-bnx2-20230829-1.1.noarch Mesa-dri-nouveau-23.2.0-1699.360.pm.1.x86_64 kernel-firmware-dpaa2-20230829-1.1.noarch kernel-firmware-atheros-20230829-1.1.noarch kernel-firmware-radeon-20230829-1.1.noarch kernel-firmware-ueagle-20230829-1.1.noarch kernel-firmware-brcm-20230829-1.1.noarch kernel-firmware-chelsio-20230829-1.1.noarch kernel-firmware-nvidia-20230829-1.1.noarch kernel-firmware-ti-20230829-1.1.noarch kernel-firmware-media-20230829-1.1.noarch kernel-firmware-realtek-20230829-1.1.noarch kernel-firmware-mellanox-20230829-1.1.noarch libdrm_intel1-2.4.116-2.1.x86_64 kernel-firmware-network-20230829-1.1.noarch kernel-firmware-ath11k-20230829-1.1.noarch kernel-firmware-mediatek-20230829-1.1.noarch kernel-firmware-bluetooth-20230829-1.1.noarch kernel-firmware-prestera-20230829-1.1.noarch kernel-firmware-liquidio-20230829-1.1.noarch kernel-firmware-marvell-20230829-1.1.noarch kernel-default-6.5.2-1.1.x86_64 kernel-firmware-nfp-20230829-1.1.noarch kernel-default-devel-6.5.2-1.1.x86_64 kernel-devel-6.5.4-1.1.noarch kernel-firmware-qlogic-20230829-1.1.noarch kernel-default-devel-6.5.4-1.1.x86_64 kernel-default-6.5.4-1.1.x86_64 kernel-devel-6.5.2-1.1.noarch $ lsmod |grep -i -e i915 -e nvidia -e nouveau nvidia_drm 94208 0 nvidia_modeset 1794048 1 nvidia_drm nvidia_uvm 3608576 0 i915 4087808 5 drm_buddy 20480 1 i915 i2c_algo_bit 20480 1 i915 drm_display_helper 237568 1 i915 ttm 102400 1 i915 cec 90112 2 drm_display_helper,i915 nvidia 8843264 2 nvidia_uvm,nvidia_modeset video 77824 3 thinkpad_acpi,i915,nvidia_modeset $ modinfo nvidia |grep -i version version: 535.113.01 srcversion: 81566B70A70B0B19F40FD1A vermagic: 6.5.4-1-default SMP preempt mod_unload modversions $ cat /proc/cmdline # but I tested with others, see above BOOT_IMAGE=/boot/vmlinuz-6.5.4-1-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap mitigations=auto quiet security=apparmor modprobe.blacklist=i915 nosimplefb=1 I use these non-factory repos: https://download.opensuse.org/repositories/X11:/Drivers:/Video:/Redesign/op… https://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Tumbleweed/ https://download.nvidia.com/opensuse/tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 45

[Bug 1219188] New: [Build 20240123] kernel 6.7.1: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219188 Bug ID: 1219188 Summary: [Build 20240123] kernel 6.7.1: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jack(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Starting from build 20240123, which brought kernel 6.7 splice fail: splice07.c:54: TFAIL: splice() on /dev/zero -> pipe write end succeeded Jan, could you please have look whether it's a test bug or mainline kernel bug? I can reproduce the problem also on mainline 6.8.0-rc1 (testing with rapido). -- You are receiving this mail because: You are on the CC list for the bug.

1 7

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

02 Apr '24

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

1 25

[Bug 1215987] New: Slowroll - XDM doesn't launch default Plasma X11 session
by bugzilla_noreply＠suse.com 31 Mar '24

31 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1215987 Bug ID: 1215987 Summary: Slowroll - XDM doesn't launch default Plasma X11 session Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: bwiedemann(a)suse.com, msrb(a)suse.com, werner(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Initial Summary: Slowroll - XDM doesn't launch default Plasma X11 session To reproduce: 1-install minimal X role 2-install patterns-kde-kde_plasma constrained by solver.onlyRequires = true 3-ensure no DM is installed except XDM 4-ensure plasma5.desktop is the default xsession : # inxi -S System: Host: ara88 Kernel: 6.4.12-1-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Tumbleweed-Slowroll 20231001 # update-alternatives --display default-displaymanager default-displaymanager - manual mode link best version is /usr/lib/X11/displaymanagers/xdm link currently points to /usr/lib/X11/displaymanagers/xdm link default-displaymanager is /usr/lib/X11/displaymanagers/default-displaymanager /usr/lib/X11/displaymanagers/console - priority 5 /usr/lib/X11/displaymanagers/xdm - priority 10 # update-alternatives --display default-xsession.desktop default-xsession.desktop - manual mode link best version is /usr/share/xsessions/plasma5.desktop link currently points to /usr/share/xsessions/plasma5.desktop link default-xsession.desktop is /usr/share/xsessions/default.desktop /usr/share/xsessions/icewm-session.desktop - priority 15 /usr/share/xsessions/plasma5.desktop - priority 25 # Actual behavior: 1-yellow-gray display screens with a decoration-free Xterm launch 2-WINDOWMANAGER=startplasma-x11 startx in the Xterm launches an apparently normal Plasma session Expected behavior: 1-Plasma session launches directly Additional information: 1-This is not unique to Slowroll, or this particular PC. I have it happening in Leap installations as well. This particular Slowroll was was born as a zypper dup from a cloned 15.5, which has the same problem. 2-This is not a recent development. ISTR 15.4 did it too, at least 6 months ago, but rather than reporting I installed KDM3 or TDM on them instead of keeping XDM only. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1218961] New: SeaMonkey: update to 2.53.18.1
by bugzilla_noreply＠suse.com 28 Mar '24

28 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218961 Bug ID: 1218961 Summary: SeaMonkey: update to 2.53.18.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de CC: Andreas.Stieger(a)gmx.de, factory-mozilla(a)lists.opensuse.org, linux(a)daniel-bauer.com, maintenance(a)opensuse.org, Manfred.Haertel(a)rz-online.de, meissner(a)suse.com, qa-bugs(a)suse.de, security-team(a)suse.de, wolfgang.engel(a)suse.com Depends on: 1217916 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1217916 +++ Please update the SeaMonkey package in 15.5 and 15.6 to the SeaMonkey 2.53.18.1 packages provided by the mozilla/seamonkey package on OBS: <https://build.opensuse.org/package/show/mozilla/seamonkey> The latest version of SeaMonkey, 2.53.18.1, released on 16 January 2024, contains new backports of important security fixes from Firefox 115.7 and Thunderbird 115.7 ESR. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213659] New: VUL-0: CVE-2023-38496: apptainer: Ineffective privileges drop when requesting container network
by bugzilla_noreply＠suse.com 28 Mar '24

28 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1213659 Bug ID: 1213659 Summary: VUL-0: CVE-2023-38496: apptainer: Ineffective privileges drop when requesting container network Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/373431/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: cgoll(a)suse.com Reporter: gianluca.gabrielli(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Apptainer is an open source container platform. Version 1.2.0-rc.2 introduced an ineffective privilege drop when requesting container network setup, therefore subsequent functions are called with root privileges, the attack surface is rather limited for users but an attacker could possibly craft a starter config to delete any directory on the host filesystems. A security fix has been included in Apptainer 1.2.1. There is no known workaround outside of upgrading to Apptainer 1.2.1. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38496 https://bugzilla.redhat.com/show_bug.cgi?id=2226582 https://www.cve.org/CVERecord?id=CVE-2023-38496 http://www.cvedetails.com/cve/CVE-2023-38496/ https://github.com/apptainer/apptainer/pull/1523 https://github.com/apptainer/apptainer/pull/1578 https://github.com/apptainer/apptainer/security/advisories/GHSA-mmx5-32m4-w… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1214850] New: open-vm-tools 12.3.0 has been released - please rebase
by bugzilla_noreply＠suse.com 27 Mar '24

27 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1214850 Bug ID: 1214850 Summary: open-vm-tools 12.3.0 has been released - please rebase Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: jwolfe(a)vmware.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- open-vm-tools 12.3.0 was released on Aug. 31, 2023. Also affects project (?) Also affects distribution/package Edit Bug Description There are no new features in the open-vm-tools 12.3.0 release. This is primarily a maintenance release that addresses a few critical problems, including: This release resolves CVE-2023-20900. For more information on this vulnerability and its impact on VMware products, see https://www.vmware.com/security/advisories/VMSA-2023-0019.html. A tools.conf configuration setting is available to temporaily direct Linux quiesced snaphots to restore pre open-vm-tools 12.2.0 behavior of ignoring file systems already frozen. Building of the VMware Guest Authentication Service (VGAuth) using "xml-security-c" and "xerces-c" is being deprecated. A number of Coverity reported issues have been addressed. A number of GitHub issues and pull requests have been handled. Please see the Resolves Issues section of the Release Notes. For issues resolved in this release, see the Resolved Issues section of the Release Notes. For complete details, see: https://github.com/vmware/open-vm-tools/releases/tag/stable-12.3.0 Release Notes are available at https://github.com/vmware/open-vm-tools/blob/stable-12.3.0/ReleaseNotes.md The granular changes that have gone into the 12.3.0 release are in the ChangeLog at https://github.com/vmware/open-vm-tools/blob/stable-12.3.0/open-vm-tools/Ch… Note: With the changes upstreamed and the fix for CVE-2023-20867 in the source, you may not need the following patches in your open-vm-toold pacjage build: 0001-build-put-l-specifiers-into-LIBADD-not-LDFLAGS.patch 0002-build-use-grpc-pkgconfig-to-retrieve-flags-libraries.patch 2023-20867-Remove-some-dead-code.patch detect-suse-location.patch Please rebase open-vm-tools version 12.3.0 in supported releases of SLES 12 and SLES 15 for x86_64/amd64 and aarch64/ARM64 architectures as appropriate. -- You are receiving this mail because: You are on the CC list for the bug.

1 9