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
Error occured doing a software upgrate via Ubuntu Software panel
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.8.0-56-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
Date: Thu Jun 29 17:06:13 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 128
HibernationDevice: RESUME=
InstallationDate: Installed on 2017-06-25 (4 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
Lsusb:
Bus 002 Device 002: ID 05ca:18a0 Ricoh Co., Ltd
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Dell Inc. Studio XPS 1340
ProcFB:
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/08/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0K171D
dmi.board.vendor: Dell Inc.
dmi.board.version: A15
dmi.chassis.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Studio XPS 1340
dmi.product.
dmi.sys.vendor: Dell Inc.
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 #1701182, 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.