package grub-pc-bin 2.04-1ubuntu26.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub2 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After Upgrading to lastest LTS the software updater
did not work when I initiate, it states it can not update due to
a problem "Failed to download repository information"
"Check your internet connection" Internet was fine.
When the updater acts on it's own, it seems to in update.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: grub-pc-bin 2.04-1ubuntu26.2
ProcVersionSign
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu27.4
AptOrdering:
grub-common:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckR
Date: Sun Aug 2 20:41:24 2020
DuplicateSignature:
package:
Setting up grub2-common (2.04-1ubuntu26.2) ...
dpkg: error processing package grub-pc-bin (--configure):
package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
InstallationDate: Installed on 2020-01-22 (193 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
ProcCmdLine: BOOT_IMAGE=
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
SourcePackage: grub2
Title: package grub-pc-bin 2.04-1ubuntu26.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.