package linux-image-4.4.0-83-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When I open the Ubuntu Software program, there were updates. So I clicked the update button and it looked like working but it didn't end well. And error report pop up showed, then I just followed the order to report this bug.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.4.0-81-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Date: Thu Jun 29 10:00:16 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 128
HibernationDevice: RESUME=
InstallationDate: Installed on 2016-08-30 (302 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LG Electronics 15ZD960-GX56K
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.
RelatedPackageV
SourcePackage: linux
Title: package linux-image-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2016
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 15ZA1600 X64
dmi.board.
dmi.board.name: 15Z960
dmi.board.vendor: LG Electronics
dmi.board.version: FAB1
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: LG Electronics
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: 15ZD960-GX56K
dmi.product.
dmi.sys.vendor: LG Electronics
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1701085, so 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.