Ubuntu
calamares package

  1. Bug #2043161
  2. Comment #6

Comment 6 for bug 2043161

Revision history for this message
Simon Quigley (tsimonq2) wrote :

/pool/main/g/grub2/grub-efi_2.12~rc1-12ubuntu4_amd64.deb
/pool/main/g/grub2/grub-efi-ia32_2.12~rc1-12ubuntu4_amd64.deb
/pool/main/g/grub2/grub-efi-ia32-bin_2.12~rc1-12ubuntu4_amd64.deb
/pool/main/g/grub2-signed/grub-efi-amd64-signed_1.199+2.12~rc1-12ubuntu2_amd64.deb
/pool/main/g/grub2-unsigned/grub-efi-amd64_2.12~rc1-12ubuntu2_amd64.deb
/pool/main/g/grub2-unsigned/grub-efi-amd64-bin_2.12~rc1-12ubuntu2_amd64.deb

So, we either have a weird case of an i386 bootloader on an amd64 system and something exploded, or this could also be an ephemeral issue.

Can you continuously reproduce it on that machine? If so, can you maybe try running that apt command manually to see if maybe we need some more *dependencies* added to the no-network GRUB package list?