December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1234610] [Build ] openQA test fails in firstrun
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234610 https://bugzilla.suse.com/show_bug.cgi?id=1234610#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED CC| |fvogt(a)suse.com --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- Fixed with https://build.opensuse.org/request/show/1231691 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1101107] trackerbug: packages do not build reproducibly from including kernel version
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1101107 Bug 1101107 depends on bug 1234629, which changed state. Bug 1234629 Summary: sendmail: embeds uname -r https://bugzilla.suse.com/show_bug.cgi?id=1234629 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1229918] AUDIT-0: deepin-api-proxy: new dbus services of deepin-api-proxy
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1229918 https://bugzilla.suse.com/show_bug.cgi?id=1229918#c6 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|security-team(a)suse.de |matthias.gerstner(a)suse.com --- Comment #6 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- I will have a look to make some progress with pending deepin reviews after this long time. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190766] python-rich backports requirement
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1190766 https://bugzilla.suse.com/show_bug.cgi?id=1190766#c5 Nathan Cutler <ncutler(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NORESPONSE Status|IN_PROGRESS |RESOLVED --- Comment #5 from Nathan Cutler <ncutler(a)suse.com> --- no response -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234454] Compiling external modules fails with "/usr/src/linux-6.13.0-rc2-1.gf92fc5d/include/config/auto.conf: No such file or directory"
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234454 https://bugzilla.suse.com/show_bug.cgi?id=1234454#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- Packaging was updated, so I merged to master and pushed: users/jslaby/master/for-next -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212877] New: [RPi4] cannot wake up after suspend triggered
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1212877 Bug ID: 1212877 Summary: [RPi4] cannot wake up after suspend triggered Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: zluo(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 867900 --> https://bugzilla.suse.com/attachment.cgi?id=867900&action=edit yast2 logs ssh to my RPi 4 Model B, later I see following -- p200300ea3707b36b055205817bcf9853:~ # Broadcast message from root@localhost (Fri 2023-06-30 06:03:37 UTC): The system will suspend now! -- then I try to wake it up by hitting keyboard and click on mouse, nothing happened on screen. attache yast2logs. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1234646] Lockdown is not activated with Secure Boot in kernel 6.12
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234646 https://bugzilla.suse.com/show_bug.cgi?id=1234646#c1 --- Comment #1 from Jiri Slaby <jslaby(a)suse.com> --- Please update also the SUSE-2025 branch (SLE16 is based on 6.12). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228173] sssd: getsubids throws `libsubid_sss.so did not provide @subid_free@`
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228173 https://bugzilla.suse.com/show_bug.cgi?id=1228173#c5 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1233131 Dylan Meysmans <contact(a)mettekou.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(scabrero(a)suse.com | |) --- Comment #5 from Dylan Meysmans <contact(a)mettekou.com> --- (In reply to Samuel Cabrero from comment #4) > (In reply to Dylan Meysmans from comment #3) > > (In reply to Samuel Cabrero from comment #2) > > > Fixed in sssd 2.10 beta2. > > > > When can we expect sssd 2.10 to arrive for Tumbleweed? I see it is already > > in network:ldap. > > It will arrive soon, the OBS request is in place: > https://build.opensuse.org/requests/1222104. Will need to wait for > https://bugzilla.suse.com/show_bug.cgi?id=1230051, though. It seems that bug has been closed for some time now. Which other issues prevent sssd 2.10 from arriving for Tumbleweed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1232983] New: VUL-0: CVE-2024-51744: forgejo: github.com/golang-jwt/jwt/v4: Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232983 Bug ID: 1232983 Summary: VUL-0: CVE-2024-51744: forgejo: github.com/golang-jwt/jwt/v4: Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/426863/ OS: Other Status: NEW Whiteboard: CVSSv3.1:SUSE:CVE-2024-51744:3.1:(AV:N/AC:H/PR:N/UI:R/ S:U/C:L/I:N/A:N) Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: andrea.mattiazzo(a)suse.com QA Contact: security-team(a)suse.de Blocks: 1232936 Target Milestone: --- Found By: --- Blocker: --- golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-51744 https://www.cve.org/CVERecord?id=CVE-2024-51744 https://github.com/golang-jwt/jwt/commit/7b1c1c00a171c6c79bbdb40e4ce7d19706… https://github.com/golang-jwt/jwt/security/advisories/GHSA-29wx-vh33-7x7r https://bugzilla.redhat.com/show_bug.cgi?id=2323735 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1233752] [Build E.84.3] openQA test fails in trup_smoke -- TPM failure in 6.12
by bugzilla_noreply＠suse.com 17 Dec '24

17 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1233752 https://bugzilla.suse.com/show_bug.cgi?id=1233752#c47 --- Comment #47 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1233752) was mentioned in https://build.opensuse.org/request/show/1231647 Factory / kernel-source -- You are receiving this mail because: You are on the CC list for the bug.

1 0