package linux-image-4.15.0-34-generic 4.15.0-34.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/x-grub-legacy-ec2 exited with return code 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grub-legacy-ec2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
error occurred while updating
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA:
global
country IN: DFS-UNSET
(2402 - 2482 @ 40), (N/A, 20), (N/A)
(5150 - 5350 @ 160), (N/A, 23), (N/A)
(5725 - 5875 @ 80), (N/A, 23), (N/A)
Date: Sat Sep 15 19:12:32 2018
ErrorMessage: run-parts: /etc/kernel/
MachineType: Dell Inc. Vostro 15-3568
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
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.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageV
SourcePackage: grub-legacy-ec2
Title: package linux-image-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.07.00
dmi.board.name: 01Y1RD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.family: Vostro
dmi.product.name: Vostro 15-3568
dmi.sys.vendor: Dell Inc.
tags: | removed: need-duplicate-check |
Hi,
I can't get from the logs why the issue happen to begin with, but I found a report that seemed quite similar which has suggestions how to resolve it.
So I'd recommend to take a look at https:/ /askubuntu. com/questions/ 1040974/ ubuntu- server- 18-04-apt- get-fails
For a bug, we'd have to find something to fix, which with the logs so far I don't see.
If the above does not help you I'd ask you to try finding how to recreate this issue on a clean system - in that case we could more likely take a look and check for the root cause to be solved.
Until then, i'll mark the bug incomplete needing that info.
But hopefully the link above just gets you fixed.