February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207562] New: U-Boot: Raspberry Pi 4 booting from USB stopped booting
by bugzilla_noreply＠suse.com 20 Feb '23

20 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207562 Bug ID: 1207562 Summary: U-Boot: Raspberry Pi 4 booting from USB stopped booting Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: boris(a)pruessmann.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a set of Raspberry Pi 4 booting from USB sticks that all got stuck after the latest automatic MicroOS update. While U-Boot was reporting several timeouts, the thing that stuck out to me was ** Reading file would overwrite reserved memory ** Coincidentally, I had been looking into the exact same issue yesterday, trying to get a CM4 to boot from NVMe. Swapping in the u-boot I compiled yesterday for that set up, I was able to "resurrect" all those systems. Root cause: Apparently, u-boot in its current configuration - maybe related to some hardware or RPi firmware specifics that I am not aware of - is already reporting 8 reserved regions. While many configurations for other systems have CONFIG_LMB_MAX_REGIONS set to e.g. 64, the configurations for Raspberry Pis don't. The error message is wrong, loading the EFI would not overwrite any reserved memory region. It's just that there is no space left to reserve a new one. Fix: For me, increasing CONFIG_LMB_MAX_REGIONS to 64 solved the problem. However, there might be other things at play here since everything worked correctly before the latest update. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1208305] dnsdist: 1.7.3-3.1removes DoH support
by bugzilla_noreply＠suse.com 20 Feb '23

20 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208305 https://bugzilla.suse.com/show_bug.cgi?id=1208305#c2 Adam Majer <amajer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|dnsdist 1.7.3-3.1 / aarch64 |dnsdist: 1.7.3-3.1removes | |DoH support --- Comment #2 from Adam Majer <amajer(a)suse.com> --- (In reply to Marcin Gondek from comment #1) > - Remove DoH since it requires another http server that is not <---- this is > wrong It's correct. dnsdist requires h2o server to build DoH support and that hasn't been updated since 2019. It only exists in the devel project which prevents dnsdist from going to Tumbleweed or Leap ... and I don't want to maintain h2o there. See server:http h2o Otherwise the plan is to add dnsdist to TW and Leap soon. So I'm inclined to remove this dependency. For DoH support, I'm looking at nginx for this in front of dnsdist but I haven't tried it yet. https://www.nginx.com/blog/using-nginx-as-dot-doh-gateway/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208452] SSSD configured with ldap cannot disable sudoers lookup
by bugzilla_noreply＠suse.com 20 Feb '23

20 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208452 https://bugzilla.suse.com/show_bug.cgi?id=1208452#c5 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ckowalczyk(a)suse.com, | |jengelh(a)inai.de Assignee|security-team(a)suse.de |scabrero(a)suse.com --- Comment #5 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- Assigning to / Adding sssd maintainers for this topic. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208464] [wish] tool for setting DNS over TLS
by bugzilla_noreply＠suse.com 20 Feb '23

20 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208464 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |lubos.kocman(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208463] sddm not working - KDE4 Login manager
by bugzilla_noreply＠suse.com 20 Feb '23

20 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208463 https://bugzilla.suse.com/show_bug.cgi?id=1208463#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fvogt(a)suse.com Resolution|--- |UPSTREAM --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- > Unfortunately professional users that use LDAP for storing user accounts cannot change there initial passwords if LDAP requests for it. Sounds like https://github.com/sddm/sddm/issues/472. It's not easy to fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208463] sddm not working - KDE4 Login manager
by bugzilla_noreply＠suse.com 20 Feb '23

20 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208463 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |fabian(a)ritter-vogt.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208463] sddm not working - KDE4 Login manager
by bugzilla_noreply＠suse.com 20 Feb '23

20 Feb '23

1 0

[Bug 1208173] Can't boot devel:RISCV:Factory:Contrib:StarFive:VisionFive2/JeOS-starfivevisionfive2, "sbi_trap_error: hart0: trap handler failed (error -2)"
by bugzilla_noreply＠suse.com 20 Feb '23

20 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208173 https://bugzilla.suse.com/show_bug.cgi?id=1208173#c4 --- Comment #4 from Chester Lin <chester.lin(a)suse.com> --- Hi Aaron, It seems that preload FDT [fdtcontroladdr] owned by VF2 firmware blobs does not match the reviewing DTs in upstream, which is adopted by the contrib project. Could you try the following instructions? --- StarFive # load mmc 1:3 ${fdt_addr_r} /boot/dtb/jh7110-starfive-visionfive-2-vb.dtb 20801 bytes read in 8 ms (2.5 MiB/s) StarFive # load mmc 1:1 ${kernel_addr_r} /EFI/BOOT/bootriscv64.efi 2846720 bytes read in 123 ms (22.1 MiB/s) StarFive # fdt addr ${fdt_addr_r} StarFive # fdt rsvmem add 0x40000000 0x1000 StarFive # bootefi ${kernel_addr_r} ${fdt_addr_r} --- Since the current image has not supported FW booting via SDIO, I will fix the manual installation in Wiki, thanks for your feedback! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208205] New: Latest kernel/TW updates seem to have issues with openrazer drivers and polychromatic (possibly --no-initramfs issue)
by bugzilla_noreply＠suse.com 20 Feb '23

20 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208205 Bug ID: 1208205 Summary: Latest kernel/TW updates seem to have issues with openrazer drivers and polychromatic (possibly --no-initramfs issue) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: iqgrande(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Greetings, Lately the openrazer drivers don't appear to work (e.g., Polychromatic displays "No backends available") on openSUSE Tumbleweed. Since these items aren't automatically rebuilt, I manually uninstall (via `sudo zypper --non-interactive rm `rpm -qa "openrazer-kernel-modules-dkms*"``) and then reinstall them (via command below). Anyways, I notice an error/warning message below (observable when it is installed on lastest TW) that may be the culprit of this (it looks like something is calling a command with the command line option "--no-initramfs" and the command does not know what that is). Could this be the issue? Thank you for your help with this. ```sh > sudo zypper in openrazer-meta polychromatic Loading repository data... Reading installed packages... 'polychromatic' is already installed. No update candidate for 'polychromatic-0.8.0-2.2.noarch'. The highest available version is already installed. Resolving package dependencies... The following 4 NEW packages are going to be installed: openrazer-daemon openrazer-kernel-modules-dkms openrazer-meta python3-openrazer 4 new packages to install. Overall download size: 257.5 KiB. Already cached: 0 B. After the operation, additional 1.6 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving: openrazer-kernel-modules-dkms-3.5.1-2.5.noarch (hardware:razer (openSUSE_Tumbleweed)) (1/4), 60.7 KiB Retrieving: openrazer-kernel-modules-dkms-3.5.1-2.5.noarch.rpm .......................[done (60.7 KiB/s)] Retrieving: openrazer-daemon-3.5.1-2.5.noarch (hardware:razer (openSUSE_Tumbleweed)) (2/4), 145.5 KiB Retrieving: openrazer-daemon-3.5.1-2.5.noarch.rpm ...................................[done (112.0 KiB/s)] Retrieving: python3-openrazer-3.5.1-2.5.noarch (hardware:razer (openSUSE_Tumbleweed)) (3/4), 44.6 KiB Retrieving: python3-openrazer-3.5.1-2.5.noarch.rpm ................................................[done] Retrieving: openrazer-meta-3.5.1-2.5.noarch (hardware:razer (openSUSE_Tumbleweed)) (4/4), 6.7 KiB Retrieving: openrazer-meta-3.5.1-2.5.noarch.rpm ...................................................[done] Checking for file conflicts: ......................................................................[done] (1/4) Installing: openrazer-kernel-modules-dkms-3.5.1-2.5.noarch ..................................[done] (2/4) Installing: openrazer-daemon-3.5.1-2.5.noarch ...............................................[done] (3/4) Installing: python3-openrazer-3.5.1-2.5.noarch ..............................................[done] (4/4) Installing: openrazer-meta-3.5.1-2.5.noarch .................................................[done] Creating symlink /var/lib/dkms/openrazer-driver/3.5.1/source -> /usr/src/openrazer-driver-3.5.1 Building module: cleaning build area... KERNELDIR=/lib/modules/6.1.10-1-default/build make driver..... cleaning build area... razerkbd.ko.zst: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.10-1-default/updates/ razermouse.ko.zst: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.10-1-default/updates/ razerkraken.ko.zst: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.10-1-default/updates/ razeraccessory.ko.zst: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.10-1-default/updates/ Adding any weak-modules getopt: unrecognized option '--no-initramfs' Usage: ${0##*/} [options] {--add-modules|--remove-modules} ${0##*/} [options] {--add-kernel|--remove-kernel} {kernel-release} --add-modules Add a list of modules read from standard input. Create symlinks in compatible kernel's weak-updates/ directory. The list of modules is read from standard input. --remove-modules Remove compatibility symlinks from weak-updates/ directories for a list of modules. The list of modules is read from standard input. --add-kernel Add compatibility symlinks for all compatible modules to the specified or running kernel. --remove-kernel Remove all compatibility symlinks for the specified or current kernel. --verbose Print the commands executed. -dry-run Do not create/remove any files. depmod... ******************************************** * To complete installation, please run: * * # sudo gpasswd -a <yourUsername> plugdev * ******************************************** Executing %posttrans scripts ...................................................................<100%>[\i ``` Kind regards, Anthony -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1208469] New: VUL-0: CVE-2021-32419: schismtracker: information leak via the fmt_mtm_load_song function in fmt/mtm.c
by bugzilla_noreply＠suse.com 20 Feb '23

20 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208469 Bug ID: 1208469 Summary: VUL-0: CVE-2021-32419: schismtracker: information leak via the fmt_mtm_load_song function in fmt/mtm.c Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/357612/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: gabriele.sonnu(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: Security Response Team Blocker: --- An issue in Schism Tracker v20200412 fixed in v.20200412 allows attacker to obtain sensitive information via the fmt_mtm_load_song function in fmt/mtm.c. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32419 https://www.cve.org/CVERecord?id=CVE-2021-32419 https://github.com/schismtracker/schismtracker/commit/1e2cc389a2a058fd13d99… https://github.com/schismtracker/schismtracker/issues/249 -- You are receiving this mail because: You are on the CC list for the bug.

1 1