July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1218342] New: [TRACKERBUG] OpenSSL 3.2.0 upgrade tracker bug for Tumbleweed
by bugzilla_noreply＠suse.com 05 Nov '24

05 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1218342 Bug ID: 1218342 Summary: [TRACKERBUG] OpenSSL 3.2.0 upgrade tracker bug for Tumbleweed 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: otto.hollmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This bug collects the challenges and packages that need to be adapted for OpenSSL 3.2.0 upgrade in Tumbleweed. OpenSSL 3.2 migration guide: https://www.openssl.org/docs/man3.2/man7/migration_guide.html -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1226541] New: Cockpit Packagekit does not appear in UI
by bugzilla_noreply＠suse.com 05 Nov '24

05 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1226541 Bug ID: 1226541 Summary: Cockpit Packagekit does not appear in UI Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cockpit Assignee: Cockpit-bugs(a)suse.de Reporter: cody.henderson(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After installing cockpit-packagekit the Software Updates tab did not appear. After doing a little digging it appears to be caused by an incorrect path listed in the manifest for the plugin. In /usr/share/cockpit/packagekit/manifest.json it has the following conditions: > "conditions": [ > {"path-exists": "/lib/systemd/system/packagekit.service"}, > {"path-not-exists": "/sysroot/ostree"} > ], The path /lib/systemd/system/packagekit.service does not exist with packagekit installed on the system. Instead it is located at /usr/lib/systemd/system/packagekit.service. If I change that line to the corrected path the Software Update tab then appears and seems to function just fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1226112] New: Supersede kmozillahelper by xdg-desktop-portal integration
by bugzilla_noreply＠suse.com 05 Nov '24

05 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1226112 Bug ID: 1226112 Summary: Supersede kmozillahelper by xdg-desktop-portal integration Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: fabian(a)ritter-vogt.de QA Contact: qa-bugs(a)suse.de CC: opensuse-kde-bugs(a)opensuse.org Target Milestone: --- Found By: --- Blocker: --- For some time now, Firefox (and Thunderbird I hope) can use xdg-desktop-portal APIs for DE integration. We should try to migrate away from kmozillahelper in favor of using the builtin xdg-desktop-portal integration. For that, we need to make sure that on Plasma it uses xdg-desktop-portal instead of GTK file dialogs out of the box. Currently this needs to be done manually by setting widget.use-xdg-desktop-portal.file-picker=1 widget.use-xdg-desktop-portal.mime-handler=1 I'm not sure about widget.use-xdg-desktop-portal.open-uri. Can we get FF and TB configured such that it uses xdg-desktop-portal by default if it detects a Plasma session? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1226017] New: fwupd fails TPM fw upgrade with 'Secure boot is enabled, but shim isn't installed to EFI/opensuse/shim.efi'
by bugzilla_noreply＠suse.com 05 Nov '24

05 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1226017 Bug ID: 1226017 Summary: fwupd fails TPM fw upgrade with 'Secure boot is enabled, but shim isn't installed to EFI/opensuse/shim.efi' Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: anselm.gora(a)gmail.com 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/125.0.0.0 Safari/537.36 Build Identifier: fwupd expects to find EFI/opensuse/shim.efi while on openSUSE Aeon the path is EFI/systemd/shim.efi https://github.com/fwupd/fwupd/blob/eb3d26079d7b0e6f0db70b066fcb7b31ac7bcec… fwupd seems to use os release ID but it's also a build option: https://github.com/fwupd/fwupd/blob/eb3d26079d7b0e6f0db70b066fcb7b31ac7bcec… Tumbleweed seems to patch it: https://build.opensuse.org/projects/openSUSE:Factory/packages/fwupd/files/f… Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1224199] New: [Build 20240512] Unlock Users setting will end up in changing Root user settings.
by bugzilla_noreply＠suse.com 05 Nov '24

05 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1224199 Bug ID: 1224199 Summary: [Build 20240512] Unlock Users setting will end up in changing Root user settings. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4182899/modules/logi n_test/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: xiaoguang.wang(a)suse.com Reporter: grace.wang(a)suse.com QA Contact: qa-bugs(a)suse.de CC: yfjiang(a)suse.com, zcjia(a)suse.com Target Milestone: --- Found By: openQA Blocker: --- Steps: 1. Install a fresh Tumbleweed and the System Role is "Desktop with GNOME" 2. Boot to desktop and login with a non-root user which was created during installation -> Launch gnome-control-center -> Navigate to System and then Users -> Click Unlock and input Administrator password to Authenticate 3. Observe the Users Actual Result: The Users panel shows "Root" instead of the non-root user we used for login. This issue can only be reproduced on a fresh installed system. That mean if you reproduced this issue for one time and you might now be able to reproduced this one more time in this particular environment. So, be sure to take a snapshot before trying to reproduce this issue one your side. ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-desktopapps-gnome@64bit fails in [login_test](https://openqa.opensuse.org/tests/4182899/modules/login_test/st… ## Test suite description ## Reproducible Fails since (at least) Build [20240320](https://openqa.opensuse.org/tests/4028599) ## Expected result Last good: [20240319](https://openqa.opensuse.org/tests/4026004) (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 1

[Bug 1219879] New: [TRACKERBUG] Remove EOL OpenSSL 1.1.1 and OpenSSL 1.0.0
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1219879 Bug ID: 1219879 Summary: [TRACKERBUG] Remove EOL OpenSSL 1.1.1 and OpenSSL 1.0.0 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: otto.hollmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This bug collects the challenges and packages that need to be adapted before removing OpenSSL 1.1.1 and OpenSSL 1.0.0 OpenSSL 1.1.1 (package openssl1_1) is EOL since 11th September 2023. OpenSSL 1.0.0 (package openssl1_0_0) is EOL since 31th December 2019. Therefore, it makes sense to get rid of them and we are going to remove them from Factory in the near future. Unfortunately some packages still rely/depend on these old OpenSSL versions. If we would like to keep these packages, they must be adapted to use OpenSSL 3. Currently these packages are usually hardcoded to use specific openssl package, e.g.: > BuildRequires: libopenssl-1_1-devel The preferred way is to use our meta package > BuildRequires: libopenssl or > BuildRequires: libopenssl-devel that will always pull respective packages with the default OpenSSL version (at the moment libopenssl3 or libopenssl-3-devel). Migration guide can be found here: https://www.openssl.org/docs/man3.0/man7/migration_guide.html List of packages that are using old OpenSSL: dd_rescue EternalTerminal fdo-client libredfish libzrtpcpp python -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1222211] New: "Forget file" in "Recent Files" of the "Application Menu" starter seems to do nothing (KDE Plasma 6, Tumbleweed 20240329)
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1222211 Bug ID: 1222211 Summary: "Forget file" in "Recent Files" of the "Application Menu" starter seems to do nothing (KDE Plasma 6, Tumbleweed 20240329) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ingo.strauch(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I've recently updated to version 20240329 of Tumbleweed which for me was the upgrade of KDE Plasma 5 to 6. Since then, forgetting files via the start menu does not work as expected anymore. Steps to reproduce * open the "Application Menu" starter * click "Recent Files" at the top to show the list of recent files * right-click on one of the files and select "Forget File" from the context menu Expected behavior * the file gets removed from the list immediately (just like it did with KDE Plasma 5) Actual behavior * the file is still shown in the list As it turns out the file does get forgotten because it is removed from the list in a fresh login session, so it seems to me it's just a UI refresh problem. I still find it quite annoying because my use case often is to open files from the "Recent Files" list where I first have to remove several (to me) irrelevant entries before the document I'm looking for is shown. I've also tested this with a fresh user account and the problem exists there as well. Forgetting files does work as expected in "Application Starter" but not with "Application Menu". -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213156] New: systemd-xdg-autostart-generator cannot start several existing desktop files in Leap 15.5
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213156 Bug ID: 1213156 Summary: systemd-xdg-autostart-generator cannot start several existing desktop files in Leap 15.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ftake(a)geeko.jp QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This report is created in order to summarize related report caused by the same issues of systemd-xdg-autostart-generator in 15.5. systemd-xdg-autostart-generator is a mechanism to start XDG autostart (e.g., /etc/xdg/autostart) instead of desktop environments. In Leap 15.5, KDE plasma started to use this mechanism. However, due to the following problems, xdg-autostart-generator cannot start desktop files derived from Leap 15.4. Some essential services including IBus does not work in 15.5 (#1211977). * systemd-xdg-autostart-generator inappropriately ignores desktop files with X-GNOME-Autostart-Phase (#1201728) [1] * systemd-xdg-autostart-generator cannot start process that forks another process [2, 3, 4] [1] https://github.com/systemd/systemd/issues/18791 (resolved) [2] https://bugs.kde.org/show_bug.cgi?id=433299 [3] https://github.com/systemd/systemd/pull/20813 (merged) [4] https://github.com/systemd/systemd/issues/27919 (unresolved) FYI: Upstream bug tracker related xdg-autostart https://github.com/systemd/systemd/labels/xdg-autostart Some other fixes also might be necessary for 15.5 -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1220260] New: qBittorrent freezes after opening and closing preferences
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1220260 Bug ID: 1220260 Summary: qBittorrent freezes after opening and closing preferences Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: piotrus3g(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20240221 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.5-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82SG System Version: IdeaPad 5 15ABA7 Steps to reproduce: 1. Open qbittorrent 2. Open qbittorrent preferences 3. Close preferences window Observed result: qbittorrent freezes. Expected result: qbittorrent doesn't freeze. Additional information: qbittorrent unfreezes after a short time and seems to work properly. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1218101] New: qBittorrent blurry fonts on kde wayland
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1218101 Bug ID: 1218101 Summary: qBittorrent blurry fonts on kde wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: piotrus3g(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871385 --> https://bugzilla.suse.com/attachment.cgi?id=871385&action=edit Compare the fonts in qBittorrent to the right click menu on the app's titlebar Operating System: openSUSE Tumbleweed 20231213 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.6-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5625U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82SG System Version: IdeaPad 5 15ABA7 Issue: qBittorrent fonts are a bit blurry under wayland on kde. Steps to reproduce: Launch qBittorrent and see that the fonts aren't as sharp as other programs. Observed behavior: Fonts are blurrier than other programs. Expected behavior: Fonts are sharp just like every other app. Additional information: I'm not sure if it's related, but right now scaling in kde wayland on tumbleweed is a bit broken, because user has to set scaling by force font dpi and not by display scaling. Scaling works when screen scaling is at 100% and force font dpi is set to apply actual scaling (120dpi in my case for effective 125% scaling). -- You are receiving this mail because: You are on the CC list for the bug.

1 2