March 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1219988] New: go1.20,go1.21,go1.22: ensure VERSION file is present in go1.x toolchain GOROOT
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1219988 Bug ID: 1219988 Summary: go1.20,go1.21,go1.22: ensure VERSION file is present in go1.x toolchain GOROOT 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: --- go1.x tool 'go tool dist' and 'go tool distpack' require the source file VERSION to be present in GOROOT. Current go1.x packaging is missing this file, ensure it is present. Example: $ go version go1.22.0 linux/amd64 $ go tool dist list go tool dist: FAILED: not a Git repo; must put a VERSION file in $GOROOT $ go tool distpack distpack: open /usr/lib64/go/1.22/VERSION: no such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 3

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