July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1227420] New: openSUSE missing fi keymap
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227420 Bug ID: 1227420 Summary: openSUSE missing fi keymap Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: jarkko.torvinen(a)iki.fi QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On Tumbleweed installer, when selecting keyboard "Finnish", it results in "fi-kotoistus" in /etc/vconsole.conf. Gnome is not aware of such layout, resulting in non-working keymap in Gnome desktop, gnome-settings listing input source as "fi+kotoistus", and you need to change it to "Finnish" or "Finnish (classic)" to have working keyboard. On Aeon, keyboard selection is done with gnome initial setup. It has options "Finnish" and "Finnish (classic)" (as above with TW gnome-settins). 1) "Finnish" results in "fi" in /etc/vconsole.conf, but fi.map.gz does not exist in openSUSE, resulting in failing unit systemd-vconsole-setup 2) "Finnish (classic)" results in "fi-classic" in /etc/vconsole.conf, and everything works fine So both TW and Aeon are broken if you simply select obvious choices "Finnish". TW in GNOME, Aeon in form of failing unit during boot. On TW, selecting "Finnish" does not alter /etc/vconsole.conf anymore, so it does not break it, only initial setup with Aeon. Other distros (Debian,Arch for example) ship with "fi" map, and works as should. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1220626] New: bash-completion: error: "bash: have: command not found"
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1220626 Bug ID: 1220626 Summary: bash-completion: error: "bash: have: command not found" 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 CC: werner(a)suse.com Target Milestone: --- Found By: --- Blocker: --- This was problem in the past (#1060111) and now, after update to 2.12.0-1.1 (https://build.opensuse.org/request/show/1149849) it strikes again: bash: have: command not found bash: have: command not found bash: have: command not found $ rpm -qa |grep bash-completion perf-bash-completion-6.7.6-83.14.x86_64 SwayNotificationCenter-bash-completion-0.10.0-1.1.noarch bash-completion-2.12.0-1.1.noarch playerctl-bash-completion-2.4.1-1.11.noarch cpupower-bash-completion-6.7.6-6.9.noarch ethtool-bash-completion-6.7-1.1.noarch lightdm-bash-completion-1.32.0-2.5.noarch tig-bash-completion-2.5.8-1.6.noarch python-tqdm-bash-completion-4.66.1-3.4.noarch firewalld-bash-completion-2.1.1-1.2.noarch udisks2-bash-completion-2.10.0-2.2.noarch augeas-bash-completion-1.14.1-1.2.x86_64 virt-v2v-bash-completion-2.4.0-3.1.noarch docker-bash-completion-25.0.3_ce-2.1.noarch alacritty-bash-completion-0.13.1-1.2.noarch whois-bash-completion-5.5.20-1.2.noarch subversion-bash-completion-1.14.3-1.4.noarch kmod-bash-completion-31-2.2.noarch android-tools-bash-completion-34.0.4-2.3.noarch iproute2-bash-completion-6.7-1.2.x86_64 wl-clipboard-bash-completion-2.2.0-1.2.noarch btrfsprogs-bash-completion-6.7.1-1.1.x86_64 mbimcli-bash-completion-1.28.4-2.2.noarch pulseaudio-bash-completion-17.0-2.1.x86_64 yt-dlp-bash-completion-2023.12.30-1.4.noarch nvme-cli-bash-completion-2.8-1.1.noarch fwupd-bash-completion-1.9.13-1.1.noarch ModemManager-bash-completion-1.20.6-2.2.noarch mpv-bash-completion-0.37.0+git20231121.2a57a6ee-1.3.noarch $ rpm -q bash bash-5.2.26-10.3.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1224403] New: bpftrace: ERROR: Error attaching probe: 'kprobe:swap_readpage'
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1224403 Bug ID: 1224403 Summary: bpftrace: ERROR: Error attaching probe: 'kprobe:swap_readpage' 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- bpftrace fails to attach probe: # echo -e "\ninterval:s:5 { exit(); }" | cat /usr/share/bpftrace/tools/swapin.bt - | bpftrace - stdin:1-16: WARNING: swap_readpage is not traceable (either non-existing, inlined, or marked as "notrace"); attaching to it will likely fail Attaching 3 probes... cannot attach kprobe, probe entry may not exist ERROR: Error attaching probe: 'kprobe:swap_readpage' # echo $? 255 It has been failing for some time (at least since 20240412, but probably much longer). -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1227180] New: Potential regression io-io_uring-nops reports 3-8% decrease in mainline
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1227180 Bug ID: 1227180 Summary: Potential regression io-io_uring-nops reports 3-8% decrease in mainline 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: gabriel.bertazi(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- grid Infrastructure reports a 3-8% regression on io_uring nops test, found on Simba2 test potentially introduced by: Report Message-ID (Internal: <667e4b04./dspYBfaSWvQlPH0%root(a)laplace.suse.de>) Last Good/First Bad commit ========================== Last good commit: 23fbdde6205d9351bb52a4b8f11ec38bdbc8561a First bad commit: 0667db14e1f029d56243aa2509ebc5f944388200 From 0667db14e1f029d56243aa2509ebc5f944388200 Mon Sep 17 00:00:00 2001 From: Pavel Begunkov <asml.silence(a)gmail.com> Date: Mon, 18 Mar 2024 22:00:34 +0000 Subject: [PATCH] io_uring: refactor io_req_complete_post() Comparison ========== initial initial last penup last penup first good-96fca68c4fbf bad-afcd48134c58 bad-6498c5c9 bad-87585b05 good-23fbdde6 good-e5c12945 bad-0667db14 Min kIOPS 1429690.00 ( 0.00%) 1321070.00 ( -7.60%) 1384300.00 ( -3.17%) 1387440.00 ( -2.96%) 1447660.00 ( 1.26%) 1440670.00 ( 0.77%) 1383010.00 ( -3.27%) Hmean kIOPS 1593231.10 ( 0.00%) 1465349.28 * -8.03%* 1538450.10 * -3.44%* 1529321.56 * -4.01%* 1594227.00 ( 0.06%) 1595295.82 ( 0.13%) 1539502.39 * -3.37%* Stddev kIOPS 20306.39 ( 0.00%) 18381.94 ( 9.48%) 18745.79 ( 7.69%) 16745.21 ( 17.54%) 17985.08 ( 11.43%) 18572.15 ( 8.54%) 18746.99 ( 7.68%) CoeffVar kIOPS 1.27 ( 0.00%) 1.25 ( 1.58%) 1.22 ( 4.40%) 1.09 ( 14.09%) 1.13 ( 11.48%) 1.16 ( 8.66%) 1.22 ( 4.46%) Max kIOPS 1596750.00 ( 0.00%) 1469160.00 ( -7.99%) 1541920.00 ( -3.43%) 1532590.00 ( -4.02%) 1597540.00 ( 0.05%) 1598520.00 ( 0.11%) 1542790.00 ( -3.38%) BHmean-50 kIOPS 1596569.59 ( 0.00%) 1468943.05 ( -7.99%) 1541505.71 ( -3.45%) 1532015.50 ( -4.04%) 1597234.47 ( 0.04%) 1598279.59 ( 0.11%) 1542587.95 ( -3.38%) BHmean-95 kIOPS 1596456.58 ( 0.00%) 1468444.20 ( -8.02%) 1541379.66 ( -3.45%) 1531885.72 ( -4.04%) 1597010.06 ( 0.03%) 1598150.62 ( 0.11%) 1542470.52 ( -3.38%) BHmean-99 kIOPS 1595092.95 ( 0.00%) 1466984.13 ( -8.03%) 1540200.20 ( -3.44%) 1530919.05 ( -4.02%) 1595875.70 ( 0.05%) 1597044.89 ( 0.12%) 1541282.00 ( -3.37%) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[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 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 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