December 2023 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 1213574] New: Thunderbird OAUTH2 broken
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213574 Bug ID: 1213574 Summary: Thunderbird OAUTH2 broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent Thunderbird updates broke OAUTH2 and this seems to be a common problem with Thunderbird 102. With this update it no longer presents an OAUTH2 dialog for IMAP. My employer uses Microsoft Office365 and OAUTH2 is essential. This used to work. Even with a clean install and nuking the previous configuration it will never prompt for OAUTH2 authentication like it used to. Note that the OAUTH2 dialog DOES work with SMTP, but not IMAP. Searching the Internet reveals that this is a common problem with this release. Please upgrade Thunderbird to a newer release for 15.4. I'm not quite ready to upgrade to 15.5 just yet since I use this machine for heavy development work. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217260] New: slib build failed in %post
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217260 Bug ID: 1217260 Summary: slib build failed in %post 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: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello slib does not build on Leap 15.6. This should be fixed before Beta (Feb 2023). https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 Build log from Leap 15.6 https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… [ 26s] ERROR: In procedure open-file: [ 26s] In procedure open-file: No such file or directory: "/usr/share/guile/site/2.2/slibcat" [ 26s] ... running 50-check-binary-kernel-log [ 26s] ... running 50-check-core-files [ 26s] ... checking for core files [ 26s] ... running 50-check-debuginfo [ 26s] ... testing for empty debuginfo packages [ 26s] ... running 50-check-filelist [ 26s] ... checking filelist [ 26s] ... running 50-check-gconf-scriptlets [ 26s] ... testing GConf scriptlet presence [ 26s] ... running 50-check-installtest [ 26s] ... testing for pre/postinstall scripts that are not idempotent [ 27s] Backtrace: [ 27s] 12 (apply-smob/1 #<catch-closure 5638290ba180>) [ 27s] In ice-9/boot-9.scm: [ 27s] 705:2 11 (call-with-prompt ("prompt") #<procedure 5638290d38c0 ?> ?) [ 27s] In ice-9/eval.scm: [ 27s] 619:8 10 (_ #(#(#<directory (guile-user) 563829187140>))) [ 27s] In ice-9/command-line.scm: [ 27s] 181:18 9 (_ #<input: string 563829192a80>) [ 27s] In unknown file: [ 27s] 8 (eval (require (quote new-catalog)) #<directory (guile-?>) [ 27s] In /usr/share/slib/require.scm: [ 27s] 145:16 7 (slib:require new-catalog) [ 27s] 79:15 6 (catalog:get new-catalog) [ 27s] In /usr/share/slib/guile-2.init: [ 27s] 257:4 5 (with-load-pathname _ _) [ 27s] In ice-9/boot-9.scm: [ 27s] 2312:4 4 (save-module-excursion #<procedure 563829261990 at ice-?>) [ 27s] 3832:12 3 (_) [ 27s] In /usr/share/slib/mklibcat.scm: [ 27s] 22:2 2 (_) [ 27s] In ice-9/ports.scm: [ 27s] 461:11 1 (call-with-output-file "/usr/share/guile/site/2.2/slib?" ?) [ 27s] In unknown file: [ 27s] 0 (open-file "/usr/share/guile/site/2.2/slibcat" "w" # #f) [ 27s] [ 27s] ERROR: In procedure open-file: [ 27s] In procedure open-file: No such file or directory: "/usr/share/guile/site/2.2/slibcat" [ 27s] postinstall script of slib-3b7-bp156.2.2.noarch.rpm failed -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213148] New: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213148 Bug ID: 1213148 Summary: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: catice567(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1215323] New: [trackerbug] docker 24.0.6-ce update
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1215323 Bug ID: 1215323 Summary: [trackerbug] docker 24.0.6-ce update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- - Update to Docker 24.0.6-ce. See upstream changelong online at <https://docs.docker.com/engine/release-notes/24.0/#2406>. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213500] New: [trackerbug] docker 24.0.4-ce update
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213500 Bug ID: 1213500 Summary: [trackerbug] docker 24.0.4-ce update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- - Update to Docker 24.0.4-ce. See upstream changelog online at <https://docs.docker.com/engine/release-notes/24.0/#2404>. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1217350] New: Some Electron-based applications are unable to detect dark mode
by bugzilla_noreply＠suse.com 01 May '24

01 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217350 Bug ID: 1217350 Summary: Some Electron-based applications are unable to detect dark mode Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: ars2swim(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870861 --> https://bugzilla.suse.com/attachment.cgi?id=870861&action=edit Visual Studio Code, though preconfigured by default with a dark theme, has a light titlebar, suggesting that Electron detects a light theme in the system. Some Electron-based applications are unable to detect that the system is running with a dark theme, despite dark mode being the default configuration for openSUSE Aeon. This can lead to a lack of UI consistency. I noticed this primarily in apps like Visual Studio Code and Signal. It's worth pointing out that this doesn't occur on every Electron app (namely, the Webcord Flatpak is able to handle theming just fine). I'll also point out that this isn't necessarily an issue with the apps alone or GNOME, because the aforementioned apps--whether packaged as a Flatpak, tarball, or run within a distrobox--do correctly use a dark theme on Ubuntu 23.10. I'm not an expert on SELinux, but it is my best guess as to why this is happening. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213537] New: myrb / myrs drivers cause hang on boot when using a Mylex AcceleRAID 170 (DAC960)
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1213537 Bug ID: 1213537 Summary: myrb / myrs drivers cause hang on boot when using a Mylex AcceleRAID 170 (DAC960) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: medwards-suse(a)mirkwood.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868350 --> https://bugzilla.suse.com/attachment.cgi?id=868350&action=edit dmesg Booting opensuse leap 15.5 fails on this machine - shortly after the myrb and myrs drivers load and detect the AcceleRAID 170 and drives connected to this card, booting simply stops. Waiting for a few minutes will let me see kernel warnings about hung processes, but booting never completes at this point. Adding modprobe.blacklist=myrb and modprobe.blacklist=myrs to the kernel commandline lets boot complete, though obviously without the AcceleRAID card in use. Once booted, I was able to enable dyndbg for these two drivers: # for d in myr{s,b}; do echo 'file drivers/scsi/${d}.c +p' > /sys/kernel/debug/dynamic_debug/control; done Loading the drivers manually caused the modprobe for myrs to hang (myrb loaded w/o issue), leading me to believe the problem lies within the myrs driver. dyndbg of myrb + myrs: drivers/scsi/myrs.c:2114 [myrs]myrs_monitor =_ "monitor tick\012" drivers/scsi/myrs.c:1822 [myrs]myrs_slave_alloc =_ "Logical device mapping %d:%d:%d -> %d\012" drivers/scsi/myrs.c:471 [myrs]myrs_get_fwstatus =_ "Sending GetHealthStatus\012" drivers/scsi/myrs.c:338 [myrs]myrs_get_pdev_info =_ "Sending GetPhysicalDeviceInfoValid for pdev %d:%d:%d\012" drivers/scsi/myrs.c:249 [myrs]myrs_get_ldev_info =_ "Sending GetLogicalDeviceInfoValid for ldev %d\012" drivers/scsi/myrs.c:189 [myrs]myrs_get_ctlr_info =_ "Sending GetControllerInfo\012" drivers/scsi/myrb.c:2445 [myrb]myrb_monitor =_ "reschedule monitor\012" drivers/scsi/myrb.c:2436 [myrb]myrb_monitor =_ "new enquiry\012" drivers/scsi/myrb.c:2432 [myrb]myrb_monitor =_ "get background init status\012" drivers/scsi/myrb.c:2427 [myrb]myrb_monitor =_ "get consistency check progress\012" drivers/scsi/myrb.c:2421 [myrb]myrb_monitor =_ "get rebuild progress\012" drivers/scsi/myrb.c:2415 [myrb]myrb_monitor =_ "get logical drive info\012" drivers/scsi/myrb.c:2409 [myrb]myrb_monitor =_ "get rebuild progress\012" drivers/scsi/myrb.c:2403 [myrb]myrb_monitor =_ "get error table\012" drivers/scsi/myrb.c:2397 [myrb]myrb_monitor =_ "get event log no %d/%d\012" drivers/scsi/myrb.c:2390 [myrb]myrb_monitor =_ "monitor tick\012" drivers/scsi/myrb.c:2360 [myrb]myrb_handle_scsi =_ "Device nonresponsive\012" drivers/scsi/myrb.c:2355 [myrb]myrb_handle_scsi =_ "Attempt to Access Beyond End of Logical Drive" drivers/scsi/myrb.c:2350 [myrb]myrb_handle_scsi =_ "Logical Drive Nonexistent or Offline" drivers/scsi/myrb.c:2331 [myrb]myrb_handle_scsi =_ "Bad Data Encountered\012" drivers/scsi/myrb.c:1699 [myrb]myrb_pdev_slave_alloc =_ "slave alloc pdev %d:%d state %x\012" drivers/scsi/myrb.c:1693 [myrb]myrb_pdev_slave_alloc =_ "device not present, skip\012" drivers/scsi/myrb.c:1687 [myrb]myrb_pdev_slave_alloc =_ "Failed to get device state, status %x\012" drivers/scsi/myrb.c:1639 [myrb]myrb_ldev_slave_alloc =_ "slave alloc ldev %d state %x\012" drivers/scsi/myrb.c:1438 [myrb]myrb_ldev_queuecommand =_ "ldev %u in state %x, skip\012" drivers/scsi/myrb.c:1414 [myrb]myrb_read_capacity =_ "Capacity %u, blocksize %u\012" See attachment for dmesg output. myrs was loaded around timestamp 16372.039529. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1218327] New: AUDIT-0: dnf5: Audit dnf5daemon D-Bus files for whitelist
by bugzilla_noreply＠suse.com 30 Apr '24

30 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218327 Bug ID: 1218327 Summary: AUDIT-0: dnf5: Audit dnf5daemon D-Bus files for whitelist Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: ngompa13(a)gmail.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- For my package found in OBS in system:packagemanager:dnf/dnf5 I would like a whitelisting for the following rpmlint errors: [ 520s] dnf5daemon-server.x86_64: E: dbus-file-unauthorized (Badness: 10000) /etc/dbus-1/system.d/org.rpm.dnf.v0.conf (sha256 file digest default filter:4dd26c049d6240e6640106bb8805ec958e03d9ad79eb2823152b9a92156554a9 shell filter:4dd26c049d6240e6640106bb8805ec958e03d9ad79eb2823152b9a92156554a9 xml filter:bd2c589d0cb083d7b8a7696b98e0a344b2501ecd2d91a7fe447028cb47f75210) [ 520s] dnf5daemon-server.x86_64: E: dbus-file-unauthorized (Badness: 10000) /usr/share/dbus-1/system-services/org.rpm.dnf.v0.service (sha256 file digest default filter:8dff187bd14e516fd976731fb4ab3996bb92b36dfa944733655641a6aec215e1 shell filter:8dff187bd14e516fd976731fb4ab3996bb92b36dfa944733655641a6aec215e1 xml filter:<failed-to-calculate>) [ 520s] Packaging D-Bus services requires a review and whitelisting by the SUSE [ 520s] security team. If the package is intended for inclusion in any SUSE product [ 520s] please open a bug report to request review of the package by the security [ 520s] team. Please refer to [ 520s] https://en.opensuse.org/openSUSE:Package_security_guidelines#audit_bugs for [ 520s] more information. This blocks my submit request: https://build.opensuse.org/request/show/1134536 -- You are receiving this mail because: You are on the CC list for the bug.

1 8