package grub2-common 2.02~beta2-9ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Carlos Cardozo]

Been happening for a while, right after Software Updater runs. Not sure why, not sure if this is really a bug.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: grub2-common 2.02~beta2-9ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic i686
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: i386
Date: Fri Apr 10 10:26:21 2015
DuplicateSignature: package:grub2-common:2.02~beta2-9ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
InstallationDate: Installed on 2012-06-09 (1035 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=eda30047-fea2-49f9-8afe-5ef4915af23e ro quiet splash vt.handoff=7
SourcePackage: grub2
Title: package grub2-common 2.02~beta2-9ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
UpgradeStatus: Upgraded to trusty on 2014-04-24 (350 days ago)

[Mathieu Trudel-Lapierre (cyphermox)]

What happens if you run 'dpkg-reconfigure grub2-common' ?

[Carlos Cardozo (ccardozo)]

It comes back with:

no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
/usr/sbin/dpkg-reconfigure: grub2-common is broken or not fully installed

On 05/08/2015 01:48 PM, Mathieu Trudel-Lapierre wrote:
> What happens if you run 'dpkg-reconfigure grub2-common' ?
>
> ** Changed in: grub2 (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: grub2 (Ubuntu)
> Importance: Undecided => Medium
>

[Launchpad Janitor (janitor)]

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]