[Bug 2131602] [NEW] bug-reporter has bug AND apt update failed due to /boot being mounted ro.

A. Revok 2131602 at bugs.launchpad.net
Sat Nov 15 15:36:24 UTC 2025


Public bug reported:

apt upgrade flash-kernel failed, due to /boot being mounted ro.

AND while trying to report this, with the /bin/ubuntu-bug util,

none of the options allowed were for plain upgrade problems,

so I chose Other,

which then failed, because I hadn't picked one of the ALLOWED ( all the
*other* radio-buttons? ) options.

Which is why I reported it using this option, which to-me isn't correct.

---

Remounting /boot rw,

then running

apt  upgrade  --fix-missing

fixed it, for me, but now everybody else living in RasPi/Ubuntu's
borked.

_ /\ _

ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: ubuntu-release-upgrader-core 1:25.10.8
ProcVersionSignature: Ubuntu 6.17.0-1004.4-raspi 6.17.1
Uname: Linux 6.17.0-1004-raspi aarch64
ApportVersion: 2.33.1-0ubuntu3
Architecture: arm64
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/mmcblk0p1)
CrashDB: ubuntu
CurrentDesktop: LXQt
Date: Sat Nov 15 10:27:34 2025
ImageMediaBuild: 20251007
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-release-upgrader (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug arm64 arm64-image dist-upgrade questing raspi-image

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

Title:
  bug-reporter has bug AND apt update failed due to /boot being mounted
  ro.

Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  apt upgrade flash-kernel failed, due to /boot being mounted ro.

  AND while trying to report this, with the /bin/ubuntu-bug util,

  none of the options allowed were for plain upgrade problems,

  so I chose Other,

  which then failed, because I hadn't picked one of the ALLOWED ( all
  the *other* radio-buttons? ) options.

  Which is why I reported it using this option, which to-me isn't
  correct.

  ---

  Remounting /boot rw,

  then running

  apt  upgrade  --fix-missing

  fixed it, for me, but now everybody else living in RasPi/Ubuntu's
  borked.

  _ /\ _

  ProblemType: Bug
  DistroRelease: Ubuntu 25.10
  Package: ubuntu-release-upgrader-core 1:25.10.8
  ProcVersionSignature: Ubuntu 6.17.0-1004.4-raspi 6.17.1
  Uname: Linux 6.17.0-1004-raspi aarch64
  ApportVersion: 2.33.1-0ubuntu3
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: config-disk (/dev/mmcblk0p1)
  CrashDB: ubuntu
  CurrentDesktop: LXQt
  Date: Sat Nov 15 10:27:34 2025
  ImageMediaBuild: 20251007
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2131602/+subscriptions




More information about the foundations-bugs mailing list