August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1215090] New: go1.20,go1.21: Go toolchain packages missing src/cmd/vendor/github.com/google/pprof/internal/driver/html/
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215090 Bug ID: 1215090 Summary: go1.20,go1.21: Go toolchain packages missing src/cmd/vendor/github.com/google/pprof/internal/driver /html/ 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: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Include the missing directory src/cmd/vendor/github.com/google/pprof/internal/driver/html/ in our go1.1x toolchain packages. This will fix failing builds with applications that directly import runtime/pprof e.g. kubeconform which failed to build with the following error: /usr/lib64/go/1.21/src/cmd/vendor/github.com/google/pprof/internal/driv er/webhtml.go:26:12: pattern html: no matching files found Upstream Go sources vendor certain tools including the pprof profiler [1]. pprof has an asset directory pprof/internal/driver/html containing only html templates used by the pprof viewer and no Go source code. Our go packaging tries to be conservative in what we include in the RPM, and with our find/glob patterns this directory has never been included in the packaging. The issue was first reported with go1.21. However, the last vendoring update was for go1.20, so we will include the fix in go1.20 packaging as well: bb917bd 2022-11-22 09:39 cmd/vendor: update vendored github.com/google/pprof for Go 1.20 release [1] https://github.com/google/pprof -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1221849] New: grub2 bash-completion failed with '_split_longopt: command not found'
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221849 Bug ID: 1221849 Summary: grub2 bash-completion failed with '_split_longopt: command not found' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: glin(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading bash-completion to 2.12, grub2 bash-completion scripts stopped to work and showed the error: _split_longopt: command not found. It's because bash-completion 2.12 renamed '_split_longopt' as '_comp__split_longopt', and bash-completion upstream(*) stated that '_split_longopt' is a private API so it should not be used directly. Instead, the script should use '_init_completion -s' or the newer '_comp_initialize -s' to initialize 'cur', 'prev', and 'split'. (*) https://github.com/scop/bash-completion/issues/1135 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221865] New: Allow Pipewire to operate under the superuser account.
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221865 Bug ID: 1221865 Summary: Allow Pipewire to operate under the superuser account. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All URL: https://gitlab.freedesktop.org/pipewire/pipewire/-/iss ues/2244#note_2336608 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Community User Blocker: No Provide a SystemD override file, as https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2244#note_2336608 explains, to allow the superuser account to use Pipewire when authenticated. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215639] New: Provide the user with a choice of where they want their SWAP partition to be.
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215639 Bug ID: 1215639 Summary: Provide the user with a choice of where they want their SWAP partition to be. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When installing OpenSUSE with multiple internal drives, per https://forums.opensuse.org/t/how-to-transfer-swap-partition-to-os-drive-fr…, the OSTW installer places the SWAP partition on a (seemingly random) secondary internal drive. I don't want this - if I don't select the other drives when asked, it shouldn't touch them (I realize the quoted post states I did, but it refers to a previous installation; I've tested both). Consequently, either don't put the SWAP partiton on another drive unless multiple have been selected (this is the reason for this issue's designation as a bug rather than an enhancement) or allow the user to choose separately where the SWAP partition should be without needing to use the expert partitioner. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1213784] New: bugzilla.opensuse.org e-mails direct to bugzilla.suse,com
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213784 Bug ID: 1213784 Summary: bugzilla.opensuse.org e-mails direct to bugzilla.suse,com Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Target Milestone: --- Found By: --- Blocker: --- When I file a report at opensuse.bugzilla.org and receive a message via e-mail about it, all links in the post direct me to bguzilla.suse.com instead. This is quite the hassle when dealing with frequent notifications on multiple tickets. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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