Comment 12 for bug 1788727

Sandi, I hope this is the correct procedure reporting via you. Thanks
for the email. My HP system seems a little different than yours, I
finished up with the two latest kernels and a warning that I also had
an old kernel that was not of the secure boot (efi) variety.

I deleted the old kernel, to find later that it was the old kernel
that worked best occasional.

I cannot directly install Ubuntu 20.18 from a USB stick, it wont even
load up. I managed to install Ubuntu 17.10 then upgrade to Ubuntu
20.18

The first non efi kernel was 4.13.0-21-generic. I upgraded from Ubuntu
17.10, and am informed that a non efi kernel 4.13.0-46-generic has
appeared and prevents completion, I have deleted this kernel. After
aprox 20 boots I gave up trying to get into the computer. (there is no
logic in getting the computer to boot up, the more I try the less
chance of success).

Next day

Five attempts booting with kernel 4.15.0-3-generic failed, third
attempt with kernel 4.13.0-21-generic success

A crash happened on the HP pc this morning and I was asked if I could
supply any data, hence this email. I hope this information reaches all
concerned and is of use.

Regards Jim
On Wed, 12 Sep 2018 at 00:00, Sandi Vujaković
<email address hidden> wrote:
>
> Jim, I only know the GUI way of doing it. I select all of the kernels
> above 4.15.xx and select remove, but only once I have booted up with the
> older kernel (once the GRUB menu appears, go into Advanced options and
> look for 4.15 and boot off of that, just don't select "(recovery
> mode)"), type "apt autoremove", but since you probably don't use the
> terminal logged in as root in it, type in "sudo apt autoremove" and it
> should automatically start configuring the packages that were not
> configured previously, a.k.a. the GRUB updates, open UKUU, install the
> latest available kernel, restart and enjoy!
>
> Do note that I am using an HP laptop and that a previous GRUB update (a
> few months ago) enrolled new Secure Boot keys, which might affect the
> fact that I'm booting with unsigned kernels and Secure Boot on.
>
> Good luck and have a nice day!
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1789107).
> https://bugs.launchpad.net/bugs/1788727
>
> Title:
> upgrade crashing due to unsigned kernels
>
> Status in grub2 package in Ubuntu:
> Confirmed
>
> Bug description:
> not surre happened during upgrade to bionic beaver
>
> ProblemType: Package
> DistroRelease: Ubuntu 18.04
> Package: grub-efi-amd64 2.02-2ubuntu8.3
> Uname: Linux 4.7.0-040700-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.20.9-0ubuntu7.2
> Architecture: amd64
> Date: Thu Aug 23 19:33:07 2018
> ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
> InstallationDate: Installed on 2018-05-30 (85 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-040700-generic root=UUID=d9d727a6-5798-4fe1-8ac0-fb79b1d05431 ro quiet splash vt.handoff=7
> Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
> PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
> RelatedPackageVersions:
> dpkg 1.19.0.5ubuntu2
> apt 1.6.3ubuntu0.1
> SourcePackage: grub2
> Title: package grub-efi-amd64 2.02-2ubuntu8.3 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
> UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1788727/+subscriptions