August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1226101] New: Joystick and steering wheel not found in system settings
by bugzilla_noreply＠suse.com 07 Dec '24

07 Dec '24

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 2

[Bug 1229724] New: Wireshark connections started at login - even without network
by bugzilla_noreply＠suse.com 06 Dec '24

06 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1229724 Bug ID: 1229724 Summary: Wireshark connections started at login - even without network Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a wireshark VPN configured. After login the wireshark connection gets activated, even without having a network connection established (kwallet asks for the password). wireshark has the flag 'connect automatically with priority' set (I guess a default setting), but a) I dont really know what it does and b) it does not make sense to connect if the wifi connection is not established. I reported this to the KDE bugtracker as well: https://bugs.kde.org/show_bug.cgi?id=484542 but I guess its not a KDE, more a NM problem Operating System: openSUSE Tumbleweed 20240823 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.5-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227710] New: NetworkManager-openvpn must use --data-ciphers for OpenVPN >= 2.6
by bugzilla_noreply＠suse.com 06 Dec '24

06 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1227710 Bug ID: 1227710 Summary: NetworkManager-openvpn must use --data-ciphers for OpenVPN >= 2.6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/ -/issues/97 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: adrian.glaubitz(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recently, one of my OpenVPN connections stopped working with every connection attempt timing out. After some debugging and research, I figured out that the reason is that OpenVPN 2.6 deprecated the "--cipher" option and replaced it with "--data-ciphers". There is an upstream bug report which tracks the issue: > https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/97 While there have been changes made to the code to address this issue, > https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/commit/963b71a83ee1… > https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/commit/020ab0c4b872… the issue doesn't seem to be resolved yet as my own experiences and the comments of other users in the above upstream bug report suggest. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1229726] New: [Base:System/pcp] (Micro-OS) pcp package ships invalid tmpfiles with read-only filesystem
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1229726 Bug ID: 1229726 Summary: [Base:System/pcp] (Micro-OS) pcp package ships invalid tmpfiles with read-only filesystem Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc(a)user.net Reporter: rein+suse(a)purelymail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The pcp package ships a bunch of symlinks found in /usr/lib/tmpfiles.d/pcp.conf which cannot be created in Micro-OS. This causes 9 errors to be logged to the journal: symlink(../../../../usr/libexec/pcp/pmns/lockpmns, /usr/share/pcp/lib/lockpmns) failed: Read-only file system symlink(../../../../usr/libexec/pcp/pmns/unlockpmns, /usr/share/pcp/lib/unlockpmns) failed: Read-only file system symlink(../../../../usr/libexec/pcp/pmns/ReplacePmnsSubtree, /usr/share/pcp/lib/ReplacePmnsSubtree) failed: Read-only file system symlink(../../../../usr/libexec/pcp/lib/pmdaproc.sh, /usr/share/pcp/lib/pmdaproc.sh) failed: Read-only file system symlink(../../../../usr/libexec/pcp/lib/rc-proc.sh, /usr/share/pcp/lib/rc-proc.sh) failed: Read-only file system symlink(../../../../usr/libexec/pcp/lib/rc-proc.sh.minimal, /usr/share/pcp/lib/rc-proc.sh.minimal) failed: Read-only file system symlink(../../../../usr/libexec/pcp/lib/bashproc.sh, /usr/share/pcp/lib/bashproc.sh) failed: Read-only file system symlink(../../../../usr/libexec/pcp/lib/utilproc.sh, /usr/share/pcp/lib/utilproc.sh) failed: Read-only file system symlink(../../../../usr/libexec/pcp/lib/checkproc.sh, /usr/share/pcp/lib/checkproc.sh) failed: Read-only file system -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1229279] New: Bluetooth network connection is slow
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1229279 Bug ID: 1229279 Summary: Bluetooth network connection is slow Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, I am running openSUSE Leap 15.6 with kernel 6.4.0-150600.21-default My host Bluetooth hardware is Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface I've found that connection to the network using Bluetooth stopped worked for me (last time I checked Bluetooth networking was at Leap 15.3/15.4 times, and there was no issue). While the connection is successfully established, the connection is slow and latency is quite huge. For instance: PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=58 time=10110 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=58 time=10172 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=58 time=10048 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=58 time=9497 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=58 time=9472 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=58 time=9056 ms 64 bytes from 8.8.8.8: icmp_seq=7 ttl=58 time=9758 ms 64 bytes from 8.8.8.8: icmp_seq=8 ttl=58 time=9608 ms 64 bytes from 8.8.8.8: icmp_seq=9 ttl=58 time=9609 ms 64 bytes from 8.8.8.8: icmp_seq=10 ttl=58 time=9181 ms --- 8.8.8.8 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 11225ms rtt min/avg/max/mdev = 9056.183/9651.075/10172.088/358.556 ms, pipe 8 Please note, that the same smartphone connected to the host with WiFi or USB provides expected result: Internet connection is established and provides dozen Mbps. This makes me think that there is some issue within Bluetooth subsystem. nmcli c show is as following: connection.id: A41 ???????????? Matwey V. Network connection.uuid: 1bacc116-1ac9-4176-a855-15e918772164 connection.stable-id: -- connection.type: bluetooth connection.interface-name: -- connection.autoconnect: no connection.autoconnect-priority: 0 connection.autoconnect-retries: -1 (default) connection.multi-connect: 0 (default) connection.auth-retries: -1 connection.timestamp: 1723975850 connection.permissions: -- connection.zone: -- connection.master: -- connection.slave-type: -- connection.autoconnect-slaves: -1 (default) connection.secondaries: -- connection.gateway-ping-timeout: 0 connection.metered: unknown connection.lldp: default connection.mdns: -1 (default) connection.llmnr: -1 (default) connection.dns-over-tls: -1 (default) connection.mptcp-flags: 0x0 (default) connection.wait-device-timeout: -1 connection.wait-activation-delay: -1 ipv4.method: auto ipv4.dns: -- ipv4.dns-search: -- ipv4.dns-options: -- ipv4.dns-priority: 0 ipv4.addresses: -- ipv4.gateway: -- ipv4.routes: -- ipv4.route-metric: -1 ipv4.route-table: 0 (unspec) ipv4.routing-rules: -- ipv4.replace-local-rule: -1 (default) ipv4.ignore-auto-routes: no ipv4.ignore-auto-dns: no ipv4.dhcp-client-id: -- ipv4.dhcp-iaid: -- ipv4.dhcp-timeout: 0 (default) ipv4.dhcp-send-hostname: yes ipv4.dhcp-hostname: -- ipv4.dhcp-fqdn: -- ipv4.dhcp-hostname-flags: 0x0 (none) ipv4.never-default: no ipv4.may-fail: yes ipv4.required-timeout: -1 (default) ipv4.dad-timeout: -1 (default) ipv4.dhcp-vendor-class-identifier: -- ipv4.link-local: 0 (default) ipv4.dhcp-reject-servers: -- ipv4.auto-route-ext-gw: -1 (default) ipv6.method: auto ipv6.dns: -- ipv6.dns-search: -- ipv6.dns-options: -- ipv6.dns-priority: 0 ipv6.addresses: -- ipv6.gateway: -- ipv6.routes: -- ipv6.route-metric: -1 ipv6.route-table: 0 (unspec) ipv6.routing-rules: -- ipv6.replace-local-rule: -1 (default) ipv6.ignore-auto-routes: no ipv6.ignore-auto-dns: no ipv6.never-default: no ipv6.may-fail: yes ipv6.required-timeout: -1 (default) ipv6.ip6-privacy: -1 (unknown) ipv6.addr-gen-mode: default ipv6.ra-timeout: 0 (default) ipv6.mtu: auto ipv6.dhcp-pd-hint: -- ipv6.dhcp-duid: -- ipv6.dhcp-iaid: -- ipv6.dhcp-timeout: 0 (default) ipv6.dhcp-send-hostname: yes ipv6.dhcp-hostname: -- ipv6.dhcp-hostname-flags: 0x0 (none) ipv6.auto-route-ext-gw: -1 (default) ipv6.token: -- bluetooth.bdaddr: 70:1F:3C:44:22:FC bluetooth.type: panu proxy.method: none proxy.browser-only: no proxy.pac-url: -- proxy.pac-script: -- GENERAL.NAME: A41 ???????????? Matwey V. Network GENERAL.UUID: 1bacc116-1ac9-4176-a855-15e918772164 GENERAL.DEVICES: 70:1F:3C:44:22:FC GENERAL.IP-IFACE: bnep0 GENERAL.STATE: activated GENERAL.DEFAULT: yes GENERAL.DEFAULT6: yes GENERAL.SPEC-OBJECT: -- GENERAL.VPN: no GENERAL.DBUS-PATH: /org/freedesktop/NetworkManager/ActiveConnection/64 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/Settings/1 GENERAL.ZONE: -- GENERAL.MASTER-PATH: -- IP4.ADDRESS[1]: 192.168.44.85/24 IP4.GATEWAY: 192.168.44.1 IP4.ROUTE[1]: dst = 192.168.44.0/24, nh = 0.0.0.0, mt = 750 IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 192.168.44.1, mt = 750 IP4.DNS[1]: 192.168.44.1 DHCP4.OPTION[1]: broadcast_address = 192.168.44.255 DHCP4.OPTION[2]: dhcp_client_identifier = 01:cc:2f:71:d8:1f:f2 DHCP4.OPTION[3]: dhcp_lease_time = 3599 DHCP4.OPTION[4]: dhcp_server_identifier = 192.168.44.1 DHCP4.OPTION[5]: domain_name_servers = 192.168.44.1 DHCP4.OPTION[6]: expiry = 1723979449 DHCP4.OPTION[7]: host_name = alpha DHCP4.OPTION[8]: ip_address = 192.168.44.85 DHCP4.OPTION[9]: next_server = 192.168.44.1 DHCP4.OPTION[10]: requested_broadcast_address = 1 DHCP4.OPTION[11]: requested_domain_name = 1 DHCP4.OPTION[12]: requested_domain_name_servers = 1 DHCP4.OPTION[13]: requested_domain_search = 1 DHCP4.OPTION[14]: requested_host_name = 1 DHCP4.OPTION[15]: requested_interface_mtu = 1 DHCP4.OPTION[16]: requested_ms_classless_static_routes = 1 DHCP4.OPTION[17]: requested_nis_domain = 1 DHCP4.OPTION[18]: requested_nis_servers = 1 DHCP4.OPTION[19]: requested_ntp_servers = 1 DHCP4.OPTION[20]: requested_rfc3442_classless_static_routes = 1 DHCP4.OPTION[21]: requested_root_path = 1 DHCP4.OPTION[22]: requested_routers = 1 DHCP4.OPTION[23]: requested_static_routes = 1 DHCP4.OPTION[24]: requested_subnet_mask = 1 DHCP4.OPTION[25]: requested_time_offset = 1 DHCP4.OPTION[26]: requested_wpad = 1 DHCP4.OPTION[27]: routers = 192.168.44.1 DHCP4.OPTION[28]: subnet_mask = 255.255.255.0 IP6.ADDRESS[1]: 2a00:1fa0:427a:8a32:f986:3a49:ec2:5fd2/64 IP6.ADDRESS[2]: 2a00:1fa0:427a:8a32:fed3:77cf:ace8:f002/64 IP6.ADDRESS[3]: fe80::ead5:7326:bf25:2e45/64 IP6.GATEWAY: fe80::721f:3cff:fe44:22fc IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 1024 IP6.ROUTE[2]: dst = 2a00:1fa0:427a:8a32::/64, nh = ::, mt = 750 IP6.ROUTE[3]: dst = ::/0, nh = fe80::721f:3cff:fe44:22fc, mt = 20750 IP6.DNS[1]: 2a00:1fa0:427a:8a32::8 How could I debug and resolve the issue? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213380] New: Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1213380 Bug ID: 1213380 Summary: Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: samcon(a)protonmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I encountered a black screen issue while attempting to boot the openSUSE Tumbleweed ISO after the BIOS on my system. This issue specifically occurs when using a DP-HDMI video output. This problem does not arise when using the same video output with other operating systems like Leap, Fedora, and Ubuntu LTS. In those cases, I am able to get video output without any black screen problems. Steps to Reproduce: 1. Start the computer and access the BIOS. 2. Configure the boot order to prioritize booting from the openSUSE Tumbleweed ISO. 3. Save the changes and exit the BIOS. 4. The system attempts to boot from the ISO. 5. First I see the kernal or bootloader messages, then it jumps to a black screen - with waiting for source message on projector. Expected Behavior: Upon booting from the openSUSE Tumbleweed ISO, the system should display zypper installer instead of a black screen, just like other operating systems do when using the DP-HDMI video output. Additional Information: - Operating System: openSUSE Tumbleweed - Video Output: DP-HDMI - Other operating systems (Leap, Fedora, Ubuntu LTS) do not exhibit the black screen issue with the same video output. - When I connect the same system to the monitor using DP-to-DP instead of DP-to-HDMI, the video output is successfully displayed. - Have used tried with iso from few weeks back and latest Snapshot20230714-Media.iso Kind regards, Sam -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1215927] New: kernel-default-6.5.4 reboots instead of resuming from suspend
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215927 Bug ID: 1215927 Summary: kernel-default-6.5.4 reboots instead of resuming from suspend Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de CC: mrmazda(a)earthlink.net Target Milestone: --- Found By: --- Blocker: --- I upgraded from Tumbleweed 20230908 to 20230921, which included an upgrade from kernel-default-6.4.12 to kernel-default-6.5.4. I always suspend my computer at night (with systemctl suspend) and wake it the next morning. With the new kernel, the computer always restarts instead of resuming from suspend. The problem does not occur with the old kernel. Interestingly, the problem is reproducible only when I leave the computer suspended overnight. Simply suspending the computer and then waking it a few seconds later does not trigger the bug. hwinfo output (with the old kernel) is available in Attachment 869836 of Bug 1215826. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219444] New: amdgpu critical error
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1219444 Bug ID: 1219444 Summary: amdgpu critical error 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: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: teuniz(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872372 --> https://bugzilla.suse.com/attachment.cgi?id=872372&action=edit Output of dmesg The kernel crashes approx every 5 minutes. I reverted back to kernel 5.14.21-150500.55.19-default because with that one it crashes approx once a day. Operating System: openSUSE Leap 15.5 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.14.21-150500.55.44-default (64-bit) Graphics Platform: X11 Processors: 32 × 13th Gen Intel Core i9-13900K Memory: 31.0 GiB of RAM Graphics Processor: AMD Radeon Pro W6600 Manufacturer: HP Product Name: HP Z2 Tower G9 Workstation Desktop PC dmesg | grep amdgpu [ 1.540640] [drm] amdgpu kernel modesetting enabled. [ 1.540703] amdgpu: CRAT table not found [ 1.540705] amdgpu: Virtual CRAT table created for CPU [ 1.540712] amdgpu: Topology: Add CPU node [ 1.542670] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from VFCT [ 1.542671] amdgpu: ATOM BIOS: 113-D5330400-100 [ 1.542770] amdgpu 0000:03:00.0: vgaarb: deactivate vga console [ 1.542771] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default) [ 1.542799] amdgpu 0000:03:00.0: amdgpu: VRAM: 8176M 0x0000008000000000 - 0x00000081FEFFFFFF (8176M used) [ 1.542800] amdgpu 0000:03:00.0: amdgpu: GART: 512M 0x0000000000000000 - 0x000000001FFFFFFF [ 1.542801] amdgpu 0000:03:00.0: amdgpu: AGP: 267894784M 0x0000008400000000 - 0x0000FFFFFFFFFFFF [ 1.542845] [drm] amdgpu: 8176M of VRAM memory ready [ 1.542845] [drm] amdgpu: 15892M of GTT memory ready. [ 1.548699] amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist [ 1.548704] amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist [ 2.854516] amdgpu 0000:03:00.0: amdgpu: STB initialized to 2048 entries [ 2.895100] amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware [ 3.094413] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 3.115717] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 3.115740] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b2b00 (59.43.0) [ 3.115745] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched [ 3.115777] amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable [ 3.165133] amdgpu 0000:03:00.0: amdgpu: SMU is initialized successfully! [ 3.268063] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [ 3.268478] amdgpu: sdma_bitmap: ffff [ 3.302091] amdgpu: HMM registered 8176MB device memory [ 3.302135] amdgpu: SRAT table not found [ 3.302136] amdgpu: Virtual CRAT table created for GPU [ 3.302599] amdgpu: Topology: Add dGPU node [0x73e3:0x1002] [ 3.302601] kfd kfd: amdgpu: added device 1002:73e3 [ 3.302617] amdgpu 0000:03:00.0: amdgpu: SE 2, SH per SE 2, CU per SH 8, active_cu_number 28 [ 3.302658] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 3.302659] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 3.302659] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 3.302660] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 [ 3.302660] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 [ 3.302661] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 [ 3.302661] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 [ 3.302662] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 [ 3.302662] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 [ 3.302663] amdgpu 0000:03:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 [ 3.302663] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [ 3.302664] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 [ 3.302665] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1 [ 3.302665] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 1 [ 3.302666] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 1 [ 3.302666] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 1 [ 3.303573] [drm] Initialized amdgpu 3.49.0 20150101 for 0000:03:00.0 on minor 0 [ 3.308709] fbcon: amdgpudrmfb (fb0) is primary device [ 3.505728] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 3.505731] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 3.505733] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x0000073A [ 3.505733] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: DCEDMC (0x3) [ 3.505734] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x5 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [ 3.505735] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x1 [ 3.505736] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 [ 3.524299] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer device [ 4.537456] snd_hda_intel 0000:03:00.1: bound 0000:03:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [ 5.416287] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 5.416312] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 5.416319] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00000000 [ 5.416324] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: unknown (0x0) [ 5.416329] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 5.416333] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x0 [ 5.416336] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [ 5.416340] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x0 [ 5.416343] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 [ 73.156519] amdgpu 0000:03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:157 vmid:0 pasid:0, for process pid 0 thread pid 0) [ 73.156538] amdgpu 0000:03:00.0: amdgpu: in page starting at address 0x0000000006004000 from client 0x12 (VMC) [ 73.156546] amdgpu 0000:03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x0000073A [ 73.156551] amdgpu 0000:03:00.0: amdgpu: Faulty UTCL2 client ID: DCEDMC (0x3) [ 73.156562] amdgpu 0000:03:00.0: amdgpu: MORE_FAULTS: 0x0 [ 73.156566] amdgpu 0000:03:00.0: amdgpu: WALKER_ERROR: 0x5 [ 73.156570] amdgpu 0000:03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [ 73.156578] amdgpu 0000:03:00.0: amdgpu: MAPPING_ERROR: 0x1 [ 73.156582] amdgpu 0000:03:00.0: amdgpu: RW: 0x0 uname -a 5.14.21-150500.55.44-default #1 SMP PREEMPT_DYNAMIC Mon Jan 15 10:03:40 UTC 2024 (cc7d8b6) x86_64 x86_64 x86_64 GNU/Linux lspci VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 WKS-XL [Radeon PRO W6600] -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1227273] New: VUL-0: CVE-2024-39303: Weblate is a web based localization tool. Prior to version 5.6.2, Weblate didn't correctly validate filenames when restoring project backup. It may be possible to gain unauthorized access to files on the server using a crafted ...
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1227273 Bug ID: 1227273 Summary: VUL-0: CVE-2024-39303: Weblate is a web based localization tool. Prior to version 5.6.2, Weblate didn't correctly validate filenames when restoring project backup. It may be possible to gain unauthorized access to files on the server using a crafted ... Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/412574/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mcepl(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: stoyan.manolov(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Weblate is a web based localization tool. Prior to version 5.6.2, Weblate didn't correctly validate filenames when restoring project backup. It may be possible to gain unauthorized access to files on the server using a crafted ZIP file. This issue has been addressed in Weblate 5.6.2. As a workaround, do not allow untrusted users to create projects. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-39303 https://www.cve.org/CVERecord?id=CVE-2024-39303 https://github.com/WeblateOrg/weblate/commit/b6a7eace155fa0feaf01b4ac36165a… https://github.com/WeblateOrg/weblate/security/advisories/GHSA-jfgp-674x-6q… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1229549] New: django-auth-ldap: Enable sle15_python_module_pythons
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1229549 Bug ID: 1229549 Summary: django-auth-ldap: Enable sle15_python_module_pythons Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: egotthold(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My application (Orthos 2) cannot be installed on Leap since it requires django-auth-ldap, which is unavailable with Python 3.11. -- You are receiving this mail because: You are on the CC list for the bug.

1 9