Question

4

Linux Kernel update error causing package management to grind to a halt!

rated 0 times [ 4] [ 0] / answers: 1 / hits: 772 / 1 Year ago, sat, march 11, 2023, 4:28:43

I recently went to update my system (Ubuntu Studio 22.10) and new Linux Kernels were available. On Ubuntu Studio you receive updates for both the generic and low latency kernels, with the low latency being the one you boot too.

Well something has clearly gone wrong with this, as it fails to install the updated kernels (both of them) and now I can't install or update any of my packages using apt (luckily snap and flatpak still works).

I am currently stuck on kernel low latency 1009, when 1012 is available.

I've seen some questions similar to this but none can provide me with a solution.

Neither Sudo apt-get install -f nor sudo apt --fix-broken install work.

My system seems to want me to remove linux-image-5.19.0-23-generic but any attempt to remove this package fails, and tells me that dpkg has ran into too many errors.

When attempting to remove the package through Synaptic all I got was this:

E: linux-image-5.19.0-23-generic: installed linux-image-5.19.0-23-generic package post-removal script subprocess returned error exit status 1

It might also be useful to note that this install of Ubuntu started at 21.10 and has been upgraded through 22.04 and 22.10. I would really rather not have to reinstall my entire system. So please say there is a way to fix this.

I'll be glad to provide more info if needed.

Thank you in advance!

Edit: here is the output of apt -f install

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

The following packages will be REMOVED

  linux-image-5.19.0-23-generic

0 to upgrade, 0 to newly install, 1 to remove and 2 not to upgrade.

3 not fully installed or removed.

After this operation, 12.2 MB disk space will be freed.

Do you want to continue? [Y/n] y

(Reading database ... 406974 files and directories currently installed.)

Removing linux-image-5.19.0-23-generic (5.19.0-23.24) ...

/etc/kernel/postrm.d/initramfs-tools:

update-initramfs: Deleting /boot/initrd.img-5.19.0-23-generic

/etc/kernel/postrm.d/zz-update-grub:

Sourcing file `/etc/default/grub'

Sourcing file `/etc/default/grub.d/init-select.cfg'

Generating grub configuration file ...

/etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory

run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127

dpkg: error processing package linux-image-5.19.0-23-generic (--remove):

 installed linux-image-5.19.0-23-generic package post-removal script subprocess returned error exit status 1

dpkg: too many errors, stopping

Errors were encountered while processing:

 linux-image-5.19.0-23-generic

Processing was halted because there were too many errors.

E: Sub-process /usr/bin/dpkg returned an error code (1)

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

uestred

Add To Favorites

Follow

Total Points: 464

Total Questions: 104

Total Answers: 112

Location: Israel

Member since Wed, Apr 14, 2021

3 Years ago

uestred questions

1 SDDM error - Cannot assign to non-existent property "actionItemsVisible"

Mon, Sep 27, 21, 03:43, 3 Years ago

1 What does dev mean in linux commands?

Wed, Mar 2, 22, 04:04, 2 Years ago

1 Bluetooth audio problems on 21.04

Wed, Jan 5, 22, 05:57, 2 Years ago

1 Ubuntu Landscape - update_security_db.sh failure on fresh quickstart deployment

Sun, Apr 30, 23, 12:47, 1 Year ago

1 Firefox is rendering window and pages transparent and flickering

Tue, Dec 21, 21, 08:26, 2 Years ago

View All

answered 1 Year ago utschang · Accepted Answer

Currently you cannot do much except install the libcrypto.so.1.1 which is an deprecated version like this.

the origin of the problem is the grub script grub_proxy, it is not from any official packages. It must come from your own modification or from some ppa.

Please try:

apt-file find grubcfg_proxy

If you have apt-file. Identify that package and uninstall it. Then try to find alternative to it. I guess you are using grub-customizer. When you use some ppa change your boot process and then use do-release-upgrade is basically shooting yourself in the foot. Because, do-release-upgrade will try to mask out all customized repos. However, boot process definitely depends on those masked out packages to function. Moreover, the old packages on the system usually depend on system libraries accurately to specific subversions. So in most cases the old packages won't work at all. Most users do not notice this, since they are not using boot-process-customizers. After reboot into new version, the broken packages can be upgraded by enable the ppa of new release version or uninstalled and replaced by alternative packages.

To me, the release upgrade never works (more than 20 year experience. I try the release upgrade method every time I saw it, never works.). I highly recommend you reinstall your system regularly. You have to be smart to keep your /home on a different partition and do not format or overwrite it during installation. After installation, you can try out fresh system to see if you like it. Then modify /etc/fstab to mount your /home partition back. Then you can see if there is some config in your ~ you have to modify (usually only small portion of them need to be changed/recreated).

You can check how many mess the release-upgrade had created via running aptitude search '?narrow(?installed, ~o)'. This gives you the orphan packages usually a source of broken dependencies.

Reinstall ubuntu only take about 10 mins, so no real reason to not do it if you do not perform deep customization: (adding too many ppas, change too much boot configuration, use more than twice update-alternatives). If you do lots of customization then you wish not touch the configurations. However, the configure files change formats, the packages come and go. Thus, if you wish to not touch the configuration, you end up cannot upgrade at all: the release update will destroy your system. This is hard lesson I learned at the very beginning and it remains true. So I highly recommand you only do user customization with configs in your ~/. Only touch very small set of configuration in /etc and use some sysop tools like ansible to maintain it, if you feel you still touched too many parts of the system and need to automate it. If you do not know what ansible is and do not want to learn it. Then I suggest you choose the best distro fit you out-of-box. Do NOT tweak the system to make it your own distro, it is missing impossible. You have to ask yourself if you hate most of the default settings why you are still using this distro at all.