High CPU usage and broken dpkg after upgrade

Hi,
After upgrading to 17, I noticed that my base CPU usage was higher than usual, with no particular process standing out.

While trying to update packages through Synaptic, I got an error message saying it couldn't get exclusive access to packages.

I then tried to update through apt, which then told me that some dpkg process was locking packages, even though I had nothing running otherwise.
Once the process terminated, I was finally able to run apt upgrade, which then returned the following :

Errors were found while executing : 
 grub-efi-amd64-signed
 shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

The Zorin update manager similarly crashed while trying to update.

1 Like

It looks like you have Secure Boot enabled in your BIOS / EFI settings. Are you dual booting with Windows OS?
If not, then you can safely disable Secure Boot in your BIOS / EFI settings.

I technically still have a Windows partition, but haven't booted it in years.
I think that there was a significant BIOS update after the upgrade to 17, this might have enabled it again, I will check.

It would be great to see a side-by-side TOPS/HTOPS comparison of ZOS 16.3 to ZOS 17 to see what processes are running causing the additional CPU usage. Given ZOS 17 is based on Ubuntu 22.04 LTS which is a different version entirely than the ZOS 16.3 base of Ubuntu 20.04 LTS, there may be additional applications running in the background that might be by design from Ubuntu, GNOME, or Zorin... or all 3 combined. For now this is anecdotal at best since we have no baseline comparison. So far from perspective, it has been running well but my perspective is anecdotal at best too.

1 Like

Just checked, Secure Boot is still disabled.

I have noticed a higher workload for specific tasks as well, such as displaying videos, which wasn't the case before. Still anecdotal for now too.

1 Like

Just wondering if any change in performance if OP hits the gearwheel icon at login and chooses X instead of the default Wayland session.

1 Like

After rebooting to check the Secure Boot setting, I restarted Synaptic and was prompted to reinstall grub somewhere. I picked my boot partition, install went fine, I haven't rebooted yet but hopefully it will be fine.
Everything updates normally.

CPU usage went down significantly once the packages were updated, but I will try X11 to see if it helps.

1 Like

Bit of a late update : switched to X11, everything now runs perfectly fine. Seems Wayland is still a bit troublesome.

1 Like

I have therefore marked your last post as Solution.

1 Like