How to Avoid Grub Errors After Running Apt-Get Upgrade - Ubuntu

Error: grub-efi-amd64-signed in Ubuntu 20.04. Trying to install packages

I had this same problem the last few days. Months ago I installed Ubuntu 20.04 alongside Win10 I had to switch the BIOS to AHCI from RAID as it wouldn't allow install. Then after install I could switch back to RAID to allow Win10 dual boot. However along some update it messed it up and I had to switch back to AHCI and reinstalled grub as above. It sorted the problem.

Ubuntu Update Failed; how do I fix packages with broken triggers?

Wow, first downvote. Thanks. Well I'll answer my own question. This isn't the minimalistic or perfect solution, but when I subsequently installed another package, this caused the triggers to run again, and that fixed the problem.

sudo apt-get install git

(Git has nothing to do with it, I just needed it, and the package system fixed itself!)

error: symbol 'grub_calloc' not found on Ubuntu boot

You need to reinstall grub to your boot partition, which can be done as follows:

• boot to a linux live system (e.g. Ubuntu Desktop).

• assuming your actual boot partition is /dev/sda1 run the following:

   sudo apt-get update && apt-get install grub2
   sudo mount /dev/sda1  /mnt    
   sudo grub-install --root-directory=/mnt/  /dev/sda 
  

• restart your system, do not forget to remove the live image.

How do I resolve `The following packages have unmet dependencies`

The command to have Ubuntu fix unmet dependencies and broken packages is

sudo apt-get install -f

from the man page:

-f, --fix-broken
Fix; attempt to correct a system with broken dependencies in place.
This option, when used with install/remove, can omit any packages
to permit APT to deduce a likely solution. If packages are
specified, these have to completely correct the problem. The option
is sometimes necessary when running APT for the first time; APT
itself does not allow broken package dependencies to exist on a
system. It is possible that a system's dependency structure can be
so corrupt as to require manual intervention (which usually means
using dselect(1) or dpkg --remove to eliminate some of the
offending packages)

Ubuntu will try to fix itself when you run the command. When it completes, you can test if it worked by running the command again, and you should receive output similar to:

Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

---

Related Topics