September 2023 - 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 1214274] New: Google Chrome and Chromium: Skia shader compilation error
by bugzilla_noreply＠suse.com 17 Mar '24

17 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1214274 Bug ID: 1214274 Summary: Google Chrome and Chromium: Skia shader compilation error 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: miso(a)hlavki.eu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868797 --> https://bugzilla.suse.com/attachment.cgi?id=868797&action=edit error log After upgrade to snapshots 20230812, 20230813 Google Chrome and Chromium stops render properly web pages. Started to blink and console log shows errors. Attachned error.txt It looks similar to: https://bugs.chromium.org/p/chromium/issues/detail?id=1442633 Can confirm that workaround is: google-chrome --disable-gpu-driver-bug-workarounds -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1214800] New: KDE Wayland Screen Energy Saving Problem
by bugzilla_noreply＠suse.com 14 Mar '24

14 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1214800 Bug ID: 1214800 Summary: KDE Wayland Screen Energy Saving Problem Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: pfaca(a)tutamail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When using Wayland, Screen Energy Saving doesn't work. Either waiting for the switch off timer, or using Ctrl + Alt + D the outcome is the same: 1. display turns off 2. display says that there is no signal/input 3. display turns off again 4. display wakes up immediately Journal gives the following: plasmashell[2276] qt.qpa.wayland: Wayland does not support QWindow::requestActivate() At bugs.kde.org there is the bug number 462695 (https://bugs.kde.org/show_bug.cgi?id=462695) where it claims the bug was resolved at KDE side and the fix has to be provided by openSUSE. My specs: openSUSE Tumbleweed Kernel 6.4.11-1-default DE Plasma 5.27.7 CPU Intel i5-4670K GPU AMD ATI Radeon RX 6750 XT Note: Everything works has expected using X11. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1214786] New: [Build 20230823] libreoffice: pressing alt-t does not keep the menu 'open'
by bugzilla_noreply＠suse.com 14 Mar '24

14 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1214786 Bug ID: 1214786 Summary: [Build 20230823] libreoffice: pressing alt-t does not keep the menu 'open' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3528042/modules/libr eoffice_default_theme/steps/4 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation This trips up openQA - and I could reproduce it locally: * Start LibreOffice (the main program) * press alt-t (open Tools menu) In many cases (especially when alt is not pressed longer) you can see the tools menu open and close down right again. if you press alt for at least as long until the sub-menu tools/Macros is rendered, the menu stays open. This seems quite annoying for keyboard users (clicking Tools with the mouse seems to keep it open always) openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-desktopapps-documentation-x11@64bit fails in [libreoffice_default_theme](https://openqa.opensuse.org/tests/3528042/module… ## Test suite description ## Reproducible Fails since (at least) Build [20230531](https://openqa.opensuse.org/tests/3327574) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1214111] New: VUL-0: CVE-2023-3894: jackson-dataformats-text: DoS during toml deserialization
by bugzilla_noreply＠suse.com 10 Mar '24

10 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1214111 Bug ID: 1214111 Summary: VUL-0: CVE-2023-3894: jackson-dataformats-text: DoS during toml deserialization Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/374699/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: fstrba(a)suse.com Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CVE-2023-3894 Those using jackson-dataformats-text to parse TOML data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-3894 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50083 https://www.cve.org/CVERecord?id=CVE-2023-3894 https://github.com/FasterXML/jackson-dataformats-text/blob/2.16/release-not… https://github.com/FasterXML/jackson-dataformats-text/pull/398 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215628] New: unbound fails to start under openSUSE MicroOS
by bugzilla_noreply＠suse.com 08 Mar '24

08 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1215628 Bug ID: 1215628 Summary: unbound fails to start under openSUSE MicroOS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: proprietaer1(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- steps to reproduce: 1. install unbound `transactional-update pkg in unbound` 2. reboot your system 3. try to start unbound.service 4. unbound fails to start systemctl status unbound.service systemd[1]: Starting Unbound recursive Domain Name Server... (sudo)[1552]: unbound.service: Failed to locate executable /usr/bin/sudo: Permission denied systemd[1]: unbound.service: Control process exited, code=exited, status=203/EXEC systemd[1]: unbound.service: Failed with result 'exit-code'. systemd[1]: Failed to start Unbound recursive Domain Name Server. It's maybe related to SELinux /var/log/audit/audit.log: type=AVC msg=audit(1695461159.115:842): avc: denied { execute } for pid=1552 comm="(sudo)" name="sudo" dev="sda2" ino=14092 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:sudo_exec_t:s0 tclass=file permissive=0 Unfortunately I have no idea about SELinux, any help would be appreciated. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215282] New: consoletest_setup fails on gnome scenario
by bugzilla_noreply＠suse.com 08 Mar '24

08 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1215282 Bug ID: 1215282 Summary: consoletest_setup fails on gnome scenario Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/3568610/modules/cons oletest_setup/steps/52 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: dmueller(a)suse.com, fvogt(a)suse.com Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-aarch64-system_performance@aarch64 fails in [consoletest_setup](https://openqa.opensuse.org/tests/3568610/modules/consol… consoletest_setup fails on gnome scenario since aarch64 Tumbleweed snapshot 20230911. The problem is we have broken fonts: https://openqa.opensuse.org/tests/3568601#step/consoletest_setup/54 So, '/usr/lib/systemd/systemd-vconsole-setup' is called (and returns 0), but prints some errors: https://openqa.opensuse.org/tests/3568601#step/consoletest_setup/55 ********** Sep 12 02:25:59.709634 localhost systemd-vconsole-setup[376]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument Sep 12 02:25:59.709640 localhost systemd-vconsole-setup[376]: Fonts will not be copied to remaining consoles ********** And does not display new fonts as expected by openQA: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/lib/… ## Test suite description Maintainer: QE Core An explicit system performance test. https://progress.opensuse.org/issues/36100 ## Reproducible Fails since (at least) Build [20230911](https://openqa.opensuse.org/tests/3568153) ## Expected result Last good: [20230910](https://openqa.opensuse.org/tests/3565572) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1213043] New: windows:mingw:win{32|64}/mingw{32|64}-cross-cmake: no version support for generated mingw32(cmake:xxx) provides
by bugzilla_noreply＠suse.com 07 Mar '24

07 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1213043 Bug ID: 1213043 Summary: windows:mingw:win{32|64}/mingw{32|64}-cross-cmake: no version support for generated mingw32(cmake:xxx) provides Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- Qt6 packages often uses dependencies to cmake package including a version as shown below: %package devel Summary: Qt 6 base development meta package Requires: qt6-base-common-devel Requires: cmake(Qt6Concurrent) = %{real_version} Requires: cmake(Qt6Core) = %{real_version} Requires: cmake(Qt6DBus) = %{real_version} Requires: cmake(Qt6Gui) = %{real_version} Requires: cmake(Qt6Network) = %{real_version} Requires: cmake(Qt6OpenGL) = %{real_version} Requires: cmake(Qt6OpenGLWidgets) = %{real_version} Requires: cmake(Qt6PrintSupport) = %{real_version} Requires: cmake(Qt6Sql) = %{real_version} Requires: cmake(Qt6Test) = %{real_version} Requires: cmake(Qt6Widgets) = %{real_version} Requires: cmake(Qt6Xml) = %{real_version} BuildArch: noarch https://build.opensuse.org/package/view_file/KDE:Qt6/qt6-base/qt6-base.spec… Cmake-related provides generated by the named package do not currently support versions. This means that when porting Qt6 packages to MinGW, the versions would have to be removed manually or via script. It would therefore be helpful if a version were available for these generated "Provides". -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213028] New: windows:mingw:win{32|64}/mingw{32|64}-libmng: no pkgconfig support
by bugzilla_noreply＠suse.com 07 Mar '24

07 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1213028 Bug ID: 1213028 Summary: windows:mingw:win{32|64}/mingw{32|64}-libmng: no pkgconfig support Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- On building mingw32-qt6-imageformat for MinGW it turned out that the mentioned package does not have pkgconfig support ~/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats> osc build openSUSE_Leap_15.5 -j12 Building mingw32-qt6-imageformats.spec for openSUSE_Leap_15.5/x86_64 Getting buildconfig from server and store to /home/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats/.osc/_buildconfig-openSUSE_Leap_15.5-x86_64 Getting buildinfo from server and store to /home/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats/.osc/_buildinfo-openSUSE_Leap_15.5-x86_64.xml buildinfo is broken... it says: unresolvable: nothing provides mingw32(pkg:libmng) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215574] New: sshfs-3.7.4 hangs processes with Status "D"
by bugzilla_noreply＠suse.com 07 Mar '24

07 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1215574 Bug ID: 1215574 Summary: sshfs-3.7.4 hangs processes with Status "D" Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: screening-team-bugs(a)suse.de Reporter: E.Kuemmerle(a)fz-juelich.de QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I use sshfs to mount my home directory. This works fine since many years, including the version 3.7.3 of sshfs. After installing version 3.7.4 from https://download.opensuse.org/repositories/filesystems/15.5, simple file accesses still work, but when I try to login graphically, the login hangs because many processes hang with status "D": #ps -efl F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD ... 0 D myuser 9334 9218 0 80 0 - 62739 filena 13:53 ? 00:00:00 /usr/lib/xdg-permission-store 0 D myuser 9377 9218 0 80 0 - 158487 d_allo 13:53 ? 00:00:00 /usr/bin/ksmserver 0 D myuser 9379 9218 0 80 0 - 314812 d_allo 13:53 ? 00:00:00 /usr/bin/kded5 0 D myuser 9407 9218 0 80 0 - 186461 d_allo 13:53 ? 00:00:00 /usr/bin/plasmashell --no-respawn 0 D myuser 9506 9218 0 80 0 - 199330 d_allo 13:53 ? 00:00:00 /usr/lib/evolution-data-server/evolution-data-server/evolution-alarm-notify 0 D myuser 9515 9511 0 80 0 - 37989 d_allo 13:53 ? 00:00:00 oyranos-monitor -s --daemon 0 D myuser 9529 9218 0 80 0 - 156587 d_allo 13:53 ? 00:00:00 /usr/bin/kaccess 0 D myuser 9566 9377 0 80 0 - 161680 d_allo 13:53 ? 00:00:00 /usr/bin/kwin_x11 -session 1094a77331000144844708300000033840001_1448447132_823255 0 D myuser 9732 9218 0 80 0 - 11101 walk_c 13:58 ? 00:00:00 systemd-tmpfiles --user --clean The sshfs process does not die but file access to the sshfs filesystem is then no longer possible. I suppose the high access load causes the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 7