Your message dated Thu, 24 Aug 2023 13:49:03 +0200
with message-id <bdbf94e8-df4c-4938-8af4-7c84fc4f7...@debian.org>
and subject line Re: systemd: "reboot" fails to boot into the grub-menu
has caused the Debian Bug report #1025909,
regarding systemd: "reboot" fails to boot into the grub-menu
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1025909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 252.3-1
Severity: normal
X-Debbugs-Cc: zieg...@uni-freiburg.de
Dear Maintainer,
"reboot" fails to boot into the grub-menu, as well as the command
"systemctl reboot". The least kernel in the grub menu is booted
instead.
"systemctl reboot --boot-loader-menu=5" gives an error
A reboot 1.12.2022 (with versions 252.1-1) worked as expected, the
next boot 7.12.2022 (still with versions 252.1-1) showed the
incriminated behaviour. With versions 252.2-1 and 252.3-1 still no
boot into the grub menu.
I looks as if another package is responsible for this change.
But I cannot guess which.
-- Package-specific info:
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii libacl1 2.3.1-2
ii libaudit1 1:3.0.7-1.1+b2
ii libblkid1 2.38.1-4
ii libc6 2.36-6
ii libcap2 1:2.44-1
ii libcryptsetup12 2:2.6.0-2
ii libfdisk1 2.38.1-4
ii libgcrypt20 1.10.1-3
ii libkmod2 30+20220905-1
ii liblz4-1 1.9.4-1
ii liblzma5 5.2.9-0.0
ii libmount1 2.38.1-4
ii libseccomp2 2.5.4-1+b2
ii libselinux1 3.4-1+b3
ii libssl3 3.0.7-1
ii libsystemd-shared 252.3-1
ii libsystemd0 252.3-1
ii libzstd1 1.5.2+dfsg-1
ii mount 2.38.1-4
Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.14.4-1
ii systemd-timesyncd [time-daemon] 252.3-1
Versions of packages systemd suggests:
ii libfido2-1 1.12.0-2
ii libqrencode4 4.1.1-1
pn libtss2-esys-3.0.2-0 <none>
pn libtss2-mu0 <none>
pn libtss2-rc0 <none>
ii policykit-1 122-1
ii polkitd 122-1
pn systemd-boot <none>
pn systemd-container <none>
pn systemd-homed <none>
pn systemd-resolved <none>
pn systemd-userdbd <none>
Versions of packages systemd is related to:
ii dbus-user-session 1.14.4-1
pn dracut <none>
ii initramfs-tools 0.142
ii libnss-systemd 252.3-1
ii libpam-systemd 252.3-1
ii udev 252.2-2
-- Configuration Files:
/etc/systemd/networkd.conf changed:
[Network]
[DHCPv4]
<<<<<<< networkd.conf
[DHCPv6]
=======
[Login]
>>>>>>> logind.conf.dpkg-new
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 11 Dec 2022 20:51:42 +0100 Martin Ziegler
<zieg...@uni-freiburg.de> wrote:
Package: systemd
Version: 252.3-1
Severity: normal
X-Debbugs-Cc: zieg...@uni-freiburg.de
Dear Maintainer,
"reboot" fails to boot into the grub-menu, as well as the command
"systemctl reboot". The least kernel in the grub menu is booted
instead.
"systemctl reboot --boot-loader-menu=5" gives an error
A reboot 1.12.2022 (with versions 252.1-1) worked as expected, the
next boot 7.12.2022 (still with versions 252.1-1) showed the
incriminated behaviour. With versions 252.2-1 and 252.3-1 still no
boot into the grub menu.
I looks as if another package is responsible for this change.
But I cannot guess which.
--boot-loader-menu= only works for boot loaders that implement the "Boot
Loader Interface" which is documented at
https://systemd.io/BOOT_LOADER_INTERFACE/
Specifically
"
the systemctl reboot --boot-loader-entry=… and systemctl reboot
--boot-loader-menu=… commands rely on the LoaderFeatures ,
LoaderConfigTimeoutOneShot, LoaderEntries, LoaderEntryOneShot variables.
"
TTBOMK, grub does actually implement this interface.
systemd-boot does implement this interface, in case you want to make use
of this functionality.
I don't think there is anything actionable on the systemd side here,
thus closing the bug report here.
Feel free to raise this issue with grub, if you want to see support for
this interface there.
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
