June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1212912] New: hamradio/direwolf: Bug - Doesn't install on TW because it wants libgps29 instead of libgps30
by bugzilla_noreply＠suse.com 12 Feb '25

12 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1212912 Bug ID: 1212912 Summary: hamradio/direwolf: Bug - Doesn't install on TW because it wants libgps29 instead of libgps30 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: jansimon.moeller(a)opensuse.org Reporter: ruimail24(a)gmail.com QA Contact: screening-team-bugs(a)suse.de CC: mardnh(a)gmx.de Target Milestone: --- Found By: --- Blocker: --- As per the title, hamradio/direwolf doesn't install on OpenSUSE TW because it depends on libgps29, and TW offers only libgps30. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1216986] New: libguestfs: embeds /etc/hosts
by bugzilla_noreply＠suse.com 12 Feb '25

12 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1216986 Bug ID: 1216986 Summary: libguestfs: embeds /etc/hosts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: carnold(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1081754 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our libguestfs package can produce bit-identical results locally, but when comparing with the official OBS builds, it has this diff in --- old//usr/lib64/guestfs/supermin.d/base.tar.gz/./etc/hosts +++ new//usr/lib64/guestfs/supermin.d/base.tar.gz/./etc/hosts @@ -1,4 +1,26 @@ 127.0.0.1 hst +# +# hosts This file describes a number of hostname-to-address +# mappings for the TCP/IP subsystem. It is mostly +# used at boot time, when no name servers are running. +# On small systems, this file can be used instead of a +# "named" name server. +# Syntax: +# +# IP-Address Full-Qualified-Hostname Short-Hostname +# + 127.0.0.1 hst +# fallback hostname used by NetworkManager 127.0.0.1 hst -127.0.0.1 hst + +# special IPv6 addresses +::1 localhost ipv6-localhost ipv6-loopback + +fe00::0 ipv6-localnet + +ff00::0 ipv6-mcastprefix +ff02::1 ipv6-allnodes +ff02::2 ipv6-allrouters +ff02::3 ipv6-allhosts + Chances are, that it pulls in the /etc/hosts file from the build VM and that one might vary depending from usage of a preinstallimage or other factors. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1220905] New: salt-master: Error loading known_hosts
by bugzilla_noreply＠suse.com 10 Feb '25

10 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1220905 Bug ID: 1220905 Summary: salt-master: Error loading known_hosts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: egotthold(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This error is happening to me on openSUSE MicroOS 20240302 (the logs reveal this has been happening for a good while already). The error is known upstream and is due to a combination of changes in pygit2 and how Salt is starting up its daemon. https://github.com/saltstack/salt/issues/64121#issuecomment-1705658539 Since we are not using the onedir packaging yet one cannot downgrade to another pygit2 version via salt-pip. I am not that deep into the codebase to know if a systemd drop-in that specifies the user used for running the salt-master.service as "salt", is enough. The log of the salt-master is spammed with the following message: Mar 04 00:01:51 esprimo-1 salt-master[30997]: [ERROR ] Error occurred fetching git_pillar remote 'main git(a)gitlab.com:<user>/<repo>.git': error loading known_hosts: Mar 04 00:01:51 esprimo-1 salt-master[30997]: Traceback (most recent call last): Mar 04 00:01:51 esprimo-1 salt-master[30997]: File "/usr/lib/python3.11/site-packages/salt/utils/gitfs.py", line 1996, in _fetch Mar 04 00:01:51 esprimo-1 salt-master[30997]: fetch_results = origin.fetch(**fetch_kwargs) Mar 04 00:01:51 esprimo-1 salt-master[30997]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Mar 04 00:01:51 esprimo-1 salt-master[30997]: File "/usr/lib64/python3.11/site-packages/pygit2/remotes.py", line 155, in fetch Mar 04 00:01:51 esprimo-1 salt-master[30997]: payload.check_error(err) Mar 04 00:01:51 esprimo-1 salt-master[30997]: File "/usr/lib64/python3.11/site-packages/pygit2/callbacks.py", line 99, in check_error Mar 04 00:01:51 esprimo-1 salt-master[30997]: check_error(error_code) Mar 04 00:01:51 esprimo-1 salt-master[30997]: File "/usr/lib64/python3.11/site-packages/pygit2/errors.py", line 65, in check_error Mar 04 00:01:51 esprimo-1 salt-master[30997]: raise GitError(message) Mar 04 00:01:51 esprimo-1 salt-master[30997]: _pygit2.GitError: error loading known_hosts: -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221893] New: distrobox : launchers of exported applications no longer work
by bugzilla_noreply＠suse.com 10 Feb '25

10 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1221893 Bug ID: 1221893 Summary: distrobox : launchers of exported applications no longer work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: c.chalu(a)free.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, Since the last distrobox update on Tumbleweed, the launchers of exported applications no longer work. In konsole on my host system : /usr/bin/distrobox-enter -n -n boxdebgeophar -- ' geophar' return this error : Error: runc: exec failed: unable to start container process: exec: " geophar": executable file not found in $PATH: OCI runtime attempted to invoke a command that was not found /usr/bin/distrobox-enter -n boxtumbleweed -- ' lyx %F' Error: runc: exec failed: unable to start container process: exec: " lyx %F": executable file not found in $PATH: OCI runtime attempted to invoke a command that was not found Information for package distrobox: ---------------------------------- Repository : Dépôt principal (OSS) Name : distrobox Version : 1.7.0.1_g7a56b6e-1.1 Arch : noarch Vendor : openSUSE Installed Size : 493.9 KiB Installed : Yes Status : up-to-date Source package : distrobox-1.7.0.1_g7a56b6e-1.1.src Upstream URL : https://github.com/89luca89/distrobox Summary : Use any linux distribution inside your terminal Description : Use any Linux distribution inside your terminal. Distrobox uses podman or docker to create containers using the Linux distribution of your choice. The created container will be tightly integrated with the host, allowing sharing of the HOME directory of the user, external storage, external USB devices and graphical apps (X11/Wayland), and audio. Operating System: openSUSE Tumbleweed 20240321 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: Wayland Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226394] New: xdg-desktop-portal-lxqt not started by default
by bugzilla_noreply＠suse.com 07 Feb '25

07 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1226394 Bug ID: 1226394 Summary: xdg-desktop-portal-lxqt not started by default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: lxqt-bugs(a)suse.de Reporter: brbigam(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- xdg-desktop-portal-lxqt isn't automatically started by xdg-desktop-portal on login, so the LXQt file dialog isn't picked up by apps that could use it, like Firefox. Steps to reproduce: Log in to LXQt check running processes, such as in qps check file dialog in Firefox with widget.use-xdg-desktop-portal.file-picker set to 1 Actual result: x-d-p is running, but not x-d-p-lxqt no file dialog opens in Firefox (Unless another portal backend is also installed) Expected result: x-d-p-lxqt is running LXQt file dialog is used by Firefox System: Tumbleweed 20240613 and earlier, as long as LXQt 2.0.0 has been available LXQt 2.0.0 xdg-desktop-portal-lxqt 1.0.2 xdg-desktop-portal 1.18.4 Qt 6.7.1 Workaround: If I run /usr/libexec/xdg-desktop-portal --replace after login, x-d-p correctly picks up x-d-p-lxqt and everything works correctly. Adding this to autostart apps also works correctly. So if it's an upstream issue, openSUSE might consider adding this to packaging temporarily as a workaround. I don't know what the underlying problem might be. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226463] New: algif_hash in kernel-obs-build causes an openssl-1_1 test failure
by bugzilla_noreply＠suse.com 06 Feb '25

06 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1226463 Bug ID: 1226463 Summary: algif_hash in kernel-obs-build causes an openssl-1_1 test failure 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875539 --> https://bugzilla.suse.com/attachment.cgi?id=875539&action=edit diff of lsinitrd From https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… : > [ 248s] ../test/recipes/30-test_afalg.t (Wstat: 256 (exited 1) Tests: 1 Failed: 1) Comparing /proc/modules in the build VM shows: +algif_hash 12288 0 - Live 0x0000000000000000 (E) +af_alg 36864 1 algif_hash, Live 0x0000000000000000 (E) So apparently, algif_hash brings af_alg and that for some unknown reason breaks the test. If I rm algif_hash from KERNEL_MODULES, it works again. -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1221270] New: rpmlint fails to handle 6GB source rpms
by bugzilla_noreply＠suse.com 06 Feb '25

06 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1221270 Bug ID: 1221270 Summary: rpmlint fails to handle 6GB source rpms 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: asn(a)cryptomilk.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- It looks like rpmlint fails to extract a source rpm which is bigger than 4GB? [ 274s] RPMLINT report: [ 274s] =============== [ 312s] (none): E: fatal error while reading //home/abuild/rpmbuild/SRPMS/piper-voices-1.0.0-0.src.rpm: [Errno 2] No such file or directory: '/tmp/rpmlint.piper-voices-1.0.0-0.src. rpm.83mfaz86/piper-voices.spec' [ 312s] Traceback (most recent call last): [ 312s] File "/opt/testing/bin/rpmlint.real", line 8, in <module> [ 312s] sys.exit(lint()) [ 312s] ^^^^^^ [ 312s] File "./rpmlint/cli.py", line 184, in lint [ 312s] File "./rpmlint/lint.py", line 123, in run [ 312s] File "./rpmlint/lint.py", line 91, in _run [ 312s] File "./rpmlint/lint.py", line 264, in validate_files [ 312s] File "./rpmlint/lint.py", line 290, in validate_file [ 312s] File "./rpmlint/lint.py", line 283, in validate_file [ 312s] File "./rpmlint/lint.py", line 299, in run_checks [ 312s] File "./rpmlint/checks/AbstractCheck.py", line 16, in check [ 312s] File "./rpmlint/checks/SpecCheck.py", line 179, in check_source [ 312s] File "./rpmlint/checks/SpecCheck.py", line 187, in check_spec [ 312s] File "./rpmlint/checks/SpecCheck.py", line 229, in _check_non_utf8_spec_file [ 312s] File "./rpmlint/pkg.py", line 105, in is_utf8 [ 312s] FileNotFoundError: [Errno 2] No such file or directory: '/tmp/rpmlint.piper-voices-1.0.0-0.src.rpm.83mfaz86/piper-voices.spec' Reproducer (needs git-lfs): osc co home:gladiac piper-voices cd 'home:gladiac/piper-voices/' osc service manualrun osc build I wonder if it has issues with source RPMs which are bigger than 4GB: # unrpm /srv/oscbuild/build-root-openSUSE_Tumbleweed-x86_64/home/abuild/rpmbuild/SRPMS/piper-voices-1.0.0-0.src.rpm /srv/oscbuild/build-root-openSUSE_Tumbleweed-x86_64/home/abuild/rpmbuild/SRPMS/piper-voices-1.0.0-0.src.rpm: files over 4GB not supported by cpio, use rpm2archive instead cpio: premature end of archive -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1218424] New: go1.22 release tracking
by bugzilla_noreply＠suse.com 05 Feb '25

05 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1218424 Bug ID: 1218424 Summary: go1.22 release tracking 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.22 (expected February 2024) is a major release of Go. Minor releases of go1.22.x will be provided through February 2025. This issue tracks go1.22.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1222479] New: VUL-0: CVE-2024-22189: kubo: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
by bugzilla_noreply＠suse.com 03 Feb '25

03 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1222479 Bug ID: 1222479 Summary: VUL-0: CVE-2024-22189: kubo: quic-go: memory exhaustion attack against QUIC's connection ID mechanism Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/400376/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: bwiedemann(a)suse.com Reporter: camila.matos(a)suse.com QA Contact: qa-bugs(a)suse.de CC: camila.matos(a)suse.com, security-team(a)suse.de, smash_bz(a)suse.de Blocks: 1222461 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1222461 +++ quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-22189 https://www.cve.org/CVERecord?id=CVE-2024-22189 https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c… https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478 https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-manageme… https://www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s https://bugzilla.redhat.com/show_bug.cgi?id=2273513 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1217820] New: spdlog on aarch64 and armv{6,7} needs rebuilt against libfmt10
by bugzilla_noreply＠suse.com 03 Feb '25

03 Feb '25

https://bugzilla.suse.com/show_bug.cgi?id=1217820 Bug ID: 1217820 Summary: spdlog on aarch64 and armv{6,7} needs rebuilt against libfmt10 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Right now spdlog-devel is broken on the ARM ports as it pulls in fmt 10 headers while the library itself exports fmt 9 types. (I do not have an arm machine and only noticed this because vscode fails to build) What's worse, spdlog exports fmt types as part of its ABI which in particular means that it breaks abi without soname bump whenever fmt breaks abi. This would be less of a problem if fmt-9 were simply dropped from the distro (due to broken deps triggering a rebuild), but as it still exists, every spdlog consumer must also be manually rebuilt. -- You are receiving this mail because: You are on the CC list for the bug.

1 16