package blcr-dkms 0.8.2-15ubuntu1 failed to install/upgrade: blcr kernel module failed to build

[jamesgoodsell]

Trying to upgrade form virtualbox 4.0.4 via ubuntu 11.04 repositories to virtualbox 4.0.6 via ppa installed with following commands:

echo "deb http://download.virtualbox.org/virtualbox/debian $(lsb_release -sc) contrib" | sudo tee /etc/apt/sources.list.d/virtualbox.list
wget -q http://download.virtualbox.org/virtualbox/debian/oracle_vbox.asc -O- | sudo apt-key add -

Ran synaptic, updated, and installed virtualbox 4.0.6 from synaptic. NOTE: Already had Windows XP installed and updated in virtualbox 4.0.4 but problems with audio motivated upgrade to 4.0.6 with hope that Windows reinstall would not be necessary. Instead ended up with this problem and virtualbox does not show in accessories menu. Also note that previous to all this I upgraded from ubuntu studio 10.10 to ubuntu studio 11.04 therefore running with generic kernel. When installing virtualbox 4.0.6 noticed recommended installs from synaptic included linux server and virtual headers which I marked for installation. My plan now is to back track to virtual 4.0.4 if possible, remove virtualbox ppa and try other solutions for audio problem in virtualboxed Windows.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: blcr-dkms 0.8.2-15ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Mon May 9 15:46:39 2011
ErrorMessage: blcr kernel module failed to build
InstallationMedia: Ubuntu-Studio 10.10 "Maverick Meerkat" - Release amd64 (20101008)
PackageArchitecture: all
PackageVersion: 0.8.2-15ubuntu1
SourcePackage: blcr
Title: package blcr-dkms 0.8.2-15ubuntu1 failed to install/upgrade: blcr kernel module failed to build
UpgradeStatus: Upgraded to natty on 2011-05-03 (5 days ago)

[Robert Roth (evfool)]

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 #762996, 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.