[Bug 2150675] [NEW] /etc/default/grub found empty (0 bytes) after unattended upgrade on Ubuntu 26.04 while updating to kernel 7.0.0-15
Eric Rickin
2150675 at bugs.launchpad.net
Wed Apr 29 20:10:38 UTC 2026
Public bug reported:
System Context:
I have two identical Intel 13th Gen i7 NUCs running Ubuntu 26.04.
The Issue:
Following an unattended-upgrade which updated the kernel from 7.0.0-14 to 7.0.0-15 involving the grub2 package, one machine became unresponsive/stuck, requiring a hard reboot. After rebooting, the system defaulted to a verbose boot (no splash screen) and showed a GRUB menu timeout.
Upon inspection, /etc/default/grub on the affected machine was
completely empty (0 bytes). The second identical machine updated
successfully without wiping the file.
Impact:
Loss of critical boot parameters including quiet splash, zswap settings, and USB power management overrides (usbcore.autosuspend).
Steps to Resolve:
Manually restoring the content of /etc/default/grub from the healthy machine and running sudo update-grub resolved the issue.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Tags: 26.04 grub2 unattended-upgrades
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/2150675
Title:
/etc/default/grub found empty (0 bytes) after unattended upgrade on
Ubuntu 26.04 while updating to kernel 7.0.0-15
Status in grub2 package in Ubuntu:
New
Bug description:
System Context:
I have two identical Intel 13th Gen i7 NUCs running Ubuntu 26.04.
The Issue:
Following an unattended-upgrade which updated the kernel from 7.0.0-14 to 7.0.0-15 involving the grub2 package, one machine became unresponsive/stuck, requiring a hard reboot. After rebooting, the system defaulted to a verbose boot (no splash screen) and showed a GRUB menu timeout.
Upon inspection, /etc/default/grub on the affected machine was
completely empty (0 bytes). The second identical machine updated
successfully without wiping the file.
Impact:
Loss of critical boot parameters including quiet splash, zswap settings, and USB power management overrides (usbcore.autosuspend).
Steps to Resolve:
Manually restoring the content of /etc/default/grub from the healthy machine and running sudo update-grub resolved the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2150675/+subscriptions
More information about the foundations-bugs
mailing list