package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128

Bug #1784218 reported by Ross Ylitalo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
New
Undecided
Unassigned
grub2 (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was booting into Ubuntu, using the default option in grub, and was able to enter my password in the login screen, but the displays started flickering a lot, and there were a lot of repeated text messages (it switched into text mode). I finally did a hard reset and tried booting into ubuntu - generic which seemed to work. There was a prompt from apt to update, so I did, and then I got this error message.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64 2.02-2ubuntu8.2
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Jul 29 06:00:14 2018
ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128
InstallationDate: Installed on 2017-11-11 (259 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=a68c1ee5-ce8a-4eed-b95f-7625f3118746 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.3
SourcePackage: grub2
Title: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 128
UpgradeStatus: Upgraded to bionic on 2018-06-23 (35 days ago)

Revision history for this message
Ross Ylitalo (ross-ylitalo) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Phillip Susi (psusi) wrote :

Looks like some more debconf breakage:

Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66, <GEN0> line 10.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67, <GEN0> line 10.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68, <GEN0> line 10.
Use of uninitialized value in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 202, <GEN0> line 10.
Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66, <GEN0> line 10.
Use of uninitialized value $reply in concatenation (.) or string at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 67, <GEN0> line 10.
Use of uninitialized value $reply in split at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 68, <GEN0> line 10.
Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 212, <GEN0> line 10.
Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, <GEN0> line 10.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.