January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 1217973] New: warewulf: non-deterministic cpio files
by bugzilla_noreply＠suse.com 27 Mar '24

27 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1217973 Bug ID: 1217973 Summary: warewulf: non-deterministic cpio files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: eich(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: cgoll(a)suse.com Blocks: 1134568 Target Milestone: --- Found By: --- Blocker: --- While working on reproducible builds for openSUSE, I found that our warewulf package varies in every build. 8 cpio files in /var/lib/warewulf/initramfs/x86_64/ vary every time: base capabilities/provision-adhoc capabilities/provision-files capabilities/provision-selinux capabilities/provision-vnfs capabilities/setup-filesystems capabilities/setup-ipmi capabilities/transport-http Here is a partial PoC patch that helped to produce bit-reproducible results: --- a/provision/initramfs/capabilities/transport-http/Makefile.am +++ b/provision/initramfs/capabilities/transport-http/Makefile.am @@ -16,7 +16,7 @@ rootfs: done capability.cpio: rootfs - cd rootfs/; find . | cpio -o -H newc -F ../capability.cpio + cd rootfs/; find . | xargs touch -d @1690848000 ; find . | sort | cpio -o -H newc --reproducible -F ../capability.cpio install-data-local: capability.cpio install -d -m 755 $(DESTDIR)/$(WAREWULF_STATEDIR)/warewulf/initramfs/$(MACHINE)/capabilities I'm not sure if the mtimes of files in the cpio files matter. The source tar is from 2018, so not sure if upstream would be interested in this. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217495] New: WiFi fails to re-connect on return from suspend, occasionally.
by bugzilla_noreply＠suse.com 27 Mar '24

27 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1217495 Bug ID: 1217495 Summary: WiFi fails to re-connect on return from suspend, occasionally. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870981 --> https://bugzilla.suse.com/attachment.cgi?id=870981&action=edit journal showing the event Some times, when thawing my laptop, it fails to connect to the WiFi. Looking at the log, this might look a router issue, but the thing is, it has happened to me on two routers, one in Ottawa, another in Madrid. And hibernating the machine makes the WiFi connect again (power cycles the chipset). Thus I believe the problem is in the laptop/linux side, not the router. Laptop is less that a year old, a Lenovo L14 Gen3 AMD. I will attach journal showing one such incident. Some lines removed for privacy. You have to look on the journal at the timestamps marked with an arrow below: 2023-11-25T15:30:44,422546660+01:00 - Booting the system now ================================================================================ Linux Laicolasse 5.14.21-150500.55.36-default #1 SMP PREEMPT_DYNAMIC Tue Oct 31 08:37:43 UTC 2023 (e7a2e23) x86_64 x86_64 x86_64 GNU/Linux 2023-11-25 16:02:59+01:00 - Suspending the system now... 2023-11-25 18:33:09+01:00 - Thawing from suspend the system now)... <-- worked 2023-11-25 18:37:19+01:00 - Suspending the system now... 2023-11-25 18:37:32+01:00 - Thawing from suspend the system now)... <========== failed 2023-11-25 18:38:09+01:00 - Hibernating the system now... 2023-11-25 18:43:14+01:00 - Thawing the system now... <========== worked Laicolasse:~ # inxi -n -N Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth0 state: down mac: f4:a8:0d:7a:49:01 Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: mt7921e IF: wlan0 state: up mac: 60:e9:aa:a0:1a:49 Laicolasse:~ # hwinfo 25: PCI 600.0: 0282 WLAN controller [Created at pci.386] Unique ID: y9sn.gA5E5AhV_LC Parent ID: AXjq.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.6/0000:06:00.0 SysFS BusID: 0000:06:00.0 Hardware Class: network Model: "MEDIATEK WLAN controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x0616 SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0xe0c6 Driver: "mt7921e" Driver Modules: "mt7921e" Device File: wlan0 Features: WLAN Memory Range: 0xe0200000-0xe02fffff (ro,non-prefetchable) Memory Range: 0xfd400000-0xfd407fff (rw,non-prefetchable) IRQ: 80 (157547 events) HW Address: 60:e9:aa:a0:1a:49 Permanent HW Address: 60:e9:aa:a0:1a:49 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v000014C3d00000616sv000017AAsd0000E0C6bc02sc80i00" Driver Info #0: Driver Status: mt7921e is active Driver Activation Cmd: "modprobe mt7921e" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #26 (PCI bridge) 54: None 00.0: 1070a WLAN [Created at net.126] Unique ID: AYEt.QXn1l67RSa1 Parent ID: y9sn.gA5E5AhV_LC SysFS ID: /class/net/wlan0 SysFS Device Link: /devices/pci0000:00/0000:00:02.6/0000:06:00.0 Hardware Class: network interface Model: "WLAN network interface" Driver: "mt7921e" Driver Modules: "mt7921e" Device File: wlan0 HW Address: 60:e9:aa:a0:1a:49 Permanent HW Address: 60:e9:aa:a0:1a:49 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (WLAN controller) Please ask for any other information needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219195] New: /sys/class/drm/card1/device/hwmon/hwmon*/power1_cap_min increased from 6.6. to 6.7 way too much
by bugzilla_noreply＠suse.com 24 Mar '24

24 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219195 Bug ID: 1219195 Summary: /sys/class/drm/card1/device/hwmon/hwmon*/power1_cap_mi n increased from 6.6. to 6.7 way too much Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: benedictbroy(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Dear maintainers, when upgrading the kernel in Tumbleweed from 6.611-1.1 to 6.7.1-1.1 the lowest TDP I could set for my AMD RX6600 increased from 0 (might be nonsensical) to 94W (which is close to the default of 100W). I'm referring to the TDP floor of /sys/class/drm/card1/device/hwmon/hwmon*/power1_cap_min where * denotes the device number. On 6.611-1.1, I could happily drive my RX 6600 with a 50W TDP (by means of setting echo '50000000' > '/sys/class/drm/card1/device/hwmon/hwmon3/power1_cap' at boot); once upgraded to 6.7.1-1.1 this no longer works. Have the TDP floors been purposefully increased for some reason? As my 50W TDP setting on 6.611-1.1 works like a charm, I'd be delighted if the previous behaviour could perhaps be restored. Thanks a lot in advance and let me know if I can provide further info. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217920] New: QT_IM_MODULE is always set on plasma 5.27.9
by bugzilla_noreply＠suse.com 23 Mar '24

23 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1217920 Bug ID: 1217920 Summary: QT_IM_MODULE is always set on plasma 5.27.9 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: i(a)xuzhao.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- According to the fcitx5 on wayland wiki page: https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland QT_IM_MODULE and GTK_IM_MODULE and SDL_IM_MODULE are not suggested to be set on fcitx5+plasma_wayland>5.27. However, after I install fcitx5 on opensuse 20231117, these environment variables are still being set by default. Is there a way that I can disable setting these environment variables on startup? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1218283] New: Building ZFS for 15.6 and Tumbleweed broken by kernel_neon_begin changed from EXPORT_SYMBOL_GPL EXPORT_SYMBOLto
by bugzilla_noreply＠suse.com 22 Mar '24

22 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218283 Bug ID: 1218283 Summary: Building ZFS for 15.6 and Tumbleweed broken by kernel_neon_begin changed from EXPORT_SYMBOL_GPL EXPORT_SYMBOLto 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: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Fail: https://build.opensuse.org/package/live_build_log/filesystems/zfs/openSUSE_… [ 259s] ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_end' [ 259s] ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'kernel_neon_begin' Upstream tracks the issue here https://github.com/openzfs/zfs/issues/15401 and here https://github.com/openzfs/zfs/issues/14555 It could be fixed by reverting this kernel patch: https://github.com/torvalds/linux/commit/aaeca98456431a8d9382ecf48ac4843e25… -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1218780] New: Raspberry Pi 400 defaults to llvmpipe renderer instead of Broadcom V3D 4.2
by bugzilla_noreply＠suse.com 22 Mar '24

22 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218780 Bug ID: 1218780 Summary: Raspberry Pi 400 defaults to llvmpipe renderer instead of Broadcom V3D 4.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: robert-suse2(a)riemann.cc QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I installed openSUSE-Tumbleweed-ARM-KDE-raspberrypi.aarch64-2023.11.30-Snapshot20240109.raw.xz on my Raspberry Pi 400 (4GB RAM). Unfortunately, no 3D acceleration works. The file /boot/efi/config.txt contains the following section that is also considered for PI 400 series: [pi4] dtoverlay=vc4-kms-v3d,cma-default dtoverlay=disable-vc4 `glxinfo -B` shows that llvmpipe is used as opengl renderer. After a lot of trial and error, I found out that if I comment out `dtoverlay=disable-vc4` in config.txt, then 3d acceleration is working and opengl renderer is "V3D 4.2". I suggest that opensuse tumbleweed does not add the disable-vc4 overlay for raspberry pi 400 (and possibly pi 4) users. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1219355] New: Missing Mesa 3D OpenCL Rusticl driver for Leap 15.6 with X11:XOrg repository
by bugzilla_noreply＠suse.com 19 Mar '24

19 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219355 Bug ID: 1219355 Summary: Missing Mesa 3D OpenCL Rusticl driver for Leap 15.6 with X11:XOrg repository Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: kaykaykay123(a)gmail.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: Community User Blocker: --- It looks like everything is ready to get Mesa 3D OpenCL Rusticl driver for Leap 15.6 with X11:XOrg repository. Rust-bindgen: https://software.opensuse.org/package/rust-bindgen Spirv-llvm-translator: https://software.opensuse.org/package/spirv-llvm-translator Related bugs: boo#1207578, boo#1207711. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1219113] New: VUL-0: CVE-2024-23222: webkit2gtk3,webkitgtk: type confusion may lead to arbitrary code execution
by bugzilla_noreply＠suse.com 18 Mar '24

18 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219113 Bug ID: 1219113 Summary: VUL-0: CVE-2024-23222: webkit2gtk3,webkitgtk: type confusion may lead to arbitrary code execution Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/391964/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: mlin(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: --- A type confusion issue was addressed with improved checks. This issue is fixed in tvOS 17.3, iOS 17.3 and iPadOS 17.3, macOS Sonoma 14.3, iOS 16.7.5 and iPadOS 16.7.5, Safari 17.3, macOS Ventura 13.6.4, macOS Monterey 12.7.3. Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been exploited. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-23222 https://support.apple.com/en-us/HT214058 https://support.apple.com/en-us/HT214057 https://support.apple.com/en-us/HT214063 https://support.apple.com/en-us/HT214059 https://support.apple.com/en-us/HT214061 https://www.cve.org/CVERecord?id=CVE-2024-23222 https://support.apple.com/en-us/HT214055 https://support.apple.com/en-us/HT214056 https://bugzilla.redhat.com/show_bug.cgi?id=2259893 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1219387] New: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 121.0.6167.139
by bugzilla_noreply＠suse.com 18 Mar '24

18 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219387 Bug ID: 1219387 Summary: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 121.0.6167.139 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: gmbr3(a)opensuse.org Reporter: gianluca.gabrielli(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The Stable channel has been updated to 121.0.6167.139 for Mac and Linux and 121.0.6167.139/140 to Windows which will roll out over the coming days/weeks. A full list of changes in this build is available in the log. Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. This update includes 4 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. [$5000][1511567] High CVE-2024-1060: Use after free in Canvas. Reported by Anonymous on 2023-12-14 [$3000][1514777] High CVE-2024-1059: Use after free in WebRTC. Reported by Cassidy Kim(@cassidy6564) on 2023-12-29 [N/A][1511085] High CVE-2024-1077: Use after free in Network. Reported by Microsoft Security Research Center on 2023-12-13 We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel. As usual, our ongoing internal security work was responsible for a wide range of fixes:[1523290] Various fixes from internal audits, fuzzing and other initiatives Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzze -- You are receiving this mail because: You are on the CC list for the bug.

1 4