System drops to GRUB prompt after kernel update and release upgrade (UEFI, dual boot with Windows 10)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- operating-systems
Research direction
Start by reviewing the Update Manager path that handles kernel and Linux Mint release upgrades, then inspect proposed PR #1026. Reproduce the upgrade on a UEFI dual-boot system with Windows 10 and verify that reboot reaches the normal boot menu rather than a GRUB prompt.
Written by the indexing model from the issue text.
Description
System information
Initial Linux Mint version: 22.2 "Zara"
Updated Linux Mint version: 22.3 "Zena"
Kernel before update: 6.14.0-37
Kernel after update: 6.17.0-14
Firmware: UEFI
Boot setup: Dual boot (Linux Mint + Windows 10)
Update method: Update Manager (default settings)
Steps to reproduce
- Install Linux Mint 22.2 "Zara" alongside Windows 10 (UEFI, dual boot).
- Use Update Manager to install regular system updates.
- Update includes a kernel upgrade (to 6.17.0-14) and system upgrade to Linux Mint 22.3.
- Reboot the system.
Actual result
System fails to boot and drops to GRUB command line prompt:
GNU GRUB version 2.12
Minimal BASH-like line editing is supported.
grub>
System cannot boot without manual GRUB recovery.
Expected result
System should boot normally after a kernel update and release upgrade,
or provide automatic recovery / clear guidance,
especially on common UEFI dual-boot setups.
Impact
Critical. A regular update via Update Manager renders the system unbootable
on a common UEFI dual-boot configuration.
This is not recoverable by a non-technical user.
Additional notes
No custom bootloader configuration.
System was recovered manually after the failure.
Proposed fix: PR #1026
- Dominant language
- Python
- Stars
- 421
- Forks
- 191
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/mintupdate
-
BUG
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
linuxmint/mintupdate#1089 · 1 comment ·
-
BUG
Difficulty 1/5 Under an hour Newbie friendliness 88/100
linuxmint/mintupdate#1062 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
linuxmint/mintupdate#1041 · 1 comment ·
-
FEATURE REQUEST
Difficulty 1/5 Under an hour Newbie friendliness 65/100
linuxmint/mintupdate#910 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
linuxmint/mintupdate#903 ·
All issues in linuxmint/mintupdate
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Qiskit/qiskit-ibm-runtime#3431 · 1 comment ·
Maintainers usually reply within 1 day
-
[Lesson] A compatibility-gate rejection is a verdict, not something to overwrite with --accept-riskOpenlesson-submission needs-ac pending-review
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Ikalus1988/MisakaNet#2870 ·
Maintainers usually reply within 1 day
-
feature:LinkChecker
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
digitalfabrik/integreat-cms#4594 ·
Maintainers usually reply within 5 days