package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1751416 reported by Vlad on 2018-02-24
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Undecided
Unassigned

Bug Description

It is appeared after installing an updates on fresh ubuntu 17.10 installation

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: grub-common 2.02~beta3-4ubuntu7.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Sat Feb 24 09:00:33 2018
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2018-02-23 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic root=UUID=b38738b2-7475-4dad-a28f-be6621cecbb5 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5.1
SourcePackage: grub2
Title: package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Vlad (sorosand) wrote :
tags: removed: need-duplicate-check
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1705345, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Michael Poole (mdpoole) wrote :

The complaint here -- apparently trying to run "which python" failed -- makes it look quite different than the "plymouth --ping" issue in bug 1705345. What is the basis for marking this as a duplicate?

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

Other bug subscribers