Ubuntu
bcmwl package

package bcmwl-kernel-source 5.100.82.38 bdcom-0ubuntu3 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 3

Bug #787253 reported by Nelson Reyes Klein on 2011-05-23

This bug report is a duplicate of: Bug #776439: package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 3 (Error! There are no instances of module: bcmwl). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	bcmwl (Ubuntu)	New	Undecided	Unassigned

Bug Description

i can't activate my wireless broadcom driver in my Compaq V3217la

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
NonfreeKernelModules: nvidia
AptOrdering: bcmwl-kernel-source: Remove
Architecture: i386
Date: Mon May 23 18:09:52 2011
ErrorMessage: el subproceso instalado el script pre-removal devolvió el código de salida de error 3
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 5.100.82.38+bdcom-0ubuntu3 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 3
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Nelson Reyes Klein (n-reyesklein) wrote on 2011-05-23:

Dependencies.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (48.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (300 bytes, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-05-24:

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 #776439, 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. Feel free to continue to report any other bugs you may find.