May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225299] New: systemd-boot doesn't display passphrase prompt for decryption until a key is pressed
by bugzilla_noreply＠suse.com 01 Jul '24

01 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225299 Bug ID: 1225299 Summary: systemd-boot doesn't display passphrase prompt for decryption until a key is pressed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875117 --> https://bugzilla.suse.com/attachment.cgi?id=875117&action=edit no prompt Installed TW with systemd-boot on my laptop about a month ago. It has 1 drive (nvme), it has one partition for /boot/efi, one for root and an encrypted partition for /home, no LVM. When booting the kernel messages just stop and there's no indicator asking to enter the passphrase for /home partition unless I press a key, then the prompt "Please enter passphrase for disk..." appears. Or if I press escape then it displays this gray semi-graphical screen with the same message. The kernel command line contains 'splash=silent quiet' and Plymouth is installed, I didn't do any configuration there but it's not displayed, just plain kernel messages when booting. It would be nice to have a better passphrase prompt especially on a 14" 2880x1800 screen where the kernel messages are tiny. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1225298] New: systemd-boot fails to boot 6.9.1
by bugzilla_noreply＠suse.com 01 Jul '24

01 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225298 Bug ID: 1225298 Summary: systemd-boot fails to boot 6.9.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875116 --> https://bugzilla.suse.com/attachment.cgi?id=875116&action=edit screen photo Installed TW with systemd-boot about a month ago, updated today to 20240523, rebooted, everything seemed to work but noticed it was still on 6.8.8. Rebooted, selected 6.9.1 from the systemd-boot menu and it gets stuck while booting. Reaches target Initrd File System Times out waiting for device /dev/gpt-auto-root Attached a photo of the screen with boot messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224152] New: MicroOS + systemd-boot: boot menu title does not match Tumbleweed snapshot number
by bugzilla_noreply＠suse.com 01 Jul '24

01 Jul '24

1 1

[Bug 1222069] New: Systemd-boot issue after upgrade
by bugzilla_noreply＠suse.com 01 Jul '24

01 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222069 Bug ID: 1222069 Summary: Systemd-boot issue after upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc(a)user.net Reporter: regis(a)hubelia.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/123.0.0.0 Safari/537.36 Build Identifier: Boot/System config: systemd-boot with encrypted root Last known working version: 7.6.1 After doing a transactional-update dup, we get the following error: /init: error while loading shared libraries: libsystemd-core-255.so: cannot open shared object file: No such file or directory Very similar, if not exactly the same issue as https://bbs.archlinux.org/viewtopic.php?pid=2158970 We use MicroOS on 2 Framework 13th Gen laptops, a i9 9900k desktop, and 2x 13900k desktops. The latest upgrades works fine on the 2 13900k desktops, but the same error occurs on the 9900k and the 2 Framework laptops. Unfortunatly, we do not have bios upgrades for the Framework laptops or the 9900k, we are using the most recent bios on all computers. Reproducible: Always Steps to Reproduce: 1. boot version 7.6.1 - works perfectly 2. run "transacitonal-update dup" and reboot Actual Results: the boot loader is interupted with the above error message and a kernel panic (see the arch linux link for a screenshot, we have the same on our side) Expected Results: The system should boot as usual -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222183] New: pcr-oracle fails to parse LOADER_CONF_EVENT_TAG_ID
by bugzilla_noreply＠suse.com 01 Jul '24

01 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222183 Bug ID: 1222183 Summary: pcr-oracle fails to parse LOADER_CONF_EVENT_TAG_ID Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: aplanas(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I believe on March, 26 I attempted to update MicroOS instance. Update failed, but more importantly it also stopped generating the correct predictions. As far as I can tell, attempted update managed to install newer version of systemd-boot which started to add TPM2 event entry that pcr-oracle fails to parse. 10:~ # /tmp/sdbootutil update-predictions ::: Initializing predictor for sha256:0,2,4,7,9 from eventlog ::: Detected TPMv2 event log ::: Successfully read 46 events from TPM event log ::: Created new predictor ::: runtime_read_efi_application(/dev/vda2, /EFI/systemd/shim.efi) ::: Reading EFI application (/dev/vda2)/EFI/systemd/shim.efi ::: runtime_read_efi_application(/dev/vda2, /EFI/systemd/grub.efi) ::: Reading EFI application (/dev/vda2)/EFI/systemd/grub.efi Error: Unable to parse EVENT_EVENT_TAG event from TPM log ::: 04f9c: event type=EVENT_EVENT_TAG pcr=5 digests=4 data=32 bytes ::: sha1 01d4e1ca16f118f6fcd954e175c0116c4a4f746b ::: sha256 bdbea6dbc6791de89a483abc3a61af8e910249e7565682ff2011c910a490520a ::: sha384 12ebd339e16a134b0aeeb3114bd5b233f9f862037b7550c922a7c73686fa616995273aa75144640d4fb911945d7b5f55 ::: sha512 7c4a18a73955640cde19777b87735f1ca928fe6ef6b54aa3a6d8117c8eaadbd6c00778165a9a320303644489c242c88a5b2ca6b20be1ffe75f70d5b930f647f6 ::: Data: ::: 0000 2a 58 bc f5 18 00 00 00 6c 00 6f 00 61 00 64 00 65 00 72 00 2e 00 63 00 6f 00 6e 00 66 00 00 00 *X......l.o.a.d.e.r...c.o.n.f... Fatal: Aborting. Error: Failed to install TPM predictions for From systemd sources src/fundamental/tpm2-pcr.h:#define LOADER_CONF_EVENT_TAG_ID UINT32_C(0xf5bc582a) loader.conf existed for a long time. Bootloader was updated at this day. 10:~ # ls -l /boot/efi/loader total 32 drwxr-xr-x. 2 root root 8192 Feb 23 14:58 entries -rwxr-xr-x. 1 root root 6 Dec 26 21:28 entries.srel -rwxr-xr-x. 1 root root 41 Dec 26 21:28 loader.conf -rwxr-xr-x. 1 root root 32 Mar 30 18:26 random-seed 10:~ # efibootmgr BootCurrent: 0007 Timeout: 3 seconds BootOrder: 0007,0000,0001,0002,0003,0004,0005,0006 Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331) Boot0001* UEFI Misc Device PciRoot(0x0)/Pci(0x2,0x0){auto_created_boot_option} Boot0002* UEFI PXEv4 (MAC:525400123456) PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,1)/IPv4(0.0.0.00.0.0.0,0,0){auto_created_boot_option} Boot0003* UEFI PXEv6 (MAC:525400123456) PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,1)/IPv6([::]:<->[::]:,0,0){auto_created_boot_option} Boot0004* UEFI HTTPv4 (MAC:525400123456) PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri(){auto_created_boot_option} Boot0005* UEFI HTTPv6 (MAC:525400123456) PciRoot(0x0)/Pci(0x3,0x0)/MAC(525400123456,1)/IPv6([::]:<->[::]:,0,0)/Uri(){auto_created_boot_option} Boot0006* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1) Boot0007* openSUSE Boot Manager HD(2,GPT,4d904b6d-6495-4891-8481-fe0fbdacec21,0x1800,0xfa000)/File(\EFI\systemd\shim.efi) 10:~ # ls -l /boot/efi/EFI/systemd total 1880 -rwxr-xr-x. 1 root root 846096 Mar 28 21:11 MokManager.efi -rwxr-xr-x. 1 root root 62 Mar 28 21:11 boot.csv -rwxr-xr-x. 1 root root 98160 Mar 28 21:11 grub.efi -rwxr-xr-x. 1 root root 17 Mar 28 21:11 installed_by_sdbootutil -rwxr-xr-x. 1 root root 934024 Mar 28 21:11 shim.efi -rwxr-xr-x. 1 root root 451 Mar 17 07:57 tpm2-pcr-public-key.pem -rwxr-xr-x. 1 root root 631 Mar 17 07:57 tpm2-pcr-signature.json 10:~ # Apart from the obvious bug in pcr-oracle, this invalidates any claim of "immutability" of MicroOS - failed update makes it impossible to boot MicroOS without human intervention. 10:~ # ls -l /boot/efi/EFI/systemd/grub.efi -rwxr-xr-x. 1 root root 98160 Mar 28 21:11 /boot/efi/EFI/systemd/grub.efi 10:~ # ls -l /usr/lib/systemd/boot/efi/systemd-bootx64.efi -rw-r--r--. 1 root root 94576 Feb 21 22:42 /usr/lib/systemd/boot/efi/systemd-bootx64.efi 10:~ # -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225779] New: gtest.pc injects a bogus include directory which breaks libstdc++ headers
by bugzilla_noreply＠suse.com 01 Jul '24

01 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225779 Bug ID: 1225779 Summary: gtest.pc injects a bogus include directory which breaks libstdc++ headers 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: Development Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- > pkg-config --cflags gtest -DGTEST_HAS_PTHREAD=1 -lpthread -I/usr/lib64/pkgconfig/../../include The `-I` is changed to `-isystem` by a downstream build system (Google Ninja) When calling g++-13 with this flag on a file which includes `<cstdlib>`, i'm getting a confusing build error: In file included from ../../v8/include/v8.h:21, from ../../third_party/electron_node/src/node.h:79, from ../../third_party/electron_node/src/api/async_resource.cc:1: /usr/include/c++/13/cstdlib:79:15: fatal error: stdlib.h: No such file or directory 79 | #include_next <stdlib.h> | ^~~~~~~~~~ This is gtest-1.10.0-1.10.x86_64 The problem happens on both 15.5 and 15.6, does not happen on Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1220085] New: Data races reported by KCSAN on s390x
by bugzilla_noreply＠suse.com 01 Jul '24

01 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1220085 Bug ID: 1220085 Summary: Data races reported by KCSAN on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: miroslav.franc(a)suse.com Reporter: miroslav.franc(a)suse.com QA Contact: qa-bugs(a)suse.de CC: ihno(a)suse.com, marcela.maslanova(a)suse.com, ro(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 872851 --> https://bugzilla.suse.com/attachment.cgi?id=872851&action=edit dmesg log from s390x VM z15 factory KCSAN enabled kernel* on s390x reports a lot of data races. See the dmesg log for details. * https://download.suse.de/ibs/home:/mfranc:/branches:/SUSE:/Factory:/Head:/k… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1225174] New: conflicto actualizacion
by bugzilla_noreply＠suse.com 30 Jun '24

30 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225174 Bug ID: 1225174 Summary: conflicto actualizacion Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: allanvejar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- <html>Ha fallado la resolución de dependencias:<br/><br/>el elemento tlp-1.6.1-2.1.noarch que se va a instalar tiene un conflicto con tuned, que proporciona el elemento tuned-2.22.1.2+git.86ac977-3.1.noarch instalado</html> -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1222993] New: maliit-keyboard should have libqt5-qtwayland as dependency
by bugzilla_noreply＠suse.com 30 Jun '24

30 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222993 Bug ID: 1222993 Summary: maliit-keyboard should have libqt5-qtwayland as dependency Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: suse.com(a)s.bjoern-tantau.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I just installed maliit-keyboard and selected it in KDE as my virtual keyboard. But it would not appear. I fixed it by installing libqt5-qtwayland. So I guess this should be a dependency of maliit. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219521] New: dmd compiler cannot find standard library
by bugzilla_noreply＠suse.com 29 Jun '24

29 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1219521 Bug ID: 1219521 Summary: dmd compiler cannot find standard library 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: andrea.manzini(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- To reproduce on a Tumbleweed installation: # zypper in dmd dub sudo zypper in dub dmd Loading repository data... Reading installed packages... Resolving package dependencies... The following recommended package was automatically selected: phobos-devel The following 4 NEW packages are going to be installed: dmd dub libphobos2-0_105 phobos-devel # cat > main.d import std.stdio; void main() { writeln("Hello, world"); } # dmd main.d /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: cannot find -lphobos2: No such file or directory collect2: error: ld returned 1 exit status Error: linker exited with status 1 as a workaround, installing # zypper in phobos-devel-static the main executable gets created -- You are receiving this mail because: You are on the CC list for the bug.

1 1