January 2024 - openSUSE Bugs - openSUSE Mailing Lists

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

18 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219118 Bug ID: 1219118 Summary: VUL-0: chromium,ungoogled-chromium: multiple vulnerabilities fixed in 121.0.6167.85 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: gmbr3(a)opensuse.org Reporter: thomas.leroy(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The Stable channel has been updated to 121.0.6167.85 for Mac and Linux and 121.0.6167.85/.86 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 17 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. High CVE-2024-0807: Use after free in WebAudio. Reported by Huang Xilin of Ant Group Light-Year Security Lab on 2023-11-25 High CVE-2024-0812: Inappropriate implementation in Accessibility. Reported by Anonymous on 2023-09-19 High CVE-2024-0808: Integer underflow in WebUI. Reported by Lyra Rebane (rebane2001) on 2023-11-24 Medium CVE-2024-0810: Insufficient policy enforcement in DevTools. Reported by Shaheen Fazim on 2023-10-26 Medium CVE-2024-0814: Incorrect security UI in Payments. Reported by Muneaki Nishimura (nishimunea) on 2023-07-11 Medium CVE-2024-0813: Use after free in Reading Mode. Reported by @retsew0x01 on 2023-08-30 Medium CVE-2024-0806: Use after free in Passwords. Reported by 18楼梦想改造家 on 2023-11-25 Medium CVE-2024-0805: Inappropriate implementation in Downloads. Reported by Om Apip on 2024-01-01 Medium CVE-2024-0804: Insufficient policy enforcement in iOS Security UI. Reported by Narendra Bhati of Suma Soft Pvt. Ltd. Pune (India) on 2024-01-03 Low CVE-2024-0811: Inappropriate implementation in Extensions API. Reported by Jann Horn of Google Project Zero on 2023-10-21 [TBD][1497985] Low CVE-2024-0809: Inappropriate implementation in Autofill. Reported by Ahmed ElMasry on 2023-10-31 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1215962] New: sddm fails when starting as a wayland client
by bugzilla_noreply＠suse.com 17 Mar '24

17 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1215962 Bug ID: 1215962 Summary: sddm fails when starting as a wayland client 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: sfalken(a)cloverleaf-linux.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869927 --> https://bugzilla.suse.com/attachment.cgi?id=869927&action=edit Output of Journal, for failure condition Setting an override in /etc/sddm.conf.d/10-wayland.conf for: [General] DisplayManager=wayland I would expect to get sddm running as a wayland client, but it crashes with an SDDM::Auth::Helper_AUTH_ERROR Please see attached log from the journal. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[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 1218899] New: Wrong license of cairo package
by bugzilla_noreply＠suse.com 16 Mar '24

16 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218899 Bug ID: 1218899 Summary: Wrong license of cairo package Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: stefan6419846(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The *cairo* package (https://build.opensuse.org/package/show/openSUSE:Leap:15.6/cairo, https://download.opensuse.org/source/distribution/leap/15.6/repo/oss/src/ca…) states that the license is `LGPL-2.1-or-later OR MPL-1.1`. Looking at the upstream repository and skimming through the (relevant) shipped source code, this does not seem to be correct and should rather be `LGPL-2.1-only OR MPL-1.1`: https://gitlab.freedesktop.org/cairo/cairo/-/blob/master/COPYING -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1218423] New: Patched source not in source RPM
by bugzilla_noreply＠suse.com 16 Mar '24

16 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218423 Bug ID: 1218423 Summary: Patched source not in source RPM Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Following up on https://lists.opensuse.org/archives/list/packaging@lists.opensuse.org/threa… a patch for the source file is not included in the source RPM. This leads (currently) to build errors in all orthanc-plugins in Factory. Example for the issue is here: https://build.opensuse.org/package/show/home:DocB:Orthanc/orthanc_1_12_1 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1218427] New: plasma-discover - Unable to search for applications in the OpenSUSE repos after update 25122023
by bugzilla_noreply＠suse.com 15 Mar '24

15 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218427 Bug ID: 1218427 Summary: plasma-discover - Unable to search for applications in the OpenSUSE repos after update 25122023 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: silviucc(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871583 --> https://bugzilla.suse.com/attachment.cgi?id=871583&action=edit part of the log showing which packages were installed and which were removed Hello, After updating to snapshot 25122023 Discover does not work properly anymore. On the Home screen it show: "Unable to load applications. Please verify internet connectivity" It is only able to search through flathub and shows only flatpak apps. zypper still works normally. I saw a bunch of packagekit updates in the logs, maybe one of them borked it? Attaching a trimmed zypper log This is what it shows when started from the terminal: --- silviu@localhost:~> plasma-discover fetch ratings! false adding empty sources model QStandardItemModel(0x5585bc8e01e0) no component found for "org.opensuse.opensuse-tumbleweed" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib64/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight" qrc:/qml/Feedback.qml:44: ReferenceError: UserFeedbackSettings is not defined PackageKit stopped running! --- -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1217047] New: Tracker: Packages incompatible with appstream 1.0
by bugzilla_noreply＠suse.com 15 Mar '24

15 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1217047 Bug ID: 1217047 Summary: Tracker: Packages incompatible with appstream 1.0 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: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Appstream 1.0 comes with BIC changes and format changes for metainfo files. Besides, appstream now uses Qt6 or Qt5 but shares the same library and CMake config name. Among the factory packages requiring appstream at build time, 8 failures were found. Build failures: - discover (needs appstreamqt built with Qt5 for its stable build) - flatpak - gnome-software - libadwaita - pidgin-sipe metainfo validation failures: - deja-dup - gnome-sudoku - gthumb -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1216681] New: AltGr key gets stuck in virtual console after switching to Swedish keyboard layout's "mac" variant using `localectl`
by bugzilla_noreply＠suse.com 15 Mar '24

15 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1216681 Bug ID: 1216681 Summary: AltGr key gets stuck in virtual console after switching to Swedish keyboard layout's "mac" variant using `localectl` 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: no(a)no.noooo.ooo QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 Build Identifier: Using a standard European keyboard (I use Swedish) with an AltGr key, after using `localectl` to switch to Swedish keyboard's MAC variant, virtual console would make AltGr stuck after typing `AltGr+Shift+<anything>`. Reproducible: Always Steps to Reproduce: 0. Get a European keyboard (I use Swedish) with an 'AltGr' key. 1. Log into any X11 GUI terminals and do sudo localectl set-x11-keymap se pc104 mac ctrl:nocaps In fact any keyboard models (pc104 etc.) I've tried will reproduce the bug. 2. Press Ctrl+Alt+F1 to go from X11 to virtual console. 3. Try typing the '{' character by pressing AltGr+Right_Shift+8. Actual Results: Now just press the '2' on your keyboard; but instead of '2', the character '@' is inserted because it seems to think that AltGr is still active, and in this Swedish layout '@' is AltGr+2. Similarly typing 'hckiang' produces 'ħ¢ĸ→æ”ŋ' as if the AltGr key is down. Now there're no easy ways to even shutdown the computer because you can't type any normal command/shortcuts any more. Not even Ctrl+Alt+F2 to switch back to X11. The only choice is to hit my laptop's power button to restart. Expected Results: After pressing AltGr+Right_Shift+8 to input a '{', you can still type normally, such that keyboard sequence 'hckiang' should input 'hckiang' rather than 'ħ¢ĸ→æ”ŋ'. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1218290] New: The world is not ready for FreeRDP 3
by bugzilla_noreply＠suse.com 15 Mar '24

15 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218290 Bug ID: 1218290 Summary: The world is not ready for FreeRDP 3 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: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- freerdp was attempted to be upgraded to version 3. This causes quite a lot of build issues: gamescope nothing provides pkgconfig(freerdp2) gnome-connections nothing provides pkgconfig(freerdp2) >= 2.0.0 gnome-remote-desktop nothing provides pkgconfig(freerdp-client2) >= 2.10.0 nothing provides pkgconfig(freerdp-server2) >= 2.10.0 nothing provides pkgconfig(freerdp2) >= 2.10.0 pidgin-sipe nothing provides pkgconfig(freerdp-shadow2) remmina nothing provides pkgconfig(freerdp2) >= 2.1.0 weston nothing provides pkgconfig(freerdp2) wlroots nothing provides pkgconfig(freerdp2) wlroots-0_16 nothing provides pkgconfig(freerdp2) wlroots10 nothing provides pkgconfig(freerdp2) This is a bit too much breakage in the old yea -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1218815] New: Unwanted "^@" output on tty interfere login
by bugzilla_noreply＠suse.com 15 Mar '24

15 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1218815 Bug ID: 1218815 Summary: Unwanted "^@" output on tty interfere login Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- For some reason I have on recent Tumbleweed (20231221) problems to log to tty due something printing ^@ during login. It prints every few seconds (visible in login), thus after some time typing enough helped to login (output stops), but it's something which is really problematic and should be fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 9