December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1215760] steam deck usb stop working after waking up from sleep
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1215760 https://bugzilla.suse.com/show_bug.cgi?id=1215760#c9 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED CC| |jslaby(a)suse.com --- Comment #9 from Jiri Slaby <jslaby(a)suse.com> --- This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1214473] ASUS zenbook ux425ea: Can not find wlan adapter
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1214473 https://bugzilla.suse.com/show_bug.cgi?id=1214473#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED CC| |jslaby(a)suse.com --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- By a chance, has this been fixed in the meantime? You did not reset needinfo, nor provided dmesg output, so hard to tell now... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201963] 11th Gen Intel(R) Core(TM) i5-1145G7 throttling to 400MHz from 70°C until it reaches 54°C
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1201963 https://bugzilla.suse.com/show_bug.cgi?id=1201963#c13 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |UPSTREAM --- Comment #13 from Jiri Slaby <jslaby(a)suse.com> --- This is a very old bug. Closing this in a hope this got fixed upstream. Sorry for that. You still can reopen if this still happens. But it would make more sense to report and handle this upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210111] intel 3400 sata controller fail on 6.2.9 kernel
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1210111 https://bugzilla.suse.com/show_bug.cgi?id=1210111#c32 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NORESPONSE Status|NEW |RESOLVED --- Comment #32 from Jiri Slaby <jslaby(a)suse.com> --- As soon as you provide the requested info, feel free to reopen. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213380] Black Screen Issue on openSUSE Tumbleweed ISO after BIOS with DP-HDMI Video Output
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1213380 https://bugzilla.suse.com/show_bug.cgi?id=1213380#c22 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #22 from Jiri Slaby <jslaby(a)suse.com> --- Hopefully this was resolved upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203974] Suspend succeeds, system refuses to wake up.
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1203974 https://bugzilla.suse.com/show_bug.cgi?id=1203974#c15 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|NEW |RESOLVED --- Comment #15 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Gene Snider from comment #14) > Done, https://bugzilla.kernel.org/show_bug.cgi?id=217793 There was no progress at all. It might make sense to send an e-mail to pm directly. Anyway this bug is an upstream one. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1214227] Screen flicker / sometimes no image on internal LCD (i915)
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1214227 https://bugzilla.suse.com/show_bug.cgi?id=1214227#c8 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NORESPONSE CC| |jslaby(a)suse.com Status|NEW |RESOLVED --- Comment #8 from Jiri Slaby <jslaby(a)suse.com> --- As soon as you provide the requested info, feel free to reopen. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231573] New: VUL-0: CVE-2024-47875: python-ipysheet: dompurify: nesting-based mXSS
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1231573 Bug ID: 1231573 Summary: VUL-0: CVE-2024-47875: python-ipysheet: dompurify: nesting-based mXSS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/423728/ OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Security Assignee: python-maintainers(a)suse.com Reporter: camila.matos(a)suse.com QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com, security-team(a)suse.de, smash_bz(a)suse.de Blocks: 1231571 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1231571 +++ DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. DOMpurify was vulnerable to nesting-based mXSS. This vulnerability is fixed in 2.5.0 and 3.1.3. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-47875 https://www.cve.org/CVERecord?id=CVE-2024-47875 https://github.com/cure53/DOMPurify/blob/0ef5e537a514f904b6aa1d7ad9e749e365… https://github.com/cure53/DOMPurify/commit/0ef5e537a514f904b6aa1d7ad9e749e3… https://github.com/cure53/DOMPurify/commit/6ea80cd8b47640c20f2f230c7920b1f4… https://github.com/cure53/DOMPurify/security/advisories/GHSA-gx9m-whjm-85jf -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1232782] New: NetworkManager-applet shows 2 same indicators
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232782 Bug ID: 1232782 Summary: NetworkManager-applet shows 2 same indicators Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: novell(a)tower-net.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878373 --> https://bugzilla.suse.com/attachment.cgi?id=878373&action=edit Screenshot of panel showing 2 nm-applet indicator icons After boot, so first login, the NetworkManager-applet (NetworkManager-applet-1.34.0-150600.1.3.x86_64) shows 2 times the same indicator icon in the task bar. There is only a single process running, so needs to be a bug in the applet to create 2 icons in some circumstances. # ps -efa | grep nm-applet | grep -v grep | sed 's/^[a-z]*[ ]*//' 1747 1594 0 09:44 ? 00:00:00 nm-applet --indicator When killing and restarting, there comes up only the single icon. ~> kill 1747 ; nm-applet --indicator & Could be that the behavior started after upgrading from 15.5 to 15.6. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1189456] Add ashmem and binder drivers
by bugzilla_noreply＠suse.com 05 Dec '24

05 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1189456 https://bugzilla.suse.com/show_bug.cgi?id=1189456#c20 llyyr <llyyr.public(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(llyyr.public@gmai | |l.com) | --- Comment #20 from llyyr <llyyr.public(a)gmail.com> --- (In reply to roke beedell from comment #19) > (In reply to llyyr from comment #18) > > > However, since the original comment wanted to use Waydroid, there is > > a way to do it without building the kernel yourself. Or waiting for an > > upstream solution, which could be... forever at this rate. > > > > dkms also isn't going away, unless I missed something, so "temporary" > > depends on your definition of it. > > Yeah, I'd consider it installing and running to be solution. The method by > which it achieves that isn't particularly important (as long as it's not > virtualized in a snap or Flatpak). > > Can `psi=1` be set in the kernel configuration by the RPM installation > script, or would that potentially have unintended consequences? The kernel documentation for CONFIG_DEFAULT_DISABLED says: > This feature adds some code to the task wakeup and sleep paths of the > scheduler. The overhead is too low to affect common scheduling-intense > workloads in practice (such as webservers, memcache), but it does show up in > artificial scheduler stress tests, such as hackbench. So I don't know if it's a good idea. Also technically you could install Android 9 or older which doesn't require PSI enabled to work. -- You are receiving this mail because: You are on the CC list for the bug.

1 0