SUMMARY After upgrading to Ubuntu 20.04 LTS, reboot goes to the GRUB2 command line with no indication of why the boot failed. STEPS TO REPRODUCE 1. Upgrade from Neon User Edition 5.19 to Ubuntu 20.04 LTS using the instructions provided at https://community.kde.org/Neon/FocalUpgrades 2. Reboot (as normal part of the upgrade). OBSERVED RESULT Reboot fails, dropping back to GRUB2 command line. EXPECTED RESULT Normal reboot. SOFTWARE/OS VERSIONS Linux: 5.4.0-48-generic KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.75,0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Architecture: x86_64 Dell Latitude E6530. GRUB2 package versions (from dpkg -l): grub-efi 2.04-1ubuntu26.4 grub-efi-amd64 2.04-1ubuntu26.4 grub-efi-amd64-bin 2.04-1ubuntu26.4 grub-efi-amd64-signed 1.142.6+2.04-1ubuntu26.4 At the GRUB command line, 'echo $prefix' reports /EFI/ubuntu. Running 'strings -a' on /boot/efi/EFI/BOOT/BOOTX64.EFI confirms that this string is hardcoded into the executable. Likewise, for /boot/efi/EFI/neon/grubx64.efi. Both are copies of /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed from the grub-efi-amd64-signed package. The /EFI/ubuntu directory does not exist, instead replaced by /EFI/neon. Re-running 'grub-install' did not fix the problem. At the GRUB command line, the following effected the boot: set prefix=($root)'/EFI/neon' configfile $prefix/grub.cfg I have implemented a workaround by creating /boot/efi/EFI/ubuntu/ and copying over grub.cfg and grubx64.efi from /boot/efi/EFI/neon/.
I have recently downloaded KDE neon 5.26 and Face the same exact bug. Prefix is set to /efi/ubuntu instead of ../neon. Using update-grub then grub-install does not fix the problem. I also tried using the boot-repair utility. I hope this gets prioritized because it seems to be easily fixable.
Thank you for your bug report! However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since before 01/01/2025. Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's. Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report. Thanks for understanding!