April 2024 - openSUSE Bugs - openSUSE Mailing Lists

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

[Bug 1215865] New: VUL-0: CVE-2023-0809: mosquitto: excessive memory being allocated based on malicious initial packets that are not CONNECT packets
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215865 Bug ID: 1215865 Summary: VUL-0: CVE-2023-0809: mosquitto: excessive memory being allocated based on malicious initial packets that are not CONNECT packets Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://security-tracker.debian.org/tracker/DSA-5511-1 CVE-2023-0809 Fix excessive memory being allocated based on malicious initial packets that are not CONNECT packets. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215864] New: VUL-0: CVE-2023-3592: mosquitto: memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215864 Bug ID: 1215864 Summary: VUL-0: CVE-2023-3592: mosquitto: memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://security-tracker.debian.org/tracker/DSA-5511-1 CVE-2023-3592 Fix memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218784] New: ark cannot open tar archives which contain files with non-ascii chars in filename like umlauts äöÜ etc
by bugzilla_noreply＠suse.com 03 Nov '24

03 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1218784 Bug ID: 1218784 Summary: ark cannot open tar archives which contain files with non-ascii chars in filename like umlauts äöÜ etc Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: otto47(a)bk13.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- create two files bla.txt and test-ö.txt, then put them into a new tar achive. Opening this archive by ark throws a message "The archive you're trying to open is corrupt. Some files may be missing or damaged." It offers two buttons "Open as Read-Only" plus " Don't Open". Opening as Read-Only displays only one file bla.txt in the archive -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221250] New: glibc-locale-base missing locale() provides
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221250 Bug ID: 1221250 Summary: glibc-locale-base missing locale() provides Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, the glibc-locale package ships with "Provide"s for the different locales it ships: ``` $ rpm -q --provides glibc-locale|head glibc-locale = 2.38-6.1 glibc-locale(x86-64) = 2.38-6.1 locale(glibc:aa_DJ) locale(glibc:aa_DJ.utf8) locale(glibc:aa_ER) locale(glibc:aa_ER@saaho) locale(glibc:aa_ET) locale(glibc:af_ZA) locale(glibc:af_ZA.utf8) locale(glibc:agr_PE) ``` There are two locales which are shipped in glibc-locale-base - en_US.utf8 and C.utf8. Upon packaging something which requires one of them, I noticed that glibc-locale-base is not shipping any `locale()` "Provide"s. ``` $ rpm -q --provides glibc-locale-base glibc-locale-base = 2.38-6.1 glibc-locale-base(x86-64) = 2.38-6.1 libCNS.so()(64bit) libGB.so()(64bit) libISOIR165.so()(64bit) libJIS.so()(64bit) libJISX0213.so()(64bit) libKSC.so()(64bit) ``` I would expect glibc-locale-base to Provide `locale(glibc:C.utf8)` and `locale(glibc:en_US.utf8)` - both to have providers for all locales in the distribution and to make packaging easier. Unfortunately I could not figure out how the "Provide"s in glibc.spec are generated myself, hence I am opening this report instead. Cheers, Georg -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213339] New: Segmentation fault when setting up database with sqlite3 gda-control-center-6.0
by bugzilla_noreply＠suse.com 31 Oct '24

31 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1213339 Bug ID: 1213339 Summary: Segmentation fault when setting up database with sqlite3 gda-control-center-6.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: vojta.kottas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: When setting up a sqlite database using gda-control-center-6.0 as a test in a folder (/tmp/test_db in my case), the gui crashed and the command line showed that a segmentation fault had occurred. This issue does not happen on other distros. Reproducible: Always Steps to Reproduce: 1. Run gda-control-center-6.0 2. Set up database with sqlite Actual Results: Segmentation fault Expected Results: A database is set up in the specified folder. This all came from me trying to install the Pano extension, which upon install crashed the gnome-shell. I tracked the issue to this github issue: https://github.com/oae/gnome-shell-pano/issues/178 Which further tracks the issue down to a problem with the sqlite3 package on openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

1 5