January 2025 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1228416] New: Aeon RC3 (20240726) automatically unlocks partition even if kernel cmdline is modified
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228416 Bug ID: 1228416 Summary: Aeon RC3 (20240726) automatically unlocks partition even if kernel cmdline is modified Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: philipp(a)nhus.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0 Build Identifier: I've installed Aeon RC3 (Aeon-Installer.x86_64-0.1.0-Snapshot20240726.raw) on a ThinkPad T14s AMD Gen1. The installation finished without any errors and Aeon was installed in "Default" mode. After booting the system, I wanted to see if it actually prevents booting if the kernel cmdline is modified. So, I hit "e" in the systemd-boot menu, changed the cmdline, and the system booted without asking for the recovery key, which I did not expect. I then checked the LUKS header with "cryptsetup luksDump <device>" which reported the following: tpm2-hash-pcrs: 7 tpm2-pcrlock: false But pcrlock has to be enabled to prevent tampering of boot config on Aeon, correct? I then manually re-enrolled with systemd-cryptenroll <device> --wipe-slot 2 systemd-cryptenroll <device> --tpm2-device auto Afterwards, luksDump reports this: tpm2-hash-pcrs: <empty> tpm2-pcrlock: true which is what I would expect. If I now try to modify the cmdline on boot, it correctly asks for the recovery key. I've reinstalled 3 times, always with the same behavior. I don't have a tik.log on the stick after installation, is it not saved if the installation finished successfully? Reproducible: Always Steps to Reproduce: 1. Install Aeon-Installer.x86_64-0.1.0-Snapshot20240726 from USB stick 2. Boot the system, set up initial user account & reboot 3. In systemd-boot, press "e" to edit the kernel cmdline, remove "quiet" from the cmdline and boot Actual Results: System automatically unlocks partition without asking for recovery code. Expected Results: System refuses automatic unlocking of partition, because kernel cmdline has changed. It asks for the recovery code to unlock. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1230653] New: `transactional-update dup` snapshot boot failure, dracut-initqueue scripts 90-crypt.sh
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1230653 Bug ID: 1230653 Summary: `transactional-update dup` snapshot boot failure, dracut-initqueue scripts 90-crypt.sh Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: HP OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Transactional Update Assignee: rbrown(a)suse.com Reporter: toms.b.gm(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0 Build Identifier: Can't boot latest snapshot after `transactional-update dup` when updating slightly outdated packages (kernel 6.10.5-1) to latest packages (kernel 6.10.9-1) on default TPM FDE installation. Reproducible: Didn't try Steps to Reproduce: 1. Install and use OpenSUSE Aeon with slightly outdated packages (kernel 6.10.5-1), default TPM FDE installation 2. Update packages to latest version (kernel 6.10.9-1) via `sudo transactional-update dup` 3. Reboot system via `sudo reboot` Actual Results: Black screen for 2 minutes before being spammed the following: dracut-initqueue[546]: Warning: dracut-initqueue: starting timeout scripts dracut-initqueue[546]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: dracut-initqueue[546]: Warning: /lib/dracut/hooks/initqueue/finished/90-crypt.sh: "[ -e /dev/disk/by-id/dm-uuid-CRYPT_LUKS?-*-1b0e3ea6054943698ceef6214d27717c*-* ] || exit 1" dracut-initqueue[546]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fdisk\x2fby-uuid\x2ffba03bc2-e554-4abf-9864-208c541d469c.sh: "[ -e "/dev/disk/by-uuid/fba03bc2-e554-4abf-9864-208c541d469c" ]" After a minute of this, system seems to restart and repeat this. Expected Results: I expected it to fully boot to GDM login. Output from `sudo sdbootutil -vv --ask-pin update-predictions`: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy Found container virtualization none. Failed to check file system type of "/efi": No such file or directory File system "/boot" is not a FAT EFI System Partition (ESP) file system. Using EFI System Partition at /boot/efi. Directory "/boot" is not the root of the file system. Didn't find an XBOOTLDR partition, using the ESP as $BOOT. Reading EFI variable /sys/firmware/efi/efivars/LoaderEntries-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f. Reading EFI variable /sys/firmware/efi/efivars/LoaderEntryOneShot-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f. open("/sys/firmware/efi/efivars/LoaderEntryOneShot-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f") failed: No such file or directory Reading EFI variable /sys/firmware/efi/efivars/LoaderEntryDefault-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f. Reading EFI variable /sys/firmware/efi/efivars/LoaderEntrySelected-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f. Found default: id "aeon-6.10.9-1-default-22.conf" is matched by LoaderEntryDefault TPM PC Client Platform Firmware Profile: family 2.0, revision 1.5 Found StartupLocality event: 3 Ignoring device path element type=0x02 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x03 subtype=0x17 Ignoring device path element type=0x04 subtype=0x01 Ignoring device path element type=0x02 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x03 subtype=0x17 Ignoring device path element type=0x04 subtype=0x01 Loaded 'libtss2-esys.so.0' via dlopen() Loaded 'libtss2-rc.so.0' via dlopen() Loaded 'libtss2-mu.so.0' via dlopen() Using TPM2 TCTI driver 'device' with device '/dev/tpmrm0'. Loaded 'libtss2-tcti-device.so.0' via dlopen() Loaded TCTI module 'tcti-device' (TCTI module for communication with Linux kernel interface.) [Version 2] TPM successfully started up. Getting TPM2 capability 0x0000 property 0x0001 count 127. Getting TPM2 capability 0x0002 property 0x011f count 256. Getting TPM2 capability 0x0008 property 0x0000 count 508. Getting TPM2 capability 0x0005 property 0x0000 count 1. Reading PCR selection: [sha256(0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(0+1+2+3+4+5+6+7)] PCR value: 0:sha256=7ffe0181383f43d8d3d105a1feab73f5fd93048e1116808c563387e6a227faaf PCR value: 1:sha256=7bb778fcab821bf1f7abcffab3b5651909b68a9dbaffe1621bd8179634d34d78 PCR value: 2:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 3:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 4:sha256=aa4cb0dee0c0090784a3a14c8bd820effca45348739f3214acb9dc0cb00f681e PCR value: 5:sha256=e5dd9b9e539ef55f889c79d0859ca1f6e05d2699929e25ec9d019e78eb3e5b30 PCR value: 6:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 7:sha256=fea1985302857b5a720ffa310e6d301b71d1097454dfce43a9635ee54b172353 Reading PCR selection: [sha256(8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(8+9+10+11+12+13+14+15)] PCR value: 8:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 9:sha256=93e4a5226b16f772db5c32c5f6a9db8dece27e6dce6b5353c1025171d5ffe638 PCR value: 10:sha256=2067d93034a8f0fcf26094fab932f5f9bd9410d3e9d012f264022a7ccb01f537 PCR value: 11:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 12:sha256=d50d6e4b5a2cf9dfe0a2a379609fc4c349db32ab3aaa2ebcc6382ea10d778f31 PCR value: 13:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 14:sha256=84344d7c9bd000dc7918460efc682a4040cfebdef7c6f1742b717e833df6b2bc PCR value: 15:sha256=0000000000000000000000000000000000000000000000000000000000000000 Reading PCR selection: [sha256(16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(16+17+18+19+20+21+22+23)] PCR value: 16:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 17:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 18:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 19:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 20:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 21:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 22:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 23:sha256=0000000000000000000000000000000000000000000000000000000000000000 /var/lib/pcrlock.d/250-firmware-code-early.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/550-firmware-code-late.pcrlock.d/generated.pcrlock written. TPM PC Client Platform Firmware Profile: family 2.0, revision 1.5 Found StartupLocality event: 3 Ignoring device path element type=0x02 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x03 subtype=0x17 Ignoring device path element type=0x04 subtype=0x01 Ignoring device path element type=0x02 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x03 subtype=0x17 Ignoring device path element type=0x04 subtype=0x01 Loaded 'libtss2-esys.so.0' via dlopen() Loaded 'libtss2-rc.so.0' via dlopen() Loaded 'libtss2-mu.so.0' via dlopen() Using TPM2 TCTI driver 'device' with device '/dev/tpmrm0'. Loaded 'libtss2-tcti-device.so.0' via dlopen() Loaded TCTI module 'tcti-device' (TCTI module for communication with Linux kernel interface.) [Version 2] TPM successfully started up. Getting TPM2 capability 0x0000 property 0x0001 count 127. Getting TPM2 capability 0x0002 property 0x011f count 256. Getting TPM2 capability 0x0008 property 0x0000 count 508. Getting TPM2 capability 0x0005 property 0x0000 count 1. Reading PCR selection: [sha256(0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(0+1+2+3+4+5+6+7)] PCR value: 0:sha256=7ffe0181383f43d8d3d105a1feab73f5fd93048e1116808c563387e6a227faaf PCR value: 1:sha256=7bb778fcab821bf1f7abcffab3b5651909b68a9dbaffe1621bd8179634d34d78 PCR value: 2:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 3:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 4:sha256=aa4cb0dee0c0090784a3a14c8bd820effca45348739f3214acb9dc0cb00f681e PCR value: 5:sha256=e5dd9b9e539ef55f889c79d0859ca1f6e05d2699929e25ec9d019e78eb3e5b30 PCR value: 6:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 7:sha256=fea1985302857b5a720ffa310e6d301b71d1097454dfce43a9635ee54b172353 Reading PCR selection: [sha256(8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(8+9+10+11+12+13+14+15)] PCR value: 8:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 9:sha256=93e4a5226b16f772db5c32c5f6a9db8dece27e6dce6b5353c1025171d5ffe638 PCR value: 10:sha256=2067d93034a8f0fcf26094fab932f5f9bd9410d3e9d012f264022a7ccb01f537 PCR value: 11:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 12:sha256=d50d6e4b5a2cf9dfe0a2a379609fc4c349db32ab3aaa2ebcc6382ea10d778f31 PCR value: 13:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 14:sha256=84344d7c9bd000dc7918460efc682a4040cfebdef7c6f1742b717e833df6b2bc PCR value: 15:sha256=0000000000000000000000000000000000000000000000000000000000000000 Reading PCR selection: [sha256(16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(16+17+18+19+20+21+22+23)] PCR value: 16:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 17:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 18:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 19:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 20:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 21:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 22:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 23:sha256=0000000000000000000000000000000000000000000000000000000000000000 /var/lib/pcrlock.d/250-firmware-config-early.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/550-firmware-config-late.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/600-gpt.pcrlock.d/generated.pcrlock written. Hashing 216 @ 0 → 216 Hashing 76 @ 220 → 296 Hashing 720 @ 304 → 1024 Hashing 121856 @ 1024 → 122880 Hashing 394240 @ 122880 → 517120 Hashing 512 @ 517120 → 517632 Hashing 512 @ 517632 → 518144 Hashing 512 @ 518144 → 518656 Hashing 187392 @ 518656 → 706048 Hashing 7680 @ 706048 → 713728 Hashing 512 @ 713728 → 714240 Hashing 112128 @ 714240 → 826368 Hashing 512 @ 826368 → 826880 Hashing 127112 @ 826880 → 953992 Hashing 216 @ 0 → 216 Hashing 76 @ 220 → 296 Hashing 720 @ 304 → 1024 Hashing 121856 @ 1024 → 122880 Hashing 394240 @ 122880 → 517120 Hashing 512 @ 517120 → 517632 Hashing 512 @ 517632 → 518144 Hashing 512 @ 518144 → 518656 Hashing 187392 @ 518656 → 706048 Hashing 7680 @ 706048 → 713728 Hashing 512 @ 713728 → 714240 Hashing 112128 @ 714240 → 826368 Hashing 512 @ 826368 → 826880 Hashing 127112 @ 826880 → 953992 Hashing 216 @ 0 → 216 Hashing 76 @ 220 → 296 Hashing 720 @ 304 → 1024 Hashing 121856 @ 1024 → 122880 Hashing 394240 @ 122880 → 517120 Hashing 512 @ 517120 → 517632 Hashing 512 @ 517632 → 518144 Hashing 512 @ 518144 → 518656 Hashing 187392 @ 518656 → 706048 Hashing 7680 @ 706048 → 713728 Hashing 512 @ 713728 → 714240 Hashing 112128 @ 714240 → 826368 Hashing 512 @ 826368 → 826880 Hashing 127112 @ 826880 → 953992 Hashing 216 @ 0 → 216 Hashing 76 @ 220 → 296 Hashing 720 @ 304 → 1024 Hashing 121856 @ 1024 → 122880 Hashing 394240 @ 122880 → 517120 Hashing 512 @ 517120 → 517632 Hashing 512 @ 517632 → 518144 Hashing 512 @ 518144 → 518656 Hashing 187392 @ 518656 → 706048 Hashing 7680 @ 706048 → 713728 Hashing 512 @ 713728 → 714240 Hashing 112128 @ 714240 → 826368 Hashing 512 @ 826368 → 826880 Hashing 127112 @ 826880 → 953992 /var/lib/pcrlock.d/630-shim-efi-application.pcrlock.d/generated.pcrlock written. Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 784 @ 240 → 1024 Hashing 75264 @ 1024 → 76288 Hashing 20480 @ 76288 → 96768 Hashing 512 @ 96768 → 97280 Hashing 512 @ 97280 → 97792 Hashing 512 @ 97792 → 98304 Hashing 512 @ 98304 → 98816 Hashing 512 @ 98816 → 99328 Hashing 0 @ 99328 → 99328 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 784 @ 240 → 1024 Hashing 75264 @ 1024 → 76288 Hashing 20480 @ 76288 → 96768 Hashing 512 @ 96768 → 97280 Hashing 512 @ 97280 → 97792 Hashing 512 @ 97792 → 98304 Hashing 512 @ 98304 → 98816 Hashing 512 @ 98816 → 99328 Hashing 0 @ 99328 → 99328 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 784 @ 240 → 1024 Hashing 75264 @ 1024 → 76288 Hashing 20480 @ 76288 → 96768 Hashing 512 @ 96768 → 97280 Hashing 512 @ 97280 → 97792 Hashing 512 @ 97792 → 98304 Hashing 512 @ 98304 → 98816 Hashing 512 @ 98816 → 99328 Hashing 0 @ 99328 → 99328 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 784 @ 240 → 1024 Hashing 75264 @ 1024 → 76288 Hashing 20480 @ 76288 → 96768 Hashing 512 @ 96768 → 97280 Hashing 512 @ 97280 → 97792 Hashing 512 @ 97792 → 98304 Hashing 512 @ 98304 → 98816 Hashing 512 @ 98816 → 99328 Hashing 0 @ 99328 → 99328 /var/lib/pcrlock.d/640-boot-loader-efi-application.pcrlock.d/generated.pcrlock written. /var/lib/pcrlock.d/641-sdboot-loader-conf.pcrlock written. Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14745600 @ 20480 → 14766080 Hashing 4608 @ 14766080 → 14770688 Hashing 0 @ 14770688 → 14770688 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14745600 @ 20480 → 14766080 Hashing 4608 @ 14766080 → 14770688 Hashing 0 @ 14770688 → 14770688 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14745600 @ 20480 → 14766080 Hashing 4608 @ 14766080 → 14770688 Hashing 0 @ 14770688 → 14770688 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14745600 @ 20480 → 14766080 Hashing 4608 @ 14766080 → 14770688 Hashing 0 @ 14770688 → 14770688 /var/lib/pcrlock.d/650-kernel-efi-application.pcrlock.d/linux-1.pcrlock written. Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14860288 @ 20480 → 14880768 Hashing 4608 @ 14880768 → 14885376 Hashing 0 @ 14885376 → 14885376 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14860288 @ 20480 → 14880768 Hashing 4608 @ 14880768 → 14885376 Hashing 0 @ 14885376 → 14885376 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14860288 @ 20480 → 14880768 Hashing 4608 @ 14880768 → 14885376 Hashing 0 @ 14885376 → 14885376 Hashing 152 @ 0 → 152 Hashing 76 @ 156 → 232 Hashing 3856 @ 240 → 4096 Hashing 12288 @ 4096 → 16384 Hashing 4096 @ 16384 → 20480 Hashing 14860288 @ 20480 → 14880768 Hashing 4608 @ 14880768 → 14885376 Hashing 0 @ 14885376 → 14885376 /var/lib/pcrlock.d/650-kernel-efi-application.pcrlock.d/linux-2.pcrlock written. /tmp/sdbootutil.9dnZ5i/cmdline.pcrlock written. /var/lib/pcrlock.d/710-kernel-cmdline-boot-loader.pcrlock.d/cmdline-1.pcrlock written. /tmp/sdbootutil.9dnZ5i/cmdline.pcrlock written. /var/lib/pcrlock.d/710-kernel-cmdline-boot-loader.pcrlock.d/cmdline-2.pcrlock written. /tmp/sdbootutil.9dnZ5i/cmdline.pcrlock written. /var/lib/pcrlock.d/710-kernel-cmdline-boot-loader.pcrlock.d/cmdline-3.pcrlock written. Recovery PIN: TPM PC Client Platform Firmware Profile: family 2.0, revision 1.5 Found StartupLocality event: 3 Ignoring device path element type=0x02 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x03 subtype=0x17 Ignoring device path element type=0x04 subtype=0x01 Ignoring device path element type=0x02 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x01 subtype=0x01 Ignoring device path element type=0x03 subtype=0x17 Ignoring device path element type=0x04 subtype=0x01 Loaded 'libtss2-esys.so.0' via dlopen() Loaded 'libtss2-rc.so.0' via dlopen() Loaded 'libtss2-mu.so.0' via dlopen() Using TPM2 TCTI driver 'device' with device '/dev/tpmrm0'. Loaded 'libtss2-tcti-device.so.0' via dlopen() Loaded TCTI module 'tcti-device' (TCTI module for communication with Linux kernel interface.) [Version 2] TPM successfully started up. Getting TPM2 capability 0x0000 property 0x0001 count 127. Getting TPM2 capability 0x0002 property 0x011f count 256. Getting TPM2 capability 0x0008 property 0x0000 count 508. Getting TPM2 capability 0x0005 property 0x0000 count 1. Reading PCR selection: [sha256(0+1+2+3+4+5+6+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(0+1+2+3+4+5+6+7)] PCR value: 0:sha256=7ffe0181383f43d8d3d105a1feab73f5fd93048e1116808c563387e6a227faaf PCR value: 1:sha256=7bb778fcab821bf1f7abcffab3b5651909b68a9dbaffe1621bd8179634d34d78 PCR value: 2:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 3:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 4:sha256=aa4cb0dee0c0090784a3a14c8bd820effca45348739f3214acb9dc0cb00f681e PCR value: 5:sha256=e5dd9b9e539ef55f889c79d0859ca1f6e05d2699929e25ec9d019e78eb3e5b30 PCR value: 6:sha256=3d458cfe55cc03ea1f443f1562beec8df51c75e14a9fcf9a7234a13f198e7969 PCR value: 7:sha256=fea1985302857b5a720ffa310e6d301b71d1097454dfce43a9635ee54b172353 Reading PCR selection: [sha256(8+9+10+11+12+13+14+15+16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(8+9+10+11+12+13+14+15)] PCR value: 8:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 9:sha256=93e4a5226b16f772db5c32c5f6a9db8dece27e6dce6b5353c1025171d5ffe638 PCR value: 10:sha256=2067d93034a8f0fcf26094fab932f5f9bd9410d3e9d012f264022a7ccb01f537 PCR value: 11:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 12:sha256=d50d6e4b5a2cf9dfe0a2a379609fc4c349db32ab3aaa2ebcc6382ea10d778f31 PCR value: 13:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 14:sha256=84344d7c9bd000dc7918460efc682a4040cfebdef7c6f1742b717e833df6b2bc PCR value: 15:sha256=0000000000000000000000000000000000000000000000000000000000000000 Reading PCR selection: [sha256(16+17+18+19+20+21+22+23)] Read PCR selection: [sha256(16+17+18+19+20+21+22+23)] PCR value: 16:sha256=0000000000000000000000000000000000000000000000000000000000000000 PCR value: 17:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 18:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 19:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 20:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 21:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 22:sha256=ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff PCR value: 23:sha256=0000000000000000000000000000000000000000000000000000000000000000 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. 'content_type' missing from TPM measurement log file entry, ignoring. Couldn't find component '710-kernel-cmdline-boot-loader' in event log. Couldn't find component '750-enter-initrd' in event log. Didn't find component '800-leave-initrd' in event log, assuming system hasn't reached it yet. Didn't find component '850-sysinit' in event log, assuming system hasn't reached it yet. Didn't find component '900-ready' in event log, assuming system hasn't reached it yet. Skipped 2 components after location '940-' (950-shutdown, 990-final). Unable to recognize 2 components in event log. Event log record 34 (PCR 5, "GPT: disk a8dbca6f-77a6-485c-8c67-b653758a8928") not matching any component. Event log record 30 (PCR 7, "Authority: SbatLevel-605dab50-e046-4300-abb6-3dd810dd8b23") not matching any component. Event log record 36 (PCR 12, "String: initrd=\aeon\6.10.5-1-default\initrd-47ee25c3cff38e8c62d1fabbb864b2d002eaee0a quiet loglevel=2 systemd.show_status=no console=ttyS0,115200 console=tty0 vt.global_cursor_default=0 ignition.platform.id=metal security=selinux selinux=1 root=UUID=fba03bc2-e554-4abf-9864-208c541d469c rootflags=subvol=(a)/.snapshots/19/snapshot systemd.machine_id=cbe9f0d83488464891587d8f07c2c12b") not matching any component. Event log record 28 (PCR 14, "Raw: MokList\000") not matching any component. PCR 0 (platform-code) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCR 4 (boot-loader-code) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCR 5 (boot-loader-config) event log contains unrecognized measurements. Removing from set of PCRs. PCR 7 (secure-boot-policy) event log contains unrecognized measurements. Removing from set of PCRs. PCR 9 (kernel-initrd) matches event log and fully consists of recognized measurements. Including in set of PCRs. PCRs dropped from protection mask: 5 (boot-loader-config), 7 (secure-boot-policy) PCRs in protection mask: 0 (platform-code), 4 (boot-loader-code), 9 (kernel-initrd) Added prediction result 1 for PCR 0 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 2 for PCR 0 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@600-0xffffffff:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 1 for PCR 4 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 2 for PCR 4 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-2:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 3 for PCR 4 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@600-0xffffffff:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 4 for PCR 4 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@600-0xffffffff:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-2:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 1 for PCR 9 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-1:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 2 for PCR 9 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-2:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Added prediction result 3 for PCR 9 (path: 240-secureboot-policy@generated:250-firmware-code-early@generated:250-firmware-config-early@generated:350-action-efi-application:400-secureboot-separator@300-0x00000000:500-separator@300-0x00000000:550-firmware-code-late@generated:550-firmware-config-late@generated:600-gpt@generated:630-shim-efi-application@generated:640-boot-loader-efi-application@generated:641-sdboot-loader-conf:650-kernel-efi-application@linux-1:700-action-efi-exit-boot-services@300-present:710-kernel-cmdline-boot-loader@cmdline-1:710-kernel-cmdline-initrd-entry@cmdline-initrd-3:750-enter-initrd:800-leave-initrd:850-sysinit:900-ready) Predicted future PCRs in 1.502ms. [ { "pcr" : 0, "values" : [ "7ffe0181383f43d8d3d105a1feab73f5fd93048e1116808c563387e6a227faaf", "1b0debb8bcf768c08aa02b476fb113e98975989afedcf021bc400cc1f91d39ca" ] }, { "pcr" : 4, "values" : [ "aa4cb0dee0c0090784a3a14c8bd820effca45348739f3214acb9dc0cb00f681e", "1594d884537c303190e34ab6dbd6a51ad2ef51e0ab6da517e72d509db3765dda", "df999a2508a52c3f455dda450d74bb6a09c441dc7af2f0d77d1bf3957d46f93c", "dac23ce7ca141dab270aae4b12ddbf62500e3bafcc6901af5a43d2c516ddadf3" ] }, { "pcr" : 9, "values" : [ "3d49d1580970ec40bcd1c76975c245a31547c1cd61008230f835d692b42029d5", "93e4a5226b16f772db5c32c5f6a9db8dece27e6dce6b5353c1025171d5ffe638", "37a8d8d1b6d4512401f87921577818e82fc7b2aa6981daceab1e612c9386bbed" ] } ] Prediction is identical to current policy, skipping update. NVIndex policy created -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1229084] New: gdm does not recognize the keyboard layout
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1229084 Bug ID: 1229084 Summary: gdm does not recognize the keyboard layout Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: hotel-brot.0z(a)icloud.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:129.0) Gecko/20100101 Firefox/129.0 Build Identifier: Logs: I do not know what kind of logs I could give you, but if you need some, you can ask me and I will do my best. Reproducible: Always Steps to Reproduce: 1.Choose a non-US keyboard layout in gnome-control-center 2.Log out / reboot 3.Notice that the keyboard layout is not recognized. Actual Results: GDM is set to the US keyboard layout. Expected Results: GDM recognizes system settings Workaround: 'localectl set-keymap $layout' -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1229060] New: Cannot access console root account is locked
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1229060 Bug ID: 1229060 Summary: Cannot access console root account is locked Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: ab.serv(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When I attempted to install Aeon I had this prompt appear during the second boot of the installer, after it had entered maintenance mode during the first boot (issue #1229058). This error occurred when I installed Aeon on a cheap 32gb Sandisk Cruzer, but went away (or rather, went to #1229058) when I used a nicer 64gb thumbdrive. The Aeon installer image was downloaded yesterday (August 11 2024) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1229058] New: Installation media & first boot enters maintenance mode
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1229058 Bug ID: 1229058 Summary: Installation media & first boot enters maintenance mode Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: ab.serv(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876619 --> https://bugzilla.suse.com/attachment.cgi?id=876619&action=edit journalctl --no-pager output during maintenance mode When using the Aeon installation media, or booting Aeon for the first time, the system enters maintenance mode. I read rdsosreport.txt and I vaguely remember it said something about a block device being mounted twice, so I'm hoping it'll be a simple fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1229049] New: Installation Aeon RC3 not possible
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1229049 Bug ID: 1229049 Summary: Installation Aeon RC3 not possible 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: leoh(a)duck.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876613 --> https://bugzilla.suse.com/attachment.cgi?id=876613&action=edit installation tik.log usr/sbin/blockdev --rereadpt /dev/disk/by-id/ata-TOSHIBA_MQ01ABD050_73RUC34ET</tt -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1228871] New: Aeon installer crashes if existing LUKS partition is decrypted
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228871 Bug ID: 1228871 Summary: Aeon installer crashes if existing LUKS partition is decrypted Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: vincent.conus(a)pm.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:128.0) Gecko/20100101 Firefox/128.0 Build Identifier: Upon installing the Aeon Desktop on my Tuxedo Pulse 15 Gen2 laptop (Ryzen 7 5700U), the installer crashed after the disk selection step. Since I was installing Aeon in place of an existing Tumbleweed system on one of the internal NVMe SSD, I was prompted to give the password for the existing LUKS partition. I inadvertently entered it, and after working for a little while the installer crashed. The tik.log file will be provided. Eventually, I restarted the installer, proceed to NOT give the password for the existing system and the installation went smoothly. Reproducible: Didn't try Steps to Reproduce: 1. Run the installer for Aeon Desktop. 2. Select a disk as the target for installation with an existing LUKS partition. 3. Enter the password for the partition instead of ignoring it. Actual Results: The installer returned an error message and prompted me to submit a bug report and reboot. Expected Results: Normal install; which happened eventually! See tik.log -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1228659] New: Snapshot 20240730 - unbootable after transactional-update dup
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228659 Bug ID: 1228659 Summary: Snapshot 20240730 - unbootable after transactional-update dup Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Transactional Update Assignee: aplanas(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- All Aeon installations (and I suspect all MicroOS systemd-boot installations) are failing to boot after a transactional-update dup to the latest snapshot I suspect the cause is the misbehaviour of the sdbootutil plugin reported during the transactional-update Example logs below: (25/41) Installing: kernel-default-6.10.2-1.1.x86_64 [... Error: No ESP detected. Legacy system? ................................................................................................... Error: No ESP detected. Legacy system? Error: No ESP detected. Legacy system? dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.10.2-1-default 6.10.2-1-default dracut[I]: Module 'systemd-networkd' will not be installed, because command 'networkctl' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd' could not be found! dracut[I]: Module 'systemd-networkd' will not be installed, because command '/usr/lib/systemd/systemd-networkd-wait-online' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: 35network-legacy: Could not find any command of 'dhclient wicked'! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'pcsc' will not be installed, because command 'pcscd' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut[I]: 95nfs: Could not find any command of 'rpcbind portmap'! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command 'portablectl' could not be found! dracut[I]: Module 'systemd-portabled' will not be installed, because command '/usr/lib/systemd/systemd-portabled' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command 'resolvectl' could not be found! dracut[I]: Module 'systemd-resolved' will not be installed, because command '/usr/lib/systemd/systemd-resolved' could not be found! dracut[I]: Module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut[I]: Module 'rngd' will not be installed, because command 'rngd' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmanctl' could not be found! dracut[I]: Module 'connman' will not be installed, because command 'connmand-wait-online' could not be found! dracut[I]: 35network-legacy: Could not find any command of 'dhclient wicked'! dracut[I]: Module 'dmraid' will not be installed, because command 'dmraid' could not be found! dracut[I]: Module 'pcsc' will not be installed, because command 'pcscd' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsiadm' could not be found! dracut[I]: Module 'iscsi' will not be installed, because command 'iscsid' could not be found! dracut[I]: 95nfs: Could not find any command of 'rpcbind portmap'! dracut[I]: Module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut[I]: Module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut[I]: memstrack is not available dracut[I]: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut[I]: Module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut[I]: Module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut[I]: *** Including module: systemd *** dracut[I]: *** Including module: systemd-initrd *** dracut[I]: *** Including module: i18n *** dracut[I]: No KEYMAP configured. dracut[I]: *** Including module: drm *** dracut[I]: *** Including module: health-checker *** dracut-install: ERROR: installing 'grub2-editenv' dracut[E]: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.kGpiZ2/initramfs -a date btrfs awk grub2-editenv dracut[I]: *** Including module: pcr-signature *** dracut[I]: *** Including module: transactional-update *** dracut[I]: *** Including module: btrfs *** dracut[I]: *** Including module: kernel-modules *** udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory dracut[I]: *** Including module: kernel-modules-extra *** dracut[I]: *** Including module: rootfs-block *** dracut[I]: *** Including module: suse-btrfs *** dracut[I]: *** Including module: suse-xfs *** dracut[I]: *** Including module: terminfo *** dracut[I]: *** Including module: udev-rules *** udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory dracut[E]: Failed to detect udev version! dracut[I]: *** Including module: dracut-systemd *** dracut[I]: *** Including module: ostree *** dracut[I]: *** Including module: selinux-microos *** dracut[I]: *** Including module: usrmount *** dracut[I]: *** Including module: base *** dracut[I]: *** Including module: fs-lib *** dracut[I]: *** Including module: shutdown *** dracut[I]: *** Including module: suse *** dracut[I]: *** Including module: suse-initrd *** dracut[I]: *** Including modules done *** dracut[I]: *** Installing kernel module dependencies *** dracut[I]: *** Installing kernel module dependencies done *** dracut[I]: *** Resolving executable dependencies *** dracut[I]: *** Resolving executable dependencies done *** dracut[I]: *** Hardlinking files *** dracut[I]: *** Hardlinking files done *** dracut[I]: *** Generating early-microcode cpio image *** dracut[I]: *** Store current command line parameters *** dracut[I]: Stored kernel commandline: dracut[I]: rd.driver.pre=btrfs dracut[I]: rd.driver.pre=overlay dracut[I]: root=UUID=42fc02eb-e038-424f-b5a5-aed45173338d rootfstype=btrfs rootflags=rw,relatime,seclabel,compress=zstd:1,ssd,discard=async,space_cache=v2,subvolid=403,subvol=/@/.snapshots/98/snapshot,subvol=@/.snapshots/98/snapshot dracut[I]: *** Stripping files *** dracut[I]: *** Stripping files done *** dracut[I]: *** Creating image file '/boot/initrd-6.10.2-1-default' *** dracut[I]: *** Creating initramfs image file '/boot/initrd-6.10.2-1-default' done *** /usr/lib/bootloader/bootloader_entry: line 117: /etc/sysconfig/bootloader: No such file or directory CA enrolled. Skip /etc/uefi/certs/1F673297.crt Error: No ESP detected. Legacy system? ... Error: No ESP detected. Legacy system? Error: No ESP detected. Legacy system? /usr/lib/bootloader/bootloader_entry: line 117: /etc/sysconfig/bootloader: No such file or directory done] -- You are receiving this mail because: You are on the CC list for the bug.

1 30

[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 1235028] New: Opening a new Writer document creates a tiny window at the upper left of the screen
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1235028 Bug ID: 1235028 Summary: Opening a new Writer document creates a tiny window at the upper left of the screen Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 879387 --> https://bugzilla.suse.com/attachment.cgi?id=879387&action=edit Screenshot showing a new Writer instance on top of an existing Writer When opening a new Writer document (either by pressing Ctrl+N, or using the menu) the new Writer windows is so tiny that you almost miss it: It's in the upper left of the screen (see attachment and the faint red arrow pointing at it). -- You are receiving this mail because: You are on the CC list for the bug.

1 1