[Bug 1234741] New: Only "systemd-boot" or "grub2-bls" are recognized (end of dup)
https://bugzilla.suse.com/show_bug.cgi?id=1234741 Bug ID: 1234741 Summary: Only "systemd-boot" or "grub2-bls" are recognized (end of dup) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs@suse.de Reporter: pj.opensuse@gmx.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, Tumbleweed snapshot 20241218 after zypper ref *and* zypper dup are passed......the following is displayed in konsole... %posttrans(dracut-pcr-signature-0.5+1-1.1.noarch) script output: Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized. %transfiletriggerin(sdbootutil-1+git20241217.5aeb4e9-1.1.x86_64) script output: Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized. warning: %transfiletriggerin(sdbootutil-1+git20241217.5aeb4e9-1.1.x86_64) scriptlet failed, exit status 1 Running post-transaction scripts .......................................................................................................[done] What is going on here? -Thanks -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234741 https://bugzilla.suse.com/show_bug.cgi?id=1234741#c2 --- Comment #2 from Paul Graff <pj.opensuse@gmx.com> --- (In reply to Thorsten Kukuk from comment #1)
sdbootutil only works with systemd-boot and grub2-BLS. No idea why that is installed on your system.
Hi, I believe the problem was due to me selecting Legacy boot via usb in order to envoke the openSUSE TUmbleweed installer. I was not choosing secure boot pmap in boot menu options. Would this make sense to you? -Thank you -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234741 https://bugzilla.suse.com/show_bug.cgi?id=1234741#c3 --- Comment #3 from Paul Graff <pj.opensuse@gmx.com> --- *err opensuse-secureboot -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234741 https://bugzilla.suse.com/show_bug.cgi?id=1234741#c4 --- Comment #4 from Paul Graff <pj.opensuse@gmx.com> --- Sorry to disturb again, sdbootutil was installed because of SELinux. -Thank you -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1234741 https://bugzilla.suse.com/show_bug.cgi?id=1234741#c8 Andrei Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aplanas@suse.com, | |arvidjaar@gmail.com --- Comment #8 from Andrei Borzenkov <arvidjaar@gmail.com> --- (In reply to Thorsten Kukuk from comment #1)
sdbootutil only works with systemd-boot and grub2-BLS.
This is packaging bug. The trigger installed by sdbootutil should check for the currently configured bootloader and avoid calling "sdbootutil update" if bootloader is not managed by sdbootutil.
No idea why that is installed on your system.
It does not matter. I may have installed it just to look at it. The mere presence of this package should not cause errors when unrelated packages are updated. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com