package grub-pc 2.02~beta2-9ubuntu1.2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)

Bug #1461088 reported by djfkc on 2015-06-02
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Undecided
Unassigned

Bug Description

Doing apt-get upgrade, terminal hung at:
Setting up grub-pc (2.02~beta2-9ubuntu1.2) ...

System still responsive but did not wish to trust an attempt to reboot since it seemed to be a grub issue.
Found command dpkg-reconfigure grub-pc at:
http://askubuntu.com/questions/510434/grub-install-fails-after-upgrading-from-12-04-to-14-04-grub-pc-is-broken

Result:
$ sudo dpkg-reconfigure grub-pc
debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

Found fuser command at:
http://askubuntu.com/questions/136881/debconf-dbdriver-config-config-dat-is-locked-by-another-process-resource-t

Result:
$ sudo fuser -vik /var/cache/debconf/config.dat
                     USER PID ACCESS COMMAND
/var/cache/debconf/config.dat:
                     root 26740 F.... frontend
Kill process 26740 ? (y/N) y

Terminal running apt-get upgrade results after this command:
Setting up grub-pc (2.02~beta2-9ubuntu1.2) ...
dpkg: error processing package grub-pc (--configure):
 subprocess installed post-installation script was killed by signal (Killed)
Setting up libreoffice-help-en-us (1:4.2.8-0ubuntu1) ...
Errors were encountered while processing:
 grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug report background information requested:
$ lsb_release -rd
Description: Ubuntu 14.04.2 LTS
Release: 14.04
david@Ubuntu-B:~$ apt-cache policy pkgname
N: Unable to locate package pkgname
david@Ubuntu-B:~$ sudo apt-cache policy pkgname
N: Unable to locate package pkgname
david@Ubuntu-B:~$ sudo apt-cache policy grub-pc
grub-pc:
  Installed: 2.02~beta2-9ubuntu1.2
  Candidate: 2.02~beta2-9ubuntu1.2
  Version table:
 *** 2.02~beta2-9ubuntu1.2 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages
        100 /var/lib/dpkg/status
     2.02~beta2-9 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: grub-pc 2.02~beta2-9ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
Uname: Linux 3.13.0-53-generic i686
ApportVersion: 2.14.1-0ubuntu3.11
AptOrdering:
 libreoffice-help-en-us: Install
 grub-pc: Configure
 libreoffice-help-en-us: Configure
Architecture: i386
Date: Tue Jun 2 07:50:19 2015
DpkgHistoryLog:

DpkgTerminalLog:

ErrorMessage: subprocess installed post-installation script was killed by signal (Killed)
InstallationDate: Installed on 2014-05-16 (382 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=7fa4f6d4-e950-438e-b092-ab4db21557f1 ro quiet splash vt.handoff=7
SourcePackage: grub2
Title: package grub-pc 2.02~beta2-9ubuntu1.2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)
UpgradeStatus: Upgraded to trusty on 2014-07-29 (307 days ago)

djfkc (djfkc) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in grub2 (Ubuntu):
status: New → Confirmed
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1461088

tags: added: iso-testing
thierman (thierman) wrote :

Ran into bug while trying updater was applying recent updates. Hung, had to kill off process and clear locks. Ran
 dpkg --configure -a

In the terminal the last message displayed that I could not click ok on was:
┌──────────────────────────┤ Configuring grub-pc ├──────────────────────────┐
 │ │
 │ which devices you'd like grub-install to be automatically run for, if
 │ any.
 │
 │ Running grub-install automatically is recommended in most situations, to
 │ prevent the installed GRUB core image from getting out of sync with GRUB
 │ modules or grub.cfg.
 │
 │ If you're unsure which drive is designated as boot drive by your BIOS,
 │ it is often a good idea to install GRUB to all of them.
 │
 │ Note: it is possible to install GRUB to partition boot records as well,
 │ and some appropriate partitions are offered here. However, this forces
 │ GRUB to use the blocklist mechanism, which makes it less reliable, and
 │ therefore is not recommended.
 │
 │ <Ok>
 │ │
 └───────────────────────────────────────────────────────────────────────────

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers