Just had exactly that problem on a 18.04 installation at the end. It was a EFI installation and grub wanted to remove "grub-pc".
As described above, the prerm script tried to db_get the variable grub-pc/chainload_from_menu.lst. grub-pc version is the latest from bionic-update (2.04-1ubuntu35.2). -- prerm ------ #!/bin/bash set -e case "$1" in remove|deconfigure) . /usr/share/debconf/confmodule db_get grub-pc/chainload_from_menu.lst <---- here the scripts aborts if $RET && test -e /boot/grub/menu.lst ; then ... --------------- Because of "set -e", the scripts aborts when the variable is not available. Looking into grub-pc's config script, i find this: db_input high grub-pc/chainload_from_menu.lst || true Maybe this would be a good improvement for the prerm script? The only workaround I think of, is to preseed that variable, hoping it doesn't harm anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/347532 Title: [jaunty] package grub-pc 1.96+20080724-12ubuntu2 failed to install/upgrade: sub-process pre-removal script returned 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/347532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs