![]() »installiertes linux-image-unsigned-5.15.0-47-generic-Skript des Paketes post-removal«-Unterprozess gab den Fehlerwert 1 zurückīearbeitung wurde angehalten, da zu viele Fehler auftraten. Run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127ĭpkg: Fehler beim Bearbeiten des Paketes linux-image-unsigned-5.15.0-47-generic (-remove): etc/grub.d/bin/grubcfg_proxy: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: įound linux image: /boot/vmlinuz-5.15.0-50-genericįound initrd image: /boot/initrd.img-5.15.0-50-genericįound linux image: /boot/vmlinuz-5.15.0-48-genericįound initrd image: /boot/initrd.img-5.15.0-48-genericįound linux image: /boot/vmlinuz-5.15.0-46-genericįound initrd image: /boot/initrd.img-5.15.0-46-genericįound linux image: /boot/vmlinuz-5.15.0-43-genericįound initrd image: /boot/initrd.img-5.15.0-43-generic I have tried a lot of what is written on the Internet, but it keeps getting an error. On systems with two-factor authentication enabled, users will have to use either a physical device or authenticator app when establishing an SSH session. If you have come this far, then it’s our hope that the issue has been successfully resolved and that you were able to reinstall your software package. Starting with Ubuntu Server 20.04 LTS, SSH will support hardware-based two-factor authentication which minimises the impact of secrets leakage and improves the security level provided by SSH. This type of dpkg error points to an issue with the package installer usually caused by the interruption of an installation process or a corrupt dpkg database.Īny of the above-mentioned solutions should fix this error. You can thereafter give it another shot in reinstalling the software package. $ sudo rm -r /var/lib/dpkg/info/package-name.*įinally, update the package lists as shown: $ sudo apt update $ sudo ls -l /var/lib/dpkg/info | grep -i package_nameĪfter listing the files, you can move them to the /tmp directory as shown $ sudo mv /var/lib/dpkg/info/package-name.* /tmpĪlternatively, you can use the rm command to manually remove the files. First, you need to find these files which are located in the /var/lib/dpkg/info directory as shown. Lastly, you can manually remove all the associated with the troublesome package. Solution 4: Remove all the Files Associated with the Package Then invoke the commands below to remove all the old, unused, and unnecessary packages which also frees up space on your hard drive. $ sudo apt remove -purge google-chrome-stable $ sudo apt remove -purge package_nameįor example, in my case, purging the Google chrome package fixed the issue. ![]() If the first two solutions did not fix the problem, you can remove or purge the problematic software package as shown. Solution 3: Purge the Bad or Corrupted Software Package The -f option & -fix-broken can be interchangeably used to fix broken dependencies resulting from an interrupted package or cached package download. When such happens, you can force install the package using the -f option as shown. Sometimes, errors can occur during the installation of software packages. Solution 2: Force Install the Troublesome Package This reconfigures the unpacked packages that were not installed during the installation process.
0 Comments
Leave a Reply. |