July 2024 - openSUSE Bugs - openSUSE Mailing Lists

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

30 Sep '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 3

[Bug 1222914] New: Upgrade from kernel 5.14.21-150500.55.39-default to kernel 5.14.21-150500.55.44-default broke on my laptop
by bugzilla_noreply＠suse.com 28 Sep '24

28 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222914 Bug ID: 1222914 Summary: Upgrade from kernel 5.14.21-150500.55.39-default to kernel 5.14.21-150500.55.44-default broke on my laptop Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: marc(a)marcchamberlin.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When I tried to install the upgrade mentioned in the summary it breaks and hangs during the bootup process for the new system and badly hangs requiring me to power cycle my laptop. I have frozen and locked my laptop at vmlinuz-5.14.21-150500.55.39-default for now, but that means I can no longer install any kernel patches or upgrades. I am not sure of the cause of the hang up but have narrowed it down to probably ??? either an inability to properly query my network interfaces (it sometimes stalls out when trying to get an IP address from my DHCP server) for their identity and capabilities) or perhaps something is wrong with the nVidia drivers. I have a relatively new Dell laptop as described here - # inxi -CGMSnaz System: Kernel: 5.14.21-150500.55.39-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.39-default root=UUID=ce027c75-c647-4b4b-8c6a-e5fb48f41513 splash=silent preempt=full mitigations=auto quiet security=apparmor Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM Distro: openSUSE Leap 15.5 Machine: Type: Laptop System: Dell product: XPS 15 9530 v: N/A serial: <filter> Chassis: type: 10 serial: <filter> Mobo: Dell model: 0GY0F9 v: A00 serial: <filter> UEFI: Dell v: 1.7.0 date: 08/14/2023 CPU: Info: model: 13th Gen Intel Core i9-13900H socket: U3E1 bits: 64 type: MST AMCP arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+ process: Intel 7 (10nm) family: 6 model-id: 0xBA (186) stepping: 2 microcode: 0x411C Topology: cpus: 1x cores: 14 mt: 6 tpc: 2 st: 8 threads: 20 smt: enabled cache: L1: 1.2 MiB desc: d-8x32 KiB, 6x48 KiB; i-6x32 KiB, 8x64 KiB L2: 11.5 MiB desc: 6x1.2 MiB, 2x2 MiB L3: 24 MiB desc: 1x24 MiB Speed (MHz): avg: 540 high: 682 min/max: 400/5200:5400:4100 base/boost: 4851/5400 scaling: driver: intel_pstate governor: powersave volts: 1.3 V ext-clock: 100 MHz cores: 1: 440 2: 473 3: 404 4: 587 5: 544 6: 680 7: 468 8: 682 9: 564 10: 662 11: 443 12: 583 13: 624 14: 459 15: 532 16: 489 17: 488 18: 553 19: 580 20: 546 bogomips: 119807 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: mmio_stale_data status: Not affected Type: retbleed status: Not affected Type: spec_rstack_overflow status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Dell driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 0000:00:02.0 chip-ID: 8086:a7a0 class-ID: 0300 Device-2: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile] vendor: Dell driver: N/A alternate: nouveau, nvidia_drm, nvidia non-free: N/A status: unknown device ID bus-ID: 0000:01:00.0 chip-ID: 10de:28a0 class-ID: 0302 Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 3-6:3 chip-ID: 0c45:6a22 class-ID: fe01 serial: <filter> Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.5 compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: iris gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (19.96x11.22") s-diag: 582mm (22.9") Monitor-1: eDP-1 model: Samsung 0x414d built: 2020 res: 1920x1080 hz: 60 dpi: 145 gamma: 1.2 size: 336x210mm (13.23x8.27") diag: 396mm (15.6") ratio: 16:10 modes: 3456x2160 API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel Graphics (RPL-P) direct render: Yes Network: Device-1: Intel Raptor Lake PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 0000:00:14.3 chip-ID: 8086:51f1 class-ID: 0280 IF: wlan0 state: up mac: <filter> Device-2: ASIX AX88179 Gigabit Ethernet type: USB driver: ax88179_178a bus-ID: 2-1.3.2:4 chip-ID: 0b95:1790 class-ID: ff00 serial: <filter> IF: eth0 state: down mac: <filter> Please refer to the thread on users(a)lists.opensuse.org titled "Yikes! Looks like an update has screwed up my laptop" to see a discussion I had with the user community about this issue, for some additional information. They advised me to submit this bug report. I will be happy to provide any additional information requested, and I will see if I can capture a boot log file and add it in a followup comment. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1228366] New: Missing package for Application:Geo/qgis: causes fatal error std::bad_alloc on loading plugin
by bugzilla_noreply＠suse.com 28 Sep '24

28 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1228366 Bug ID: 1228366 Summary: Missing package for Application:Geo/qgis: causes fatal error std::bad_alloc on loading plugin Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: grant.eureka(a)xtra.co.nz QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- qgis 3.34.1 crashes when loading the Plugin "LINZ Data Importer" with fatal error std::bad_alloc I have traced the error to the package python311-OWSLib which attempts to load the Python package pyproj which needs to be installed correctly from python311-pyproj. The package python311-pyproj is missing from Leap 15.6 repos. I have successfully installed python311-pyproj 3.6.1 from a Tumbleweed community project. This has corrected the bad_alloc fatal error. Package python311-pyproj is needed in Leap 15.6 for qgis and should be listed as a "required by" in package python311-OWSLib. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227378] New: /usr/bin/idle* don't have executable bits
by bugzilla_noreply＠suse.com 27 Sep '24

27 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1227378 Bug ID: 1227378 Summary: /usr/bin/idle* don't have executable bits Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- tumbleweed-pkg~$ l /usr/bin/*idle* -rw-r--r--. 1 root root 94 čen 25 23:57 /usr/bin/idle3.11 -rw-r--r--. 1 root root 94 čen 30 21:20 /usr/bin/idle3.13 tumbleweed-pkg~$ -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1221715] New: GCC 14: liblogging package fails
by bugzilla_noreply＠suse.com 27 Sep '24

27 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1221715 Bug ID: 1221715 Summary: GCC 14: liblogging package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: thomas.blume(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building liblogging with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: beepframe.c:170:1: error: return type defaults to ‘int’ [-Wimplicit-int] 170 | sbFramActualRecvFramCommonBody(sbFramObj* pThis,sbChanObj *pChan) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ beeplisten.c: In function ‘sbLstnInit’: beeplisten.c:1055:28: error: implicit declaration of function ‘sbSock_InitUXDOMSOCK’ [-Wimplicit-function-declaration] 1055 | if((iRet = sbSock_InitUXDOMSOCK(&(pThis->pSockUXDOMSOCKListening), pActualSockName, /*SOCK_DGRAM*/ SOCK_STREAM)) != SR_RET_OK) | ^~~~~~~~~~~~~~~~~~~~ Builds with: Index: liblogging-1.0.6/rfc3195/src/beepframe.c =================================================================== --- liblogging-1.0.6.orig/rfc3195/src/beepframe.c +++ liblogging-1.0.6/rfc3195/src/beepframe.c @@ -167,6 +167,7 @@ srRetVal sbFramActualRecvFramCommonHdr(s * The channel object is updated, e.g. with a * new seqno. */ +int sbFramActualRecvFramCommonBody(sbFramObj* pThis,sbChanObj *pChan) { unsigned iToRcv; Index: liblogging-1.0.6/rfc3195/src/sockets.h =================================================================== --- liblogging-1.0.6.orig/rfc3195/src/sockets.h +++ liblogging-1.0.6/rfc3195/src/sockets.h @@ -340,4 +340,8 @@ srRetVal sbSockRecvFrom(sbSockObj *pThis # define SOCKET_ERROR -1 #endif +#if FEATURE_UNIX_DOMAIN_SOCKETS == 1 +srRetVal sbSock_InitUXDOMSOCK(sbSockObj **ppThis, char *pszSockName, int iSockType); +#endif + #endif See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1226763] New: Missing non-oss source repo for aarch64
by bugzilla_noreply＠suse.com 27 Sep '24

27 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1226763 Bug ID: 1226763 Summary: Missing non-oss source repo for aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- We have a source repo for non-oss ports on s390x and ppc but not on arm we can either add it for Arm, or drop it for others guillaume_g As it exists for x86_64, I guess we should publish it for :ARM as well https://download.opensuse.org/source/tumbleweed/repo/non-oss/ (using patterns component so it ends on rel-eng) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1225147] New: Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 Sep '24

26 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 Bug ID: 1225147 Summary: Kernel hard lockup under mild GPU load Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: llyyr.public(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0 Build Identifier: Randomly get hard lockups with no errors or dmesg logs, can't ssh into the system either. Reproducible: Always Steps to Reproduce: 1. Record the screen with vaapi encoding on amdgpu Actual Results: Kernel hard lockup some time after 5-30 minutes Expected Results: System should be stable With i5-13600k and RX 6600 XT. I'm running sway and the screen recording tool doesn't matter as long as it's using vaapi encoding. The Mesa version also doesn't matter. This happens on Kernel versions 6.7 or newer, I just tried 6.9.1 and can reproduce it there as well. It does not happen on 6.6.x. I'm currently running 6.6.31-lts. I'd go ahead and bisect the kernel but I'm not sure how to build and install the kernel in a way that it appears in the grub menu. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1227231] New: virt-manager agama based deployment with default layout will not fit on 20GB VM
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1227231 Bug ID: 1227231 Summary: virt-manager agama based deployment with default layout will not fit on 20GB VM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'd like to propose new default size for VMs to be 25GB. When it comes to Agama 8/9 of today you have to drop swap (in my case 3GB) to fit on the default 20GB VM image in virt-manager. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1218694] New: [k8s,kube-flannel] YAML File to set up Flannel Network Add-On is outdated
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1218694 Bug ID: 1218694 Summary: [k8s,kube-flannel] YAML File to set up Flannel Network Add-On is outdated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- After successfully setting up k8s (using `kubeadm init`), the coredns pod remains in a 'Pending' state: NAMESPACE NAME READY STATUS RESTARTS AG kube-system coredns-86ccd44ff8-24h9w 0/1 Pending 0 12 kube-system coredns-86ccd44ff8-rz5vq 0/1 Pending 0 12 kube-system etcd-k8s-head 1/1 Running 1 12 kube-system kube-apiserver-k8s-head 1/1 Running 1 12 kube-system kube-controller-manager-k8s-head 1/1 Running 1 12 kube-system kube-proxy-qprnj 1/1 Running 0 12 kube-system kube-scheduler-k8s-head 1/1 Running 1 13 This is due to a not yet installed network plugin. When installing `kubeadm` thru 'patterns-kubernetes-kubeadm', the package 'flannel-k8s-yaml' is installed alongside which contains a yaml file to set up Flannel as network plugin. Running `kubectl apply -f /usr/share/k8s-yaml/flannel/kube-flannel.yaml` using the supplied file fails, however after: | clusterrole.rbac.authorization.k8s.io/flannel created | clusterrolebinding.rbac.authorization.k8s.io/flannel created | serviceaccount/flannel created | configmap/kube-flannel-cfg created | daemonset.apps/kube-flannel-ds created with the error: | error: resource mapping not found for name: "psp.flannel.unprivileged" namespace: "" from "/usr/share/k8s-yaml/flannel/kube-flannel.yaml": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first When using the yaml file from https://github.com/flannel-io/flannel/blob/master/Documentation/kube-flanne… (wget https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/k…) it works, however, the flannel pod is still cycling thru a CrashLoopBackOff - it fails with (from log): | E0110 11:46:48.988799 1 main.go:332] Error registering network: failed to acquire lease: node "k8s-head" pod cidr not assigned -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1227376] New: VUL-0: CVE-2024-6284: tailscale: google/nftables: incorrect IP address encoded bytes may lead to unwanted behavior
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1227376 Bug ID: 1227376 Summary: VUL-0: CVE-2024-6284: tailscale: google/nftables: incorrect IP address encoded bytes may lead to unwanted behavior Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/412835/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: alexandre.vicenzi(a)suse.com Reporter: thomas.leroy(a)suse.com QA Contact: security-team(a)suse.de CC: security-team(a)suse.de, smash_bz(a)suse.de, thomas.leroy(a)suse.com Blocks: 1227375 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1227375 +++ In https://github.com/google/nftables IP addresses were encoded in the wrong byte order, resulting in an nftables configuration which does not work as intended (might block or not block the desired addresses). This issue affects: https://pkg.go.dev/github.com/google/nftables@v0.1.0 The bug was fixed in the next released version: https://pkg.go.dev/github.com/google/nftables@v0.2.0 References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-6284 https://www.cve.org/CVERecord?id=CVE-2024-6284 https://bugs.launchpad.net/ubuntu/+source/crowdsec-firewall-bouncer/+bug/20… https://github.com/crowdsecurity/cs-firewall-bouncer/issues/368 https://github.com/google/nftables/issues/225 https://bugzilla.redhat.com/show_bug.cgi?id=2295699 -- You are receiving this mail because: You are on the CC list for the bug.

1 4