- openSUSE Bugs

[Bug 1217716] New: No bass, nonfunctional brightness keys on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217716 Bug ID: 1217716 Summary: No bass, nonfunctional brightness keys on Lenovo Slim 7 16" AMD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: variable_valuables761(a)simplelogin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- It seems the bass speakers do not work in the latest Tumbleweed KDE snapshot on the Lenovo Slim 7 16" AMD, 16ARH7, 82UX0001US (and this same model is called Yoga outside the United States). This issue appears to be similar to that of the wide range of recently released laptops that have the CS35L41 and TAS2781 amps, however I cannot find that hardware listed in any of my logs or online spec sheets for this laptop. The closest I can find is that is has a Realtek ALC3287 codec. Also, the keyboard brightness keys do not work. It seems the internal display's brightness value is bugged and shows up as a huge number in brightnessctl (and other tools) rather than something within the expected range. I can provide any logs that would be helpful. I hope this is an appropriate place to report these issues. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1217750] New: Nonfunctional brightness keys on Lenovo Slim 7 16" AMD
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217750 Bug ID: 1217750 Summary: Nonfunctional brightness keys on Lenovo Slim 7 16" AMD Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: variable_valuables761(a)simplelogin.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 871117 --> https://bugzilla.suse.com/attachment.cgi?id=871117&action=edit Output of "brightnessctl -l" for Lenovo 16ARH7 It seems the brightness keys (Fn+F5,Fn+F6) do not work in the latest Tumbleweed KDE snapshot on the Lenovo Slim 7 16" AMD, 16ARH7, 82UX0001US (and this same model is called Yoga outside the United States). It seems the internal display's brightness values are bugged and show up as 0 and "0 (-2147483648%)" in brightnessctl rather than something within the expected range. I've attached the output of "brightnessctl -l", which shows the display and some of the keyboard/charging LEDs on the laptop. Glad to provide any other logs that could be helpful. Hope this is the right place to report this. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1221763] New: ptrace(PTRACE_ATTACH) fails on processes of the same user
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221763 Bug ID: 1221763 Summary: ptrace(PTRACE_ATTACH) fails on processes of the same user Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: giuliano.belinassi(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent updates of tumbleweed broke `ptrace(PTRACE_ATTACH, ...)` when attaching to a process from the same user. This breaks attaching a debugger (gdb) to a process and userspace livepatching. A single line reproducer in a clean system is: ``` $ sleep 5000 & gdb -p $(pidof sleep) ``` If you see the following message: ``` Attaching to process 12606 ptrace: Operation not permitted. ``` This means ptrace is not working. As a contrast, running gdb with sudo works as intended. Value of /proc/sys/kernel/yama/ptrace_scope: ``` $ cat /proc/sys/kernel/yama/ptrace_scope 1 ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 23

[Bug 1217051] New: Enable ptrace_scope=1 by default on openSUSE Tumbleweed
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217051 Bug ID: 1217051 Summary: Enable ptrace_scope=1 by default on openSUSE Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: 95kreaninw95(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently, on openSUSE Tumbleweed, ptrace_scope is disabled by default (ptrace_scope=0). This makes Chromium sandboxing status showing as no and red colored for both Ptrace Protection with Yama LSM entries. Enabling ptrace_scope=1 this fixed the issue. And I think it's a security hardening for the system. There's a request to enable this feature on SUSE 15 SP4: https://bugzilla.suse.com/show_bug.cgi?id=1198601 I am requesting this on openSUSE Tumbleweed. For reference, ptrace_scope is enabled on Ubuntu since 10.10. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1222512] New: VUL-0: CVE-2024-28871: libhtp: excessive CPU usage when parsing malformed traffic
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222512 Bug ID: 1222512 Summary: VUL-0: CVE-2024-28871: libhtp: excessive CPU usage when parsing malformed traffic Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/400377/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: otto.hollmann(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- LibHTP is a security-aware parser for the HTTP protocol and the related bits and pieces. Version 0.5.46 may parse malformed request traffic, leading to excessive CPU usage. Version 0.5.47 contains a patch for the issue. No known workarounds are available. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-28871 https://www.cve.org/CVERecord?id=CVE-2024-28871 https://github.com/OISF/libhtp/commit/79e713f3e527593a45f545e854cd9e6fbb3cd… https://github.com/OISF/libhtp/commit/bf618ec7f243cebfb0f7e84c3cb158955cb32… https://github.com/OISF/libhtp/security/advisories/GHSA-ffr2-45w9-7wmg https://redmine.openinfosecfoundation.org/issues/6757 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1220574] [META] GCC 14 package failures that cannot be worked around with -fpermissive (that are not results of warnings that are now errors by default)
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1220574 Martin Jambor <mjambor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1223820 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223832] New: [Build 669.1] openQA test fails in oscap_remediating_online
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223832 Bug ID: 1223832 Summary: [Build 669.1] openQA test fails in oscap_remediating_online Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://openqa.opensuse.org/tests/4108011/modules/osca p_remediating_online/steps/19 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: andrea.manzini(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-15.6-DVD-aarch64-openscap@aarch64 fails in [oscap_remediating_online](https://openqa.opensuse.org/tests/4108011/modules… ## Test suite description Maintainer: QE Security ## Reproducible Fails since (at least) Build [582.1](https://openqa.opensuse.org/tests/3854976) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… ## First Analysis with reference to https://progress.opensuse.org/issues/152059 on Leap 15.6 , CPE profile is missing so remediation command results in "notapplicable" localhost:~ # oscap xccdf eval --remediate --profile standard --results scan-xccdf-remediate-results.xml xccdf.xml --- Starting Evaluation --- Title Direct root Logins Not Allowed Rule no_direct_root_logins Result notapplicable Title sysctl kernel.sysrq must be 0 Rule rule_misc_sysrq Result notapplicable --- Starting Remediation --- missing 15.6 is also noticeable with # oscap --version OpenSCAP command line tool (oscap) 1.3.6 Copyright 2009--2021 Red Hat Inc., Durham, North Carolina. ==== Supported specifications ==== SCAP Version: 1.3 XCCDF Version: 1.2 OVAL Version: 5.11.1 CPE Version: 2.3 CVSS Version: 2.0 CVE Version: 2.0 Asset Identification Version: 1.1 Asset Reporting Format Version: 1.1 CVRF Version: 1.1 ==== Capabilities added by auto-loaded plugins ==== No plugins have been auto-loaded... ==== Paths ==== Schema files: /usr/share/openscap/schemas Default CPE files: /usr/share/openscap/cpe ==== Inbuilt CPE names ==== Red Hat Enterprise Linux - cpe:/o:redhat:enterprise_linux:- Red Hat Enterprise Linux 5 - cpe:/o:redhat:enterprise_linux:5 Red Hat Enterprise Linux 6 - cpe:/o:redhat:enterprise_linux:6 Red Hat Enterprise Linux 7 - cpe:/o:redhat:enterprise_linux:7 Red Hat Enterprise Linux 8 - cpe:/o:redhat:enterprise_linux:8 Community Enterprise Operating System 5 - cpe:/o:centos:centos:5 Community Enterprise Operating System 6 - cpe:/o:centos:centos:6 Community Enterprise Operating System 7 - cpe:/o:centos:centos:7 Community Enterprise Operating System 8 - cpe:/o:centos:centos:8 Fedora 32 - cpe:/o:fedoraproject:fedora:32 Fedora 33 - cpe:/o:fedoraproject:fedora:33 Fedora 34 - cpe:/o:fedoraproject:fedora:34 Fedora 35 - cpe:/o:fedoraproject:fedora:35 openSUSE Leap 15.1 - cpe:/o:opensuse:leap:15.1 openSUSE Leap 15.2 - cpe:/o:opensuse:leap:15.2 openSUSE Leap 15.3 - cpe:/o:opensuse:leap:15.3 openSUSE Leap 15.4 - cpe:/o:opensuse:leap:15.4 openSUSE Leap 15.5 - cpe:/o:opensuse:leap:15.5 openSUSE Tumbleweed - cpe:/o:opensuse:tumbleweed SUSE Linux Enterprise Server 12 - cpe:/o:suse:sles:12 SUSE Linux Enterprise Desktop 12 - cpe:/o:suse:sled:12 SUSE Linux Enterprise Server 15 - cpe:/o:suse:sles:15 SUSE Linux Enterprise Desktop 15 - cpe:/o:suse:sled:15 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222641] New: Absence of python3-Pillow binary in the distro breaks xpra
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222641 Bug ID: 1222641 Summary: Absence of python3-Pillow binary in the distro breaks xpra Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ncutler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since xpra has the following line in its spec file: Requires: python3-Pillow it was broken by the recent change in Factory: ------------------------------------------------------------------- Fri Apr 21 12:20:55 UTC 2023 - Dirk Müller <dmueller(a)suse.com> - add sle15_python_module_pythons (jsc#PED-68) Because that effectively stops it from building python3-Pillow in Leap 15.6 and SLE-15-SP6 Package Hub. This is because Leap 15.6 and SLE-15-SP6 provide both a default Python 3.6 and an optional Python 3.11. This makes it impossible to install xpra, even though xpra is part of the distro. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222935] spotifyd fails to build on Leap 15.6 - the parameter type `T` may not live long enough
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222935 https://bugzilla.suse.com/show_bug.cgi?id=1222935#c1 Max Lin <mlin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |mlin(a)suse.com Resolution|--- |FIXED --- Comment #1 from Max Lin <mlin(a)suse.com> --- spotifyd was deleted in Backports, spotifyd has been removed from Factory with the same build fail -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222927] lxc fails to build on Leap 15.6 [m[Kpassing argument 4 of '[01m[Kmount_setattr[m[K' from incompatible pointer type [[01;31m[K-Werror=incompatible-pointer-types[m[K]
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222927 https://bugzilla.suse.com/show_bug.cgi?id=1222927#c2 Max Lin <mlin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mlin(a)suse.com --- Comment #2 from Max Lin <mlin(a)suse.com> --- Give Factory's version 5.0.3 a try, it fails with different reason https://build.opensuse.org/package/live_build_log/home:mlin7442:rebuild_fai… [ 162s] Processing files: pam_cgfs-5.0.3-bp156.1.1.x86_64 [ 162s] error: File not found: /home/abuild/rpmbuild/BUILDROOT/lxc-5.0.3-bp156.1.1.x86_64/lib64/security/pam_cgfs.so -- You are receiving this mail because: You are on the CC list for the bug.

1 0