Public bug reported:
friendly-recovery 0.2.42build1 (Ubuntu 26.04, and the same code in the
development release)
On a system booted with more than one console= kernel argument, recovery
mode is only present on one console.
When booted into recovery mode (with "recovery" as a kernel arg) and two
consoles, kernel messages appear on both consoles as usual, then stop.
On the first console the recovery menu appears normally, but on others
no recovery menu appears.
The recovery menu should be reachable from whichever console the user is
monitoring.
The root cause is that friendly-recovery.service starts the menu with
StandardInput=tty-force and does not set TTYPath. systemd's TTYPath
defaults to /dev/console, and when several console= arguments are given
the kernel resolves /dev/console to only one of them.
This can be reproduced in a QEMU/KVM VM on an Ubuntu 26.04 cloud image
booted with:
recovery console=tty0 console=ttyS0,115200
The menu appears on ttyS0. On tty0 the boot output stopped and a bare
cursor remains, with no menu.
This was also initially reported and reproduced on Jetson platforms.
I have a fix for this and I will link the merge proposal.
** Affects: friendly-recovery (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
friendly-recovery 0.2.42build1 (Ubuntu 26.04, and the same code in the
development release)
On a system booted with more than one console= kernel argument, recovery
mode is only present on one console.
- When booted into recovery mode (with "recovery" as a kernel arg) and two
consoles, kernel messages
- appear on both consoles as usual, then stop. On the first console the
recovery menu
- appears normally, but on others no recovery menu appears.
+ When booted into recovery mode (with "recovery" as a kernel arg) and two
+ consoles, kernel messages appear on both consoles as usual, then stop.
+ On the first console the recovery menu appears normally, but on others
+ no recovery menu appears.
- The recovery menu should be reachable from whichever console
- the user is monitoring.
+ The recovery menu should be reachable from whichever console the user is
+ monitoring.
- The root cause is that friendly-recovery.service starts the menu with
StandardInput=tty-force
- and does not set TTYPath. systemd's TTYPath defaults to /dev/console, and when
- several console= arguments are given the kernel resolves /dev/console to only
- one of them.
+ The root cause is that friendly-recovery.service starts the menu with
+ StandardInput=tty-force and does not set TTYPath. systemd's TTYPath
+ defaults to /dev/console, and when several console= arguments are given
+ the kernel resolves /dev/console to only one of them.
This can be reproduced in a QEMU/KVM VM on an Ubuntu 26.04 cloud image
booted with:
- recovery console=tty0 console=ttyS0,115200
+ recovery console=tty0 console=ttyS0,115200
- The menu appears on ttyS0. On tty0 the boot output stopped and a bare cursor
- remains, with no menu.
+ The menu appears on ttyS0. On tty0 the boot output stopped and a bare
+ cursor remains, with no menu.
This was also initially reported and reproduced on Jetson platforms.
I have a fix for this and I will link the merge proposal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2166120
Title:
recovery menu is unreachable on all but one console when multiple
console= are set
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/2166120/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
