March 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1218653] New: Gimp 3 scheduled for May - Lets start the preparations
by bugzilla_noreply＠suse.com 22 Jan '25

22 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1218653 Bug ID: 1218653 Summary: Gimp 3 scheduled for May - Lets start the preparations Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- - https://www.phoronix.com/news/GIMP-3.0-May-2024-Schedule - https://librearts.org/2023/11/gimp-3-0-roadmap/ current test packages are in: https://build.opensuse.org/project/show/graphics:gimp:master i dropped a mail to Jehan to find out if the master snapshots of gegl and babl are still needed or not. if we want to have parallel buildable packages it would be easy to rename the master gimp package to gimp3 and apply this patch: ``` Index: gimp.spec =================================================================== --- gimp.spec (revision 1878) +++ gimp.spec (working copy) @@ -67,14 +67,16 @@ %global abiver 5 %global apiver 3.0 -Name: gimp +%define pkg_name gimp + +Name: gimp3 Version: 3.0 Release: 0 Summary: The GNU Image Manipulation Program License: GPL-3.0-or-later Group: Productivity/Graphics/Bitmap Editors URL: https://www.gimp.org/ -Source: %{name}-%{version}.tar.zst +Source: %{pkg_name}-%{version}.tar.zst Source1: macros.gimp # openSUSE palette file Source2: openSUSE.gpl @@ -184,6 +186,7 @@ Provides: gimp-2.0 = %{version} Provides: gimp(abi) = %{abiver} Provides: gimp(api) = %{apiver} +Conflicts: gimp %description The GIMP is an image composition and editing program, which can be @@ -296,7 +299,7 @@ %endif %prep -%autosetup -p1 +%autosetup -p1 -n %{pkg_name}-%{version} %build #define _lto_cflags %{nil} ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 30

[Bug 1216739] New: sssd: support configs and drop-ins in /usr
by bugzilla_noreply＠suse.com 21 Jan '25

21 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1216739 Bug ID: 1216739 Summary: sssd: support configs and drop-ins in /usr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: scabrero(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ckowalczyk(a)suse.com, jengelh(a)inai.de, scabrero(a)suse.com Target Milestone: --- Found By: --- Blocker: --- sssd ships configs in /etc. In order to be able to ship configs as packages, support for having configs in /usr is desireable as well. Any chance to simplement /usr/etc support? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1221429] New: Presence dialog for ssh id_ed25519_sk keys not showing up
by bugzilla_noreply＠suse.com 21 Jan '25

21 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1221429 Bug ID: 1221429 Summary: Presence dialog for ssh id_ed25519_sk keys not showing up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When logging in via ssh using a id_ed25519_sk key (e.g. Yubikey), typically ssh prompts a dialog, prompting the user to push the presence key on the hardware dongle. In Plasma6 when doing ssh against a host that requires this presence button to be pushed, the dialog does not show up. The login still works, ssh just blocks and when I push the button it works, but the confirmation dialog does not show up anymore. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1221095] New: Go application packages can no longer set CGO_ENABLED=0 if external linker will be used
by bugzilla_noreply＠suse.com 14 Jan '25

14 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1221095 Bug ID: 1221095 Summary: Go application packages can no longer set CGO_ENABLED=0 if external linker will be used 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: --- Per Go upstream change https://go-review.googlesource.com/c/website/+/569296, as of go1.21.8+ and go1.22.1+ go build commands cannot set CGO_ENABLED=0 if the external linker will be used. (Cgo lets Go packages call C code, see https://go.dev/blog/cgo, 2011) The most commonly used option that triggers the external linker is -buildmode=pie, which we aspirationally use in most Go application packages behind conditionals for architectures where it is unsupported, currently only ppc64le. We first encountered this issue when trying to set the go metapackage from go1.21 to go1.22. Approximately 40+ Go application packages in Factory set CGO_ENABLED=0 and -buildmode=pie together. On arch i586, builds started to fail with error: -buildmode=pie requires external (cgo) linking, but cgo is not enabled This tracking bug will be referenced for SR submissions to Go application packages to adapt to the new requirements. Most of these submissions will to remove CGO_ENABLED=0 absent a requirement for its use by a specific package. Upstream comments from the above change: https://go.dev/issue/31544, CL 477839 When using an external (C) linker with cgo enabled, the `runtime/cgo` package is now supplied to the Go linker as an additional dependency to ensure that the Go runtime is compatible with any additional libraries added by the C linker. https://go.dev/issue/46330, CL 522239 go build commands that invoke the linker now error out if an external (C) linker will be used but cgo is not enabled. (The Go runtime requires cgo support to ensure that it is compatible with any additional libraries added by the C linker.) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1220086] New: xfce4-terminal does not honor --geometry parameter under wayland
by bugzilla_noreply＠suse.com 09 Jan '25

09 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1220086 Bug ID: 1220086 Summary: xfce4-terminal does not honor --geometry parameter under wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I decided to play around with wayland instead of x11 to find out, if everything works as expected for me. On thing I found, is that xfce4-terminal does not honor --geometry parameter under wayland. It is always started centered, it seems to use the size parameters, though. Operating System: openSUSE Tumbleweed 20240216 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.4-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222194] New: kubo ipfs tries to start before the network appears and fails with an error
by bugzilla_noreply＠suse.com 09 Jan '25

09 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222194 Bug ID: 1222194 Summary: kubo ipfs tries to start before the network appears and fails with an error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- kubo ipfs tries to start before the network appears and fails with an error > [werwolf@power] ~ > ❯ sudo LANG=c zypper info kubo > Refreshing service 'openSUSE'. > Loading repository data... > Reading installed packages... > > > Information for package kubo: > ----------------------------- > Repository : filesystems > Name : kubo > Version : 0.26.0-16.17 > Arch : x86_64 > Vendor : obs://build.opensuse.org/filesystems > Installed Size : 79.2 MiB > Installed : Yes > Status : up-to-date > Source package : kubo-0.26.0-16.17.src > Upstream URL : https://github.com/ipfs/kubo > Summary : IPFS implementation in Go > Description : > IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single bittorrent swarm, exchanging git objects. IPFS provides an interface as simple as the HTTP web, but with permanence > built in. You can also mount the world at /ipfs. As far as I understand, the problem can be solved by simply adding one line to the systemd service file > Wants=network-online.target > After=network-online.target -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1218455] New: kernel: NOHZ tick-stop error: local softirq work is pending
by bugzilla_noreply＠suse.com 08 Jan '25

08 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1218455 Bug ID: 1218455 Summary: kernel: NOHZ tick-stop error: local softirq work is pending Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with kernel 6.6.6 (and continuing with 6.6.7) I get kernel: NOHZ tick-stop error: local softirq work is pending, handler #08!!! a few times within one or two minutes and during this time performance is degraded heavily. This happens about every two days, so it is not that much of a problem, but a bit annoying. system is: Operating System: openSUSE Tumbleweed 20231226 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1219817] New: GNOME 45.3 session crashed when changing sound output
by bugzilla_noreply＠suse.com 08 Jan '25

08 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1219817 Bug ID: 1219817 Summary: GNOME 45.3 session crashed when changing sound output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872650 --> https://bugzilla.suse.com/attachment.cgi?id=872650&action=edit journal.txt OS: Tumbleweed 20240209 gnome-shell version: 45.3-2.2 System: Dell Latitude 5440 laptop Had Bluetooth headphones connected, in the top-right GNOME "tray" area I changed the sound output to the Handsfree option of my headphones and my session immediately crashed, I was returned to the GDM login screen. Logged back in, everything seemed to be working again, changed the sound output without crashes. First time I've had this happen. There are some errors about code being reached that shouldn't be, stack traces and core dumps in the journal (attached file). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1220727] New: VUL-0: CVE-2023-51774: rubygem-json-jwt: JWE can sometimes be used to bypass JSON:JWT.decode
by bugzilla_noreply＠suse.com 07 Jan '25

07 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1220727 Bug ID: 1220727 Summary: VUL-0: CVE-2023-51774: rubygem-json-jwt: JWE can sometimes be used to bypass JSON:JWT.decode Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/395627/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: abergmann(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- The json-jwt (aka JSON::JWT) gem 1.16.3 for Ruby sometimes allows bypass of identity checks via a sign/encryption confusion attack. For example, JWE can sometimes be used to bypass JSON::JWT.decode. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-51774 https://www.cve.org/CVERecord?id=CVE-2023-51774 https://github.com/P3ngu1nW/CVE_Request/blob/main/novjson-jwt.md -- You are receiving this mail because: You are on the CC list for the bug.

1 3

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

06 Jan '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 115