July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1228602] New: systemd-cryptenroll fails on standard secureboot settings on ASUS motherboard - system still bootable but without a recovery key
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228602 Bug ID: 1228602 Summary: systemd-cryptenroll fails on standard secureboot settings on ASUS motherboard - system still bootable but without a recovery key Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: mats.bursjo(a)ownmail.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876379 --> https://bugzilla.suse.com/attachment.cgi?id=876379&action=edit log from an unsuccessful install The installation of Aeon Desktop RC3 fails when the secureboot settings on my ASUS prime x670-p motherboard is set to "Other OS" and "Standard". It requires the more lax "Other OS" - "Custom" setting" to work. I tried installing 3 times. Once the error was hidden in the UI due to an inability to copy the user data (this log is however lost). I was instead booted into a working OS that updated some TPM package - but since the recovery key was not enrolled I could not boot again. I then got the error two more times. I then changed the bios setting mentioned above, and installation worked. Attached is the log file from the last failed install. I understand this is probably a very specific bug, and I submit it mostly to help any other person in the same situation. The system being in a bootable state when the cryptenroll fails to enroll a recovery key seems like a good way to have a system update nuke some poor soul's data. Best regards Mats -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227621] New: IncompleteRead Error with Packaging Distrobox
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227621 Bug ID: 1227621 Summary: IncompleteRead Error with Packaging Distrobox Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Distrobox Assignee: rbrown(a)suse.com Reporter: pirateclip(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This on the surface looks similar to boo#834990 except that this requires one to use osc inside of a distrobox such as the image made for packagers: https://en.opensuse.org/Distrobox#Distrobox_For_Packagers and it affects doing a local build of any package on build.opensuse.org too. I have not gotten and IncompleteRead errors when using osc outside of distrobox (such as installing it on the MicroOS base system or on TW) Steps to reproduce: 1 Create a distrobox as detailed on the wiki: $ distrobox create --root --name tumbleweed-pkg --image registry.opensuse.org/opensuse/distrobox-packaging:latest 2 Do zypper dup (the image is not always up to date and recommends need to be installed or else osc misses a lot of features such as the loading bar when you run osc co and it is taking some time to download something) 3 Enter into it and osc co any package 4 Do a local build with osc build If osc then tries to download dependencies then *sometimes* it will fail midway through with a message like this: [40/171] (openSUSE:Tumbleweed) libuuid1-2.40.1-4.1.x86_64.rpm: 100%|############################################################################| Time: 0:00:00 [41/171] (openSUSE:Tumbleweed) libsmartcols1-2.40.1-4.1.x86_64.rpm: 100%|#######################################################################| Time: 0:00:00 [42/171] (openSUSE:Tumbleweed) libcrypt1-4.4.36-1.6.x86_64.rpm: 100%|###########################################################################| Time: 0:00:00 Connection broken: IncompleteRead(196304 bytes read, 31608179 more expected) | ETA: --:--:-- I can work around this by then just rerunning osc build and then it will download some more deps before maybe throwing another IncompleteRead error while trying to download a different dependency. Eventually it succeeds and I can get on with my local build -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227749] New: Orange PI 5 Plus limited functionality
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227749 Bug ID: 1227749 Summary: Orange PI 5 Plus limited functionality Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876046 --> https://bugzilla.suse.com/attachment.cgi?id=876046&action=edit idbloader for Orange PI 5 Plus I managed to get U-Boot running on the Orange PI 5 Plus with a couple of key SUSE patches to the point where it is booting into OpenSUSE AARCH64 Rockchip version. Currently only the following are working: - PCIe - NVME - eMMC/SD - Serial port The following are not working: - USB - Realtek RTL8125 2.5G Ethernet drivers (seen on PCIe bus) - Realtek RTL8852BE (seen on PCIe bus, not driver seems to be available) Note that in U-Boot that USB also does not work and the network cards are not supported (as of 7/15). I am attaching my U-Boot and idbloader for this board which should allow it to boot, use the usual offset 64 for the idbloader and offset 16384 for U-Boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222902] New: Monitor detection fails after hard reset
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222902 Bug ID: 1222902 Summary: Monitor detection fails after hard reset Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: david.mulder(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a hard reset (laptop locked up when I tried to suspend it), my external monitors are no longer detected. I've seen this happen 3 times in as many weeks (on several recent versions of TW), and the only solution I've found is reinstalling TW. > sudo hwinfo --monitor 45: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.iVNqLoWlvi7 Parent ID: _Znp.TcrQYGYoBS2 Hardware Class: monitor Model: "BOE CQ LCD Monitor" Vendor: BOE "BOE CQ" Device: eisa 0x0a7d Serial ID: "0" Resolution: 1920x1200@60Hz Size: 345x215 mm Year of Manufacture: 2021 Week of Manufacture: 27 Detailed Timings #0: Resolution: 1920x1200 Horizontal: 1920 1968 2000 2140 (+48 +80 +220) -hsync Vertical: 1200 1203 1209 1260 (+3 +9 +60) +vsync Frequencies: 161.79 MHz, 75.60 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 1920x1200 Vert. Sync Range: 40-60 Hz Hor. Sync Range: 76-76 kHz Bandwidth: 161 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #39 (VGA compatible controller) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217428] New: VUL-0: CVE-2023-6258: pkcs11-provider: Side-channel proofing PKCS#1 1.5 paths
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1217428 Bug ID: 1217428 Summary: VUL-0: CVE-2023-6258: pkcs11-provider: Side-channel proofing PKCS#1 1.5 paths Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/385844/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: luca.boccassi(a)gmail.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: thomas.leroy(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Side-channel proofing PKCS#1 1.5 paths (Marvin) Ref: https://github.com/latchset/pkcs11-provider/pull/308 References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-6258 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1220119] New: Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:"
by bugzilla_noreply＠suse.com 27 Dec '24

27 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220119 Bug ID: 1220119 Summary: Some tests on o3 triggers dmesg "clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large:" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jwiesner(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Some tests running on o3 (openQA instance on https://openqa.opensuse.org/) triggers in dmesg. All tests run in VM via qemu. This is on x86_64 on my private openQA worker by ltp_net_tcp_cmds, triggered for 2 tests: arp and host (both tests did not fail): OpenQA::run_ltp.pm: Starting ipneigh01_arp [ 410.818828][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 410.820365][ C0] clocksource: 'kvm-clock' wd_nsec: 506724586 wd_now: 610448443a wd_last: 60e6144350 mask: ffffffffffffffff [ 410.821824][ C0] clocksource: 'tsc' cs_nsec: 49302930542 cs_now: 17c1364ba0a cs_last: 153fdc32526 mask: ffffffffffffffff [ 410.823293][ C0] clocksource: Clocksource 'tsc' skewed 48796205956 ns (48796 ms) over watchdog 'kvm-clock' interval of 506724586 ns (506 ms) [ 410.824843][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 410.825707][ C0] tsc: Marking TSC unstable due to clocksource watchdog [ 411.109710][T28135] Initializing XFRM netlink socket OpenQA::run_ltp.pm: Starting ipneigh01_ip OpenQA::run_ltp.pm: Starting arping01 OpenQA::run_ltp.pm: Starting clockdiff01 OpenQA::run_ltp.pm: Starting ftp OpenQA::run_ltp.pm: Starting host [ 410.818845][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 410.820687][ C0] clocksource: 'kvm-clock' wd_nsec: 506741379 wd_now: 61044885d3 wd_last: 60e6144350 mask: ffffffffffffffff [ 410.821794][ C0] clocksource: 'tsc' cs_nsec: 804834172 cs_now: 154a546a082 cs_last: 153fdc32526 mask: ffffffffffffffff [ 410.822919][ C0] clocksource: Clocksource 'tsc' skewed 298092793 ns (298 ms) over watchdog 'kvm-clock' interval of 506741379 ns (506 ms) [ 410.824088][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 410.824768][ C0] tsc: Marking TSC unstable due to clocksource watchdog [ 411.126759][T28138] Initializing XFRM netlink socket Also, originally I noted this on ltp_net_tcp_cmds running on ppc64le on o3 (kernel tests in https://openqa.opensuse.org/group_overview/32) where host test keeps failing (but arp test is working), I don't see it on ltp_net_tcp_cmds on x86_64 on o3. I was not able to trigger this on VM on my laptop (x86_64). Others found that systemd-networkd test on Tumbleweed on x86_64 (https://openqa.opensuse.org/group_overview/1) [ 570.754611][ C0] Showing busy workqueues and worker pools: [ 570.755654][ C0] workqueue events: flags=0x0 [ 570.756580][ C0] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256 refcnt=2 [ 570.756586][ C0] pending: drm_fb_helper_damage_work [ 570.759551][ C0] sysrq: Show Blocked State zDBFr-0- [ 311.682306][ C0] clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc' as unstable because the skew is too large: [ 311.684482][ C0] clocksource: 'kvm-clock' wd_nsec: 621509306 wd_now: 49d9caac63 wd_last: 49b4bf31a9 mask: ffffffffffffffff [ 311.686513][ C0] clocksource: 'tsc' cs_nsec: 952336665 cs_now: a3a422af12 cs_last: a327415f8e mask: ffffffffffffffff [ 311.688559][ C0] clocksource: Clocksource 'tsc' skewed 330827359 ns (330 ms) over watchdog 'kvm-clock' interval of 621509306 ns (621 ms) [ 311.690452][ C0] clocksource: 'kvm-clock' (not 'tsc') is current clocksource. [ 311.691559][ C0] tsc: Marking TSC unstable due to clocksource watchdog Test runs also on aarch64, but error is not there. Is it a problem of openQA setup? There are other bugs. -- You are receiving this mail because: You are on the CC list for the bug.

1 41

[Bug 1226017] New: fwupd fails TPM fw upgrade with 'Secure boot is enabled, but shim isn't installed to EFI/opensuse/shim.efi'
by bugzilla_noreply＠suse.com 26 Dec '24

26 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1226017 Bug ID: 1226017 Summary: fwupd fails TPM fw upgrade with 'Secure boot is enabled, but shim isn't installed to EFI/opensuse/shim.efi' Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: anselm.gora(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 Build Identifier: fwupd expects to find EFI/opensuse/shim.efi while on openSUSE Aeon the path is EFI/systemd/shim.efi https://github.com/fwupd/fwupd/blob/eb3d26079d7b0e6f0db70b066fcb7b31ac7bcec… fwupd seems to use os release ID but it's also a build option: https://github.com/fwupd/fwupd/blob/eb3d26079d7b0e6f0db70b066fcb7b31ac7bcec… Tumbleweed seems to patch it: https://build.opensuse.org/projects/openSUSE:Factory/packages/fwupd/files/f… Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1222490] New: Kruner and Home Menu only show krusader in root mode
by bugzilla_noreply＠suse.com 25 Dec '24

25 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1222490 Bug ID: 1222490 Summary: Kruner and Home Menu only show krusader in root mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: smartinds(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874135 --> https://bugzilla.suse.com/attachment.cgi?id=874135&action=edit Screenshot Why Kruner and the "Home Menu" only show “krusader” in root mode? I have krusader in my path :~> ls -l /bin/kru* -rwxr-xr-x 1 root root 85016 mar 26 13:06 /bin/krunner -rwxr-xr-x 1 root root 84520 abr 1 13:21 /bin/krunner-plugininstaller -rwxr-xr-x 1 root root 2832680 mar 13 03:21 /bin/krusader ~> ls -l /usr/bin/kru* -rwxr-xr-x 1 root root 85016 mar 26 13:06 /usr/bin/krunner -rwxr-xr-x 1 root root 84520 abr 1 13:21 /usr/bin/krunner-plugininstaller -rwxr-xr-x 1 root root 2832680 mar 13 03:21 /usr/bin/krusader Krusader works if I run it with the terminal, but is weird that don show in "Kruner" nor "Home Menu". Note: Sometimes (random) both show me Krusader in "Normal Mode", but not the "Root Mode". -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1220490] New: GCC 14: gdb package fails
by bugzilla_noreply＠suse.com 23 Dec '24

23 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220490 Bug ID: 1220490 Summary: GCC 14: gdb package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mjambor(a)suse.com, tdevries(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Building gdb with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: gdb-13.2/gdb/configure: line 418: test: too many arguments configure: error: 18086 gdb-13.2/gdb/configure: line 307: return: Specific: numeric argument required gdb-13.2/gdb/configure: line 317: exit: Specific: numeric argument required gdb-13.2/gdb/configure: conftest.c: In function 'main': gdb-13.2/gdb/configure: conftest.c:54:18: error: implicit declaration of function 'strerror'; did you mean 'Fstrerror'? [-Wimplicit-function-declaration] gdb-13.2/gdb/configure: 54 | strerror (errno)); gdb-13.2/gdb/configure: | ^~~~~~~~ gdb-13.2/gdb/configure: | Fstrerror gdb-13.2/gdb/configure: conftest.c:75:9: error: implicit declaration of function 'strcmp' [-Wimplicit-function-declaration] gdb-13.2/gdb/configure: 75 | if (strcmp ("librpm.so", "/lib64/librpm.so.10") != 0) gdb-13.2/gdb/configure: | ^~~~~~ gdb-13.2/gdb/configure: conftest.c:41:1: note: include '<string.h>' or provide a declaration of 'strcmp' gdb-13.2/gdb/configure: 40 | #include <errno.h> gdb-13.2/gdb/configure: +++ |+#include <string.h> gdb-13.2/gdb/configure: 41 | Builds with: Index: gdb.spec_dir/gdb-13.2/gdb/configure =================================================================== --- gdb.spec_dir.orig/gdb-13.2/gdb/configure +++ gdb.spec_dir/gdb-13.2/gdb/configure @@ -17942,6 +17942,7 @@ else #include <rpm/rpmlib.h> #include <dlfcn.h> #include <errno.h> +#include <string.h> int main () -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1224452] New: installing audacious pulls in -devel packages
by bugzilla_noreply＠suse.com 21 Dec '24

21 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1224452 Bug ID: 1224452 Summary: installing audacious pulls in -devel packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: kocelfc(a)tutanota.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874956 --> https://bugzilla.suse.com/attachment.cgi?id=874956&action=edit zypper.log When trying to install the audacious package, zypper tries to pull in a lot of -devel packages: The following recommended package was automatically selected: audacious-plugins-extra The following 64 NEW packages are going to be installed: at-spi2-core-devel audacious audacious-plugins audacious-plugins-extra dbus-1-devel glib2-devel libaudcore5 libaudgui5 libaudqt2 libaudtag3 libblkid-devel libcddb2 libcue2 libdrm-devel libeconf-devel libffi-devel libfluidsynth3 libgirepository-2_0-0 libglvnd-devel libinstpatch-1_0-2 liblirc_client0 libmms0 libmodplug1 libmount-devel libopusfile0 libpciaccess-devel libpcre2-32-0 libpcre2-posix3 libselinux-devel libsepol-devel libsidplayfp6 libsndio7 libstdc++-devel libX11-devel libXau-devel libxcb-dbe0 libxcb-devel libxcb-screensaver0 libxcb-xf86dri0 libxcb-xtest0 libxcb-xvmc0 libXext-devel libXfixes-devel libXi-devel libxkbcommon-devel libXrandr-devel libXrender-devel libXtst-devel Mesa-KHR-devel Mesa-libEGL-devel Mesa-libGL-devel pcre2-devel qt6-core-devel qt6-dbus-devel qt6-gui-devel qt6-svg-devel qt6-widgets-devel typelib-1_0-Atspi-2_0 typelib-1_0-GIRepository-3_0 typelib-1_0-GLibUnix-2_0 vulkan-devel vulkan-headers wayland-devel xorgproto-devel -- You are receiving this mail because: You are on the CC list for the bug.

1 3