Upgrade from LM (Cinnamon) 21.3 to 22 Fails: Unbootable; boot-repair Does Not Fix; grub-efi-amd64-signed Not Installed
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- linux, python
- Domain
- operating-systems
Research direction
Start with the mint-upgrade entry point and reproduce the described apt-get upgrade/dist-upgrade path from Linux Mint 21.3 to 22, paying attention to the grub-efi-amd64-signed, grub-efi-amd64-bin, and base-files packages named in the report. Done means the upgrade completes with the expected Mint 22 packages installed and the system remains bootable; the payload names no source files or tests.
Written by the indexing model from the issue text.
Description
Multiple attempts to use mint-upgrade to upgrade from Linux Mint (Cinnamon) 21.3 to 22 failed with the system unbootable.
Use of boot-repair from a Linux Mint Live environment did not fix the problem.
After restoring to a working LM 21.3 via Timeshift,
apt-get upgrade
apt-get dist-upgrade
also produced an unbootable system, but revealed that grub-efi-amd64-signed and grub-efi-amd64-bin had not been installed.
In the attempted upgrade using apt-get upgrade and dist-upgrade, those packages had been held back due to phased updates.
Forcing installation of grub-efi-amd64-signed (bringing grub-efi-amd64-bin in as a dependency) resulted in a bootable system.
Some references to LM 21.3 persisted because the LM 22 version of the base-files package had not been installed; LM's versioning causes the LM22 package to be considered a "downgrade". Installing base-files, specifying the LM 22 version of the package:
apt-get install base-files=13ubuntu10mint22.0.0+wilma
fixed that. I have no idea what else, if anything, was not successfully upgraded.
- Dominant language
- Python
- Stars
- 50
- Forks
- 20
- 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/mintupgrade
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
linuxmint/mintupgrade#128 · 5 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
linuxmint/mintupgrade#127 ·
-
Keyboard layoutOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
linuxmint/mintupgrade#126 · 1 reaction ·
-
Add check and user warning for missing MOK key enrollment after Secure Boot system upgrade (LMDE 7)Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
linuxmint/mintupgrade#125 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
linuxmint/mintupgrade#123 ·
All issues in linuxmint/mintupgrade
Similar issues
-
needs-human needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
gke-labs/kube-agents#2400 · 1 comment ·
Maintainers usually reply within 1 day
-
Device Details tables: FS/SF columns contradict each other (nfet_01v8 Vt row, pfet_01v8 Idsat row)Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
google/skywater-pdk#450 ·
-
Drained trajectory arrays are overwritten when the sequence buffer is reusedPossibly taken @sylvesterkaczmarek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
google-deepmind/bsuite#56 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
LearningCircuit/local-deep-research#7206 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
chingu-voyages/V62-tier3-team-33#285 ·
Maintainers usually reply within 1 day