package linux-image-4.15.0-44-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 128

Bug #1817077 reported by John Rhines
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debconf (Ubuntu)
Confirmed
Undecided
Unassigned
grub-legacy-ec2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I applied an system update and was presented with this error after the next login.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-44-generic (not installed)
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Thu Feb 14 00:00:24 2019
ErrorMessage: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 128
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=36f6b4c3-1f42-11e9-99c9-00155d195067 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt 1.6.8
RfKill:

SourcePackage: grub-legacy-ec2
Title: package linux-image-4.15.0-44-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 128
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2012
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v1.0
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v1.0
dmi.chassis.asset.tag: 0298-0271-9062-6147-4258-1509-89
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Hyper-V UEFI Release v1.0
dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
dmi.product.family: Virtual Machine
dmi.product.name: Virtual Machine
dmi.product.version: Hyper-V UEFI Release v1.0
dmi.sys.vendor: Microsoft Corporation

Revision history for this message
John Rhines (bullitt420) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi John,
the report has a lot of red herrings (all the error device is in use), but IMHO in the log the error that you hit was.

  Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66

That is a known and unfortunate issue, as it occurs every now and then and sometimes is fixed but seems to come back - often with hard to analyze (and thereby hard to identify and fix) root causes.

It all seems like bug 1646739 to me, but since that was fixed in bug 1679435 it must be a new trigger for the same symptom.

In any case it is in debconf, so I add a bug task - but I also set it to incomplete as we'd need more information why/how it was triggered for you.

The only good side for now, usually it is a one off error that does work fine when retrying.

Changed in grub-legacy-ec2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in debconf (Ubuntu):
status: New → Confirmed
dioulde balde (dbalde)
Changed in grub-legacy-ec2 (Ubuntu):
status: Incomplete → In Progress
status: In Progress → Confirmed
Revision history for this message
dioulde balde (dbalde) wrote :

Prévisualisation du noyau 5.3 disponible en tant que noyau Linux-aws-edge.

Revision history for this message
Lucas Kanashiro (lucaskanashiro) wrote :

@dbalde, send messages here in English please. I could translate you comment but your attachment make me think whether it is just a spam message.

Anyway, you did not provide much more info, so I'll follow @cpaelzer and mark grub-legacy-ec2 as invalid again. If you have information to provide please do it and we can reconsider it.

Changed in grub-legacy-ec2 (Ubuntu):
status: Confirmed → Invalid
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.