package linux-image-4.10.0-26-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debconf (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I restarted my laptop, after installed kodi addons, it stopped working as soon after
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-
ProcVersionSign
Uname: Linux 4.10.0-24-generic i686
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC0D0c: mini 1467 F...m pulseaudio
/dev/snd/pcmC0D0p: mini 1467 F...m pulseaudio
/dev/snd/
Date: Fri Jun 30 20:34:04 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 128
HibernationDevice: RESUME=
InstallationDate: Installed on 2017-06-16 (14 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
MachineType: TOSHIBA Satellite A135
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
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
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/12/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.90
dmi.board.name: IAKAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: Satellite A135
dmi.product.
dmi.sys.vendor: TOSHIBA
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.