On Thu, Jan 07, 2016 at 07:14:48PM -0000, Marc Deslauriers wrote: > Wouldn't the grub2 package simply be held back if the proper version > required by grub2-signed isn't available?
Not in all cases. > Why did the grub2-signed binary package get uninstalled during the > update? This is allowable when running 'apt-get dist-upgrade', which is presumably how the affected users have been applying updates. When using update-manager, we have more control to avoid accidental removal of packages when applying updates. When a user explicitly invokes apt-get, we don't have control over this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528345 Title: grub or kernel update broke Secure Boot by putting grubx64.efi instead of shimx64.efi in EFI boot order To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1528345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
