package linux-image-2.6.32-24-generic 2.6.32-24.42 failed to install/upgrade: el subproceso script post-installation instalado devolvió el código de salida de error 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
i cant update the kernel, also when i reboot the computer i cant start with the newest kernel i had before the update
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: pablo 1157 F...m pulseaudio
CRDA: Error: [Errno 2] No existe el archivo o directorio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf96fc000 irq 16'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,
Controls : 37
Simple ctrls : 20
Date: Mon Sep 6 00:27:18 2010
ErrorMessage: el subproceso script post-installation instalado devolvió el código de salida de error 1
HibernationDevice: RESUME=
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdLine: root=UUID=
RelatedPackageV
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-
WpaSupplicantLog:
dmi.bios.date: 12/10/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.20
dmi.board.name: Wolfdale1333-D667.
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
tags: | added: acpi-table-checksum |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 489983, so it 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.