package linux-image-2.6.35-22-generic 2.6.35-22.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
The steps required to duplicate this bug are as follows
Prepare a USB for install (Format 8GB with 4GB for persistence)
Install Ubuntu 10.10 via iso file downloaded from Ubuntu website
Boot computer from USB stick
Go to System>
Install update labelled "Linux-
The crash will occur. I have done this multiple times and crashed every time
ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AptOrdering:
linux-
linux-
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x2a200000 irq 46'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,
Controls : 9
Simple ctrls : 7
Date: Sat Jan 1 03:01:10 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 2
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: TOSHIBA TECRA M5
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: noprompt cdrom-detect/
RelatedPackageV
SourcePackage: linux
Title: package linux-image-
dmi.bios.date: 12/26/2006
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.20
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: TECRA M5
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.