May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220571] New: [META] Packages failing because GCC 14+ treats some warnings as errors
by bugzilla_noreply＠suse.com 21 Mar '25

21 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1220571 Bug ID: 1220571 Summary: [META] Packages failing because GCC 14+ treats some warnings as errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: mjambor(a)suse.com Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- GCC 14 treats the following situations, which were only warnings before, as errors: -Werror=implicit-int -Werror=implicit-function-declaration -Werror=declaration-missing-parameter-type -Werror=return-mismatch -Werror=int-conversion -Werror=incompatible-pointer-types More details about all of these cases together with the most common ways of addressing them and some associated pitfalls is available at https://gcc.gnu.org/gcc-14/porting_to.html For the record, clang has taken a similar step since clang 16, see for example https://www.redhat.com/en/blog/new-warnings-and-errors-clang-16 The preferred method of dealing with these issues is of course fixing the code. Other distributions have shared patches from their porting efforts on relevant upstream mailing lists and bug trackers, Gentoo and RedHat are perhaps most active in this regard, so you can have a look at what they did for their packages at: - https://bugs.gentoo.org/showdependencytree.cgi?id=870412&hide_resolved=0 - https://gitlab.com/fweimer-rh/fedora-modernc/ In case there is for some reason not possible to fix the code, or at least to fix it in time for adoption of GCC 14, it is possible to turn these back to warnings by adding to the compiler options one of the following: -std=gnu89, -std=c89, or -fpermissive. (Especially if you use -fpermissive as a temporary workaround with intention to fix the underlying issues later, I'd suggest leaving the particular bug opened until it is done so.) -- You are receiving this mail because: You are on the CC list for the bug.

1 116

[Bug 1222192] New: Package description for cadvisor shows trivy
by bugzilla_noreply＠suse.com 17 Mar '25

17 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1222192 Bug ID: 1222192 Summary: Package description for cadvisor shows trivy Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: holdenrf2021(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Also shows on https://software.opensuse.org/package/cadvisor $ sudo zypper if trivy cadvisor [sudo] password for root: Loading repository data... Reading installed packages... Information for package trivy: ------------------------------ Repository : Main Repository (OSS) Name : trivy Version : 0.49.1-1.2 Arch : x86_64 Vendor : openSUSE Installed Size : 274.2 MiB Installed : No Status : not installed Source package : trivy-0.49.1-1.2.src Upstream URL : https://github.com/aquasecurity/trivy Summary : A Simple and Comprehensive Vulnerability Scanner for Containers Description : Trivy (`tri` pronounced like trigger, `vy` pronounced like envy) is a simple and comprehensive vulnerability scanner for containers and other artifacts. A software vulnerability is a glitch, flaw, or weakness present in the software or in an Operating System. Trivy detects vulnerabilities of OS packages (Alpine, RHEL, CentOS, etc.) and application dependencies (Bundler, Composer, npm, yarn, etc.). Trivy is easy to use. Just install the binary and you're ready to scan. All you need to do for scanning is to specify a target such as an image name of the container. Information for package cadvisor: --------------------------------- Repository : Main Repository (OSS) Name : cadvisor Version : 0.46.0-1.8 Arch : x86_64 Vendor : openSUSE Installed Size : 29.9 MiB Installed : No Status : not installed Source package : cadvisor-0.46.0-1.8.src Upstream URL : https://github.com/google/cadvisor Summary : A Simple and Comprehensive Vulnerability Scanner for Containers Description : Trivy (`tri` pronounced like trigger, `vy` pronounced like envy) is a simple and comprehensive vulnerability scanner for containers and other artifacts. A software vulnerability is a glitch, flaw, or weakness present in the software or in an Operating System. Trivy detects vulnerabilities of OS packages (Alpine, RHEL, CentOS, etc.) and application dependencies (Bundler, Composer, npm, yarn, etc.). Trivy is easy to use. Just install the binary and you're ready to scan. All you need to do for scanning is to specify a target such as an image name of the container. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216537] New: xdg-utils perl requirement
by bugzilla_noreply＠suse.com 13 Mar '25

13 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1216537 Bug ID: 1216537 Summary: xdg-utils perl requirement Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: simonf.lees(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jslaby(a)suse.com Target Milestone: --- Found By: --- Blocker: --- xdg-utils requires perl via /usr/bin/xdg-screensaver. On minimal systems we'd like to avoid any extra script interpreters. Any chance to avoid using perl there? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222716] New: libssh tries to read config from wrong crypto-policies location
by bugzilla_noreply＠suse.com 13 Mar '25

13 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1222716 Bug ID: 1222716 Summary: libssh tries to read config from wrong crypto-policies location Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: pmonrealgonzalez(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- libssh-config ships /etc/libssh/libssh_server.config which contains # Parse system-wide crypto configuration file Include /usr/etc/crypto-policies/back-ends/libssh.config But there is no such file. It's supposed to be /etc/crypto-policies/back-ends/libssh.config Probably caused by the fix for bug 1211718. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1222314] New: YaST doesn't set zypper locales during installation
by bugzilla_noreply＠suse.com 12 Mar '25

12 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1222314 Bug ID: 1222314 Summary: YaST doesn't set zypper locales during installation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: fvogt(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 874066 --> https://bugzilla.suse.com/attachment.cgi?id=874066&action=edit YaST installation logs I installed YaST with German locale. While the system has the locale configured as expected (e.g. /etc/locale.conf), zypper does not: ~> sudo zypper locales Code | Language | Requested -----+----------+---------- As a result, language specific packages are missing. -- You are receiving this mail because: You are on the CC list for the bug.

1 52

[Bug 1222496] New: ipv6 dies within a day (or faster) on leap 15.5
by bugzilla_noreply＠suse.com 10 Mar '25

10 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1222496 Bug ID: 1222496 Summary: ipv6 dies within a day (or faster) on leap 15.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: abittner(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I just recently narrowed down or observed that on a rather new (fresh) leap system (15.5, all updated, default repos, very simple, single gigabit ethernet pcie interface (realtek, onboard, gigabyte GA-P55-UD3 mainboard) the system becomes rather sluggish and networking stuff (only ssh-ing into the machine, some very simple things) is very unresponsive. until i discovered that even simple things such as direkt ipv6 pings onto ipv6 addresses fail and all packets become lost or never get replied. ipv4 works normal. whole network is a simple LAN with a normal soho gateway/home-router (fritzbox, in germany, deutsche telekom fibre provider consumer grade). yast2 shows dhcp4 on the eth0, but i tried having both dhcp4 and dhcp6 enabled to acquire the machines ip settings / assignments. or via neighbor announcement or what this stuff is called for ip6. either way, after less than a day of uptime of this leap 15.5 machine, the ipv6 stack seems to become non-working. once the ipv6 layer is broken I have situations such as this: -------- ping 2001:4860:4860::8844 PING 2001:4860:4860::8844(2001:4860:4860::8844) 56 data bytes ^C --- 2001:4860:4860::8844 ping statistics --- 323 packets transmitted, 0 received, 100% packet loss, time 329725ms ------------- /sbin/lspci | grep -i net 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ------- i am not very fluent with systemd, so I used rcnetwork to reset the network stack or recycle it, and after this command, ipv6 works normal again as well. > sudo rcnetwork restart fixes the stuff. only to again fail after less than a day, I couldnt narrow this down to a more precise time span. maybe completely random. any ideas? thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1221183] New: Upgrade problems with clang-cpp
by bugzilla_noreply＠suse.com 09 Mar '25

09 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1221183 Bug ID: 1221183 Summary: Upgrade problems with clang-cpp Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: franz.sirl-obs(a)lauterbach.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Hi, during a "zypper --releasever=15.6 dup" upgrade from a fully up-to-date 15.5 installation I got the following messages: Checking for file conflicts: ...................................................................................................................................................................[error] Detected 4 file conflicts: File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from install of clang13-13.0.1-bp156.7.42.x86_64 (Main Repository) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang11-11.0.1-150300.3.6.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang15-15.0.7-150500.4.4.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang7-7.0.1-150100.3.22.2.x86_64 (@System) File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no): yes Even though this is mostly harmless, it disturbs the upgrade experience and probably can be easily fixed by backporting the clang-cpp/update-alternatives change from clang17 to the other clang versions that are part of Leap. regards, Franz -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1218403] New: Qt Creator does not show qt6's examples after `zypper in qt6-*-examples`
by bugzilla_noreply＠suse.com 08 Mar '25

08 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1218403 Bug ID: 1218403 Summary: Qt Creator does not show qt6's examples after `zypper in qt6-*-examples` Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: sauntor(a)yeah.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- As the title says, after install qt 6 examples via zypper, reopen qtcreator, it will not show any qt6 example! But if you install qt5 examples, it shows. Is it a bug or can one fix it himself by some way? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1224808] New: dracut incorrectly modify btrfs compression level for /
by bugzilla_noreply＠suse.com 07 Mar '25

07 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1224808 Bug ID: 1224808 Summary: dracut incorrectly modify btrfs compression level for / Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: fcrozat(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On a MicroOS Desktop system, I'm trying to enable btrfs compression on root fs. The change is made at /etc/fstab level. The initial fstab relevant line was: UUID=no_interest_here / btrfs ro 0 0 Changed to: UUID=no_interest_here / btrfs ro,compress=zstd:1 0 0 and then running transaction-update initrd to ensure dracut is run in the transactional system. However, the stored kernel cmdline by dracut becomes: dracut[I]: root=UUID=980c03f5-35f5-405d-8686-d51ec67c17b4 rootfstype=btrfs rootflags=rw,relatime,seclabel,compress=,ssd,discard=async,space_cache=v2,subvolid=774,subvol=/@/.snapshots/619/snapshot,subvol=@/.snapshots/619/snapshot compress parameter is being stripped. This is with dracut-059+suse.588.g528264be-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1222815] New: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer
by bugzilla_noreply＠suse.com 06 Mar '25

06 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1222815 Bug ID: 1222815 Summary: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- just installing pcp and pmlogger leads to: # systemctl start pmlogger Failed to start pmlogger.service: Unit pmlogger_daily.timer not found. this unit is currently in pcp-zeroconf. however pmlogger.service is in pcp (main package). if zeroconf is supposed to be optional, then the pmlogger_daily.timer dependency is supposed to be made optional. otherwise the timer needs to be moved into the main package (like it appears to be upstream) -- You are receiving this mail because: You are on the CC list for the bug.

1 9