[Bug 2127780] [NEW] [Ubuntu 25.10 Questing] Errors shown in every text session when piboot is not enabled

[fprietog]

Public bug reported:

Ubuntu 25.10 Questing for Raspberry Pi. These errors are shown in every
text session when piboot is not enabled:

cat: /boot/firmware/current/state: No such file or directory (os error 2)
piboot is in an invalid or unexpected state:
Please file an issue: ubuntu-bug flash-kernel
run-parts: /etc/update-motd.d/90-piboot-try exited with return code 2

"/etc/update-motd.d/90-piboot-try" runs the command "/usr/sbin/piboot-
try --status" that don't have in account the possibility of having
piboot disabled so as file "/boot/firmware/current/state" just doesn't
exists it's mistaken with a piboot invalid/unexpected state.

I suggest a change in command piboot-try or in "/etc/update-
motd.d/90-piboot-try" to first test if piboot is enabled to continue
checking.

** Affects: flash-kernel (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  Ubuntu 25.10 Questing for Raspberry Pi. These errors are shown in every
  text session when piboot is not enabled:
  
  cat: /boot/firmware/current/state: No such file or directory (os error 2)
- piboot is in an invalid or unexpected state: 
+ piboot is in an invalid or unexpected state:
  Please file an issue: ubuntu-bug flash-kernel
  run-parts: /etc/update-motd.d/90-piboot-try exited with return code 2
  
  "/etc/update-motd.d/90-piboot-try" runs the command "/usr/sbin/piboot-
- try --status" that doesn't have in account the possibility of having
- piboot disabled so file "/boot/firmware/current/state" just doesn't
- exists and is mistaken with a piboot invalid/unexpected state.
+ try --status" that don't have in account the possibility of having
+ piboot disabled so as file "/boot/firmware/current/state" just doesn't
+ exists it's mistaken with a piboot invalid/unexpected state.
  
  I suggest a change in command piboot-try or in "/etc/update-
  motd.d/90-piboot-try" to first test if piboot is enabled to continue
  checking.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to flash-kernel in Ubuntu.
https://bugs.launchpad.net/bugs/2127780

Title:
  [Ubuntu 25.10 Questing] Errors shown in every text session when piboot
  is not enabled

Status in flash-kernel package in Ubuntu:
  New

Bug description:
  Ubuntu 25.10 Questing for Raspberry Pi. These errors are shown in
  every text session when piboot is not enabled:

  cat: /boot/firmware/current/state: No such file or directory (os error 2)
  piboot is in an invalid or unexpected state:
  Please file an issue: ubuntu-bug flash-kernel
  run-parts: /etc/update-motd.d/90-piboot-try exited with return code 2

  "/etc/update-motd.d/90-piboot-try" runs the command "/usr/sbin/piboot-
  try --status" that don't have in account the possibility of having
  piboot disabled so as file "/boot/firmware/current/state" just doesn't
  exists it's mistaken with a piboot invalid/unexpected state.

  I suggest a change in command piboot-try or in "/etc/update-
  motd.d/90-piboot-try" to first test if piboot is enabled to continue
  checking.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2127780/+subscriptions