Bug 387390 - Returned to the GRUB menu during EFI boot
Summary: Returned to the GRUB menu during EFI boot
Status: RESOLVED FIXED
Alias: None
Product: neon
Classification: KDE Neon
Component: Live/Install images (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR critical
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-28 09:46 UTC by Jarl Gjessing
Modified: 2017-11-30 19:52 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jarl Gjessing 2017-11-28 09:46:20 UTC
The latest versions fails to boot.
After installing I end up in grub menu :-(

I've tied the 1611 and the 2311 ISO user edition images with the same result
Comment 1 Andres Betts 2017-11-28 15:26:51 UTC
Same is happening to me. Grub fails to install during Calamares. After that the installation stops and closes. Then you boot and you are sent to the grub prompt. This appears to have with systems using EFI boot. This is happening in all versions of Neon, unstable daily, stable, lts, etc. Please check.
Comment 2 Jonathan Riddell 2017-11-28 15:40:38 UTC
fix is compiling
Comment 3 Andres Betts 2017-11-29 03:14:07 UTC
When installing from the live cd I get this error after Calamares tries to update initframs

Boost.Python error in job "bootloader".
<class 'subprocess.CalledProcessError'>
Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=KDE_neon_Developer_Edition_(Unstable_Branches) --force' returned non-zero exit status 1
Traceback:
  File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py", line 351, in run
    prepare_bootloader(fw_type)

  File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py", line 322, in prepare_bootloader
    install_grub(efi_directory, fw_type)

  File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py", line 253, in install_grub
    "--force"])

  File "<string>", line 2, in <module>

This error is well-documented online. However, if you try the suggested fixes, it still fails to launch Neon automatically and you are sent to the grub prompt.
Comment 4 Andres Betts 2017-11-29 03:14:36 UTC
I guess I should have said I tried git unstable for 28 Nov release.
Comment 5 Jonathan Riddell 2017-11-29 15:59:38 UTC
fixed in neon-useredition-20171129-1051-amd64.iso
Comment 6 Andres Betts 2017-11-30 06:23:11 UTC
Just one more thing, Dev Unstable builds are not updated to the Nov 29 version. Still on Nov 28. The other 3 releases are on Nov 29.

https://files.kde.org/neon/images/neon-devedition-gitunstable/current/
Comment 7 tungtanium 2017-11-30 19:28:12 UTC
Thanks a lot for tagging me and providing the fix.

(In reply to Andres Betts from comment #3)
> When installing from the live cd I get this error after Calamares tries to
> update initframs
> 
> Boost.Python error in job "bootloader".
> <class 'subprocess.CalledProcessError'>
> Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi
> --bootloader-id=KDE_neon_Developer_Edition_(Unstable_Branches) --force'
> returned non-zero exit status 1
> Traceback:
>   File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py",
> line 351, in run
>     prepare_bootloader(fw_type)
> 
>   File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py",
> line 322, in prepare_bootloader
>     install_grub(efi_directory, fw_type)
> 
>   File "/usr/lib/x86_64-linux-gnu/calamares/modules/bootloader/main.py",
> line 253, in install_grub
>     "--force"])
> 
>   File "<string>", line 2, in <module>
> 
> This error is well-documented online. However, if you try the suggested
> fixes, it still fails to launch Neon automatically and you are sent to the
> grub prompt.

Just out of curiosity, how can you capture these error during installation? Which ISO are you using? @Andres

Thanks
Comment 8 Jonathan Riddell 2017-11-30 19:41:44 UTC
dev unstable builds use calamares by default and that does still have the issue Andreas reports.  A workaround is to  apt install ubiquity-frontend-kde  and use ubiquity.
Comment 9 Andres Betts 2017-11-30 19:52:26 UTC
Sounds good!