Can't install updates or app's.

[jackjump]

That's okay... Let me try to explain what I see from all that output, and tell the story it tell's...

*** The only kernel that is currently there in the /boot folder to actually boot from is kernel 5.15.0-87-generic. ***

That is odd, because package-wise it says that these kernels are installed:

linux-image-5.13.0-37-generic
linux-image-5.13.0-39-generic
linux-image-5.15.0-87-generic

So the kernels for -39 and -37 didn't completely install correctly (no initramfs images present in /boot). It looks like the problems started with -37 back in 20.04... Either that, or it started to remove them , then when that failed, didn't roll anything back. It shows -87 as the current running kernel...

Your updates are trying to install kernel versions 5.15.0-88-generic and 6.2.0-36-generic... Those are the current kernels for 22.04 in the generic and generic-hwe series.

This starts a change of events... When Ubuntu installs a new kernel, it leaves 2 previous kernels, and tries to remove the older kernels than those.

It sees kernel 5.15.0-87 as an installed package, is booted from that as the latest kernel.

It's trying to remove the oldest kernels, so that after the install of the 2 new kernels that there will be the newest, and 2 older kernels (6.2.0-36, 5.15.0-88, 5.15.0-87). That would be the right things to do.

But it can't, because it cannot remove those because there were some problems. It cannot resolve those problems on it's own.

Did you follow that logic?

---

Let's try to check if they are even available anymore through his apt system. Becaseu they were 20.04 kernels, and he is now 22.04...

apt list linux-*-5.13.0-37-generic

I see those in my 22.04 results...

sudo update 
sudo apt install --reinstall openssl
sudo apt install --reinstall linux-modules-extra-5.13.0-37-generic linux-modules-extra-5.13.0-37-generic linux-headers-5.13.0-37-generic linux-image-5.13.0-37-generic
sudo apt install --reinstall linux-modules-extra-5.13.0-39-generic  linux-modules-extra-5.13.0-39-generic linux-headers-5.13.0-39-generic  linux-image-5.13.0-39-generic

The run your updates to see if they get removed successfully.

__________________________________________________ __________________________________________________ _________________________


I'm not sure if I follow your logic. I did find that there's a number of differences between how a Grub menu is generated now versus back in the day. (Which was my only lead in this matter - the choice I made - when upgrading.) It seems that there's a number of ref'ed files and at least one script, in auto configuring Grub. On the other hand, I probably went down the garden path on a mistaken hunch.

I didn't know what to make of the SSL issue but it seemed to be unrelated and I didn't want to dig my hole deeper.


Command outputs:

(base) jack@HR-Kubuntu:~$ sudo apt update 
[sudo] password for floyd:  
Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB] 
Hit:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease 
Get:3 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB] 
Hit:4 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease 
Fetched 229 kB in 1s (172 kB/s) 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
6 packages can be upgraded. Run 'apt list --upgradable' to see them. 
(base) jack@HR-Kubuntu:~$ 

(base) jack@HR-Kubuntu:~$ sudo apt install --reinstall openssl 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
The following packages will be REMOVED: 
  linux-image-5.13.0-37-generic linux-image-5.13.0-39-generic 
0 upgraded, 0 newly installed, 1 reinstalled, 2 to remove and 6 not upgraded. 
2 not fully installed or removed. 
Need to get 0 B/1,182 kB of archives. 
After this operation, 20.4 MB disk space will be freed. 
Do you want to continue? [Y/n] Y 
(Reading database ... 215206 files and directories currently installed.) 
Removing linux-image-5.13.0-37-generic (5.13.0-37.42~20.04.1) ... 
/etc/kernel/postrm.d/initramfs-tools: 
update-initramfs: Deleting /boot/initrd.img-5.13.0-37-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 ... 
using custom appearance settings 
/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.13.0-37-generic (--remove): 
 installed linux-image-5.13.0-37-generic package post-removal script subprocess retur
ned error exit status 1 
dpkg: too many errors, stopping 
Errors were encountered while processing: 
 linux-image-5.13.0-37-generic 
Processing was halted because there were too many errors. 
E: Sub-process /usr/bin/dpkg returned an error code (1) 
(base) jack@HR-Kubuntu:~$

(base) jack@HR-Kubuntu:~$ sudo apt install --reinstall linux-modules-extra-5.13.0-37
-generic linux-modules-extra-5.13.0-37-generic linux-headers-5.13.0-37-generic linux-
image-5.13.0-37-generic 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
Package linux-headers-5.13.0-37-generic is not available, but is referred to by anoth
er package. 
This may mean that the package is missing, has been obsoleted, or 
is only available from another source 

Package linux-modules-extra-5.13.0-37-generic is not available, but is referred to by
 another package. 
This may mean that the package is missing, has been obsoleted, or 
is only available from another source 

E: Package 'linux-modules-extra-5.13.0-37-generic' has no installation candidate 
E: Package 'linux-modules-extra-5.13.0-37-generic' has no installation candidate 
E: Package 'linux-headers-5.13.0-37-generic' has no installation candidate 
(base) jack@HR-Kubuntu:~$ 

(base) jack@HR-Kubuntu:~$ sudo apt install --reinstall linux-modules-extra-5.13.0-39
-generic  linux-modules-extra-5.13.0-39-generic linux-headers-5.13.0-39-generic  linu
x-image-5.13.0-39-generic 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
Package linux-headers-5.13.0-39-generic is not available, but is referred to by anoth
er package. 
This may mean that the package is missing, has been obsoleted, or 
is only available from another source 

Package linux-modules-extra-5.13.0-39-generic is not available, but is referred to by
 another package. 
This may mean that the package is missing, has been obsoleted, or 
is only available from another source 

E: Package 'linux-modules-extra-5.13.0-39-generic' has no installation candidate 
E: Package 'linux-modules-extra-5.13.0-39-generic' has no installation candidate 
E: Package 'linux-headers-5.13.0-39-generic' has no installation candidate 
(base) jack@HR-Kubuntu:~$

After the above, I tried the package update, in the GUI, with the same result:

Package failed to install:
Error while installing package: installed linux-image-5.13.0-37-generic package post-removal script subprocess returned error exit status 1

I'm baffled. (That's why I'm here. )
apt-get remove and apt-get purge (with sudo, essentially root access) doesn't work. It's as if something is blocking the action.

Again, thanks for your time and help.

[jackjump]

Generating grub configuration file ...
using custom appearance settings
/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

I can't find /etc/grub.d/bin/grubcfg_proxy in the official repos, neither in 20.04 nor in 22.04. I can find libcrypto.so.1.1, which is in libssl1.1, a package in the repos for 20.04, but not for 22.04. I suspect that grubcfg_proxy was installed from some third party source and wasn't removed during the upgrade. It depends on libcrypto.so.1.1, which was removed during the upgrade. So your update-grub is broken and must be fixed before any kernel can be fully installed or removed. Leaving third party software during an upgrade, especially is such a vital position as grub, may lead to trouble. May it have anything to do with those "custom appearance settings"?

Question is: how to cleanly remove grubcfg_proxy? Maybe this will give a clue:

dpkg --list grub*
dpkg --search /etc/grub.d/bin/grubcfg_proxy

__________________________________________________ __________________________________________________ ____________

Some of that might make some sense. I believe I enabled a third party repo for a specific app, some time ago, but that wouldn't have anything to do with grub. As I recall it was to load up a cutting edge version of a game, Endless-Sky. (This was a year or two ago.) I beleive I disabled the custom repo.
In any case,,

The Command Outputs:

(base) jack@HR-Kubuntu:~$ dpkg --list grub* 
Desired=Unknown/Install/Remove/Purge/Hold 
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend 
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) 
||/ Name                  Version         Architecture Description 
+++-=====================-===============-============-===================================================== 
un  grub                  <none>          <none>       (no description available) 
un  grub-cloud-amd64      <none>          <none>       (no description available) 
ii  grub-common           2.06-2ubuntu7.2 amd64        GRand Unified Bootloader (common files) 
un  grub-coreboot         <none>          <none>       (no description available) 
un  grub-doc              <none>          <none>       (no description available) 
un  grub-efi              <none>          <none>       (no description available) 
un  grub-efi-amd64        <none>          <none>       (no description available) 
un  grub-efi-arm          <none>          <none>       (no description available) 
un  grub-efi-arm64        <none>          <none>       (no description available) 
un  grub-efi-ia32         <none>          <none>       (no description available) 
un  grub-efi-ia64         <none>          <none>       (no description available) 
un  grub-emu              <none>          <none>       (no description available) 
ii  grub-gfxpayload-lists 0.7             amd64        GRUB gfxpayload blacklist 
un  grub-ieee1275         <none>          <none>       (no description available) 
un  grub-legacy           <none>          <none>       (no description available) 
un  grub-legacy-doc       <none>          <none>       (no description available) 
un  grub-linuxbios        <none>          <none>       (no description available) 
ii  grub-pc               2.06-2ubuntu7.2 amd64        GRand Unified Bootloader, version 2 (PC/BIOS version) 
ii  grub-pc-bin           2.06-2ubuntu7.2 amd64        GRand Unified Bootloader, version 2 (PC/BIOS modules) 
un  grub-uboot            <none>          <none>       (no description available) 
un  grub-xen              <none>          <none>       (no description available) 
un  grub-yeeloong         <none>          <none>       (no description available) 
un  grub2                 <none>          <none>       (no description available) 
ii  grub2-common          2.06-2ubuntu7.2 amd64        GRand Unified Bootloader (common files for version 2) 
(base) jack@HR-Kubuntu:~$

(base) jack@HR-Kubuntu:~$ dpkg --search /etc/grub.d/bin/grubcfg_proxy 
dpkg-query: no path found matching pattern /etc/grub.d/bin/grubcfg_proxy 
(base) jack@HR-Kubuntu:~$ 

I navigated to the above location and, interestingly, I found the file as follows:

(base) floyd@HR-Kubuntu:/etc/grub.d/bin$ ls 
grubcfg_proxy
(base) floyd@HR-Kubuntu:/etc/grub.d/bin$

I viewed the contents of the grubcfg_proxy file in nano.
It's obviously not a text file but it contains text that indicates that it might affect the Grub menu. It contains fields for other inputs and outputs.

[MAFoElffen]

This error... I've seen this before...

/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

That error doesn't affect everyone, but seems to only hit when certain conditions are seen together. That is somewhere in the code, that is met / repaired by this, that I posted my solution above...

sudo apt install --reinstall openssl

Which, that package adds that module there, or reinstalls it if not, so then it is found. Not really sure why they are looking for that. Like I said, when some machines hit a certain perfect storm condition... That openssl package is not a default installed, but no harm if you do install it, and it gets that past that error that appears on some machines.

[qyot27]

A quick search uncovered this on AskUbuntu:

https://askubuntu.com/questions/1116...185815#1185815

Short version: find where libcrypto.so.1.1 is on your system (possibly inside a snap directory), copy it to one of the library paths where grubcfg_proxy can find it. Then run

sudo apt-get --fix-broken install

and then

sudo apt-get --purge autoremove

[MAFoElffen]

From that, then this to find and copy it...

sudo cp $(ls  /snap/core*/*/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 } | head -n1) /usr/lib/x86_64-linux-gnu/

[jackjump]

This error... I've seen this before...

/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

That error doesn't affect everyone, but seems to only hit when certain conditions are seen together. That is somewhere in the code, that is met / repaired by this, that I posted my solution above...

sudo apt install --reinstall openssl

Which, that package adds that module there, or reinstalls it if not, so then it is found. Not really sure why they are looking for that. Like I said, when some machines hit a certain perfect storm condition... That openssl package is not a default installed, but no harm if you do install it, and it gets that past that error that appears on some machines.

__________________________________________________ _______________

That's the main problem as I perceive it. The issue, I can't install anything without deleting the old kernels (that refuse to be deleted), preclude the possibility of reinstalling something (like openssl) that might straighten this out. It's a circular problem.

(base) jack@HR-Kubuntu:~$ sudo apt install --reinstall openssl 
[sudo] password for jack:  
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
The following packages will be REMOVED: 
  linux-image-5.13.0-37-generic linux-image-5.13.0-39-generic 
0 upgraded, 0 newly installed, 1 reinstalled, 2 to remove and 9 not upgraded. 
2 not fully installed or removed. 
Need to get 0 B/1,182 kB of archives. 
After this operation, 20.4 MB disk space will be freed. 
Do you want to continue? [Y/n] Y 
(Reading database ... 215206 files and directories currently installed.) 
Removing linux-image-5.13.0-37-generic (5.13.0-37.42~20.04.1) ... 
/etc/kernel/postrm.d/initramfs-tools: 
update-initramfs: Deleting /boot/initrd.img-5.13.0-37-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 ... 
using custom appearance settings 
/etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: libcrypto.so.1.1: cannot open shared objec
t 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.13.0-37-generic (--remove): 
 installed linux-image-5.13.0-37-generic package post-removal script subprocess returned error exit status 1 
dpkg: too many errors, stopping 
Errors were encountered while processing: 
 linux-image-5.13.0-37-generic 
Processing was halted because there were too many errors. 
E: Sub-process /usr/bin/dpkg returned an error code (1) 
(base) jack@HR-Kubuntu:~$ 

[tea for one]

I did an in place upgrade from 20.X to 22.04.3
During the upgrade I was prompted about Grub as to, whether or not, I wanted to keep the existing config file. Since this OS is on a multi-boot platform (like an idiot) I elected to keep the existing config file.

Did you have grub-customizer installed in Ubuntu 20.X?
Later posts show the existence of /etc/grub.d/bin/grubcfg_proxy and grub proxy files are generated by grub-customizer.
Try this in a terminal:-

apt policy grub-customizer

[jackjump]

From that, then this to find and copy it...

sudo cp $(ls  /snap/core*/*/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 } | head -n1) /usr/lib/x86_64-linux-gnu/

__________________________________________________ ___________________-

The command failed:

(base) jack@HR-Kubuntu:/usr/lib/x86_64-linux-gnu$ sudo cp $(ls  /snap/core*/*/usr/lib/x86_64-linux-gnu/libcryp
to.so.1.1 } | head -n1) /usr/lib/x86_64-linux-gnu/ 
ls: cannot access '}': No such file or directory

However, the package exists in the destination location:

(base) jack@HR-Kubuntu:/usr/lib/x86_64-linux-gnu$ ls libcrypto* 
libcrypto.so.1.1  libcrypto.so.3

[deadflowr]

look in /snap/core22/current/lib/x86_64-linux-gnu

Never mind.
I missed the bottom of the above post.

[jackjump]

A quick search uncovered this on AskUbuntu:

https://askubuntu.com/questions/1116...185815#1185815

Short version: find where libcrypto.so.1.1 is on your system (possibly inside a snap directory), copy it to one of the library paths where grubcfg_proxy can find it. Then run

sudo apt-get --fix-broken install

and then

sudo apt-get --purge autoremove

__________________________________________________ _____________________________

Since the file (libcrypto.so.1.1) was found in the location specified by @MAFoElffen /usr/lib/x86_64-linux-gnu/
I ran your command lines.

Command outputs:

(base) jack@HR-Kubuntu:/usr/lib/x86_64-linux-gnu$ sudo apt-get --fix-broken install 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
The following packages will be REMOVED: 
  linux-image-5.13.0-37-generic linux-image-5.13.0-39-generic 
0 upgraded, 0 newly installed, 2 to remove and 9 not upgraded. 
2 not fully installed or removed. 
After this operation, 20.4 MB disk space will be freed. 
Do you want to continue? [Y/n] Y 
(Reading database ... 215206 files and directories currently installed.) 
Removing linux-image-5.13.0-37-generic (5.13.0-37.42~20.04.1) ... 
/etc/kernel/postrm.d/initramfs-tools: 
update-initramfs: Deleting /boot/initrd.img-5.13.0-37-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 ... 
using custom appearance settings 
Found linux image: /boot/vmlinuz-5.15.0-87-generic 
Found initrd image: /boot/initrd.img-5.15.0-87-generic 
Found linux image: /boot/vmlinuz-5.15.0-87-generic 
Found initrd image: /boot/initrd.img-5.15.0-87-generic 
Found memtest86+ image: /memtest86+.elf 
Found memtest86+ image: /memtest86+.bin 
Found Windows 10 on /dev/sda1 
Found memtest86+ image: /memtest86+.elf 
Found memtest86+ image: /memtest86+.bin 
done 
Removing linux-image-5.13.0-39-generic (5.13.0-39.44~20.04.1) ... 
/etc/kernel/postrm.d/initramfs-tools: 
update-initramfs: Deleting /boot/initrd.img-5.13.0-39-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 ... 
using custom appearance settings 
Found linux image: /boot/vmlinuz-5.15.0-87-generic 
Found initrd image: /boot/initrd.img-5.15.0-87-generic 
Found linux image: /boot/vmlinuz-5.15.0-87-generic 
Found initrd image: /boot/initrd.img-5.15.0-87-generic 
Found memtest86+ image: /memtest86+.elf 
Found memtest86+ image: /memtest86+.bin 
Found Windows 10 on /dev/sda1 
Found memtest86+ image: /memtest86+.elf 
Found memtest86+ image: /memtest86+.bin 
done 
(base) jack@HR-Kubuntu:/usr/lib/x86_64-linux-gnu$

(base) jack@HR-Kubuntu:/usr/lib/x86_64-linux-gnu$ sudo apt-get --purge autoremove 
Reading package lists... Done 
Building dependency tree... Done 
Reading state information... Done 
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.

__________________________________________________ __________________

sudo apt-get --fix-broken install

appears to have cleared the log jam. My normal updates have cleared and I can now install apps.

Thanks!