Ubuntu
blcr package

blcr-dkms 0.8.2-15ubuntu2: blcr kernel module failed to build

Bug #1004996 reported by Ruslan Boev on 2012-05-26

This bug report is a duplicate of: Bug #804943: blcr kernel module failed to build with kernel 3.0 : configure: error: --with-linux argument '3.0-x' is neither a kernel version string nor a full path. Edit Remove

This bug affects 1 person

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

Bug Description

Appeared after regular 'Software Up to Date' run. Ubuntu 12.04 LTS. It continues to appear when I open Software Update Manager.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: blcr-dkms 0.8.2-15ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
DKMSKernelVersion: 3.2.0-24-generic
Date: Sun May 27 04:05:41 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
PackageVersion: 0.8.2-15ubuntu2
SourcePackage: blcr
Title: blcr-dkms 0.8.2-15ubuntu2: blcr kernel module failed to build
UpgradeStatus: Upgraded to precise on 2012-05-09 (17 days ago)

Tags:

Revision history for this message

Ruslan Boev (indexator) wrote on 2012-05-26:

DKMSBuildLog.txt Edit (6.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (795 bytes, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (6.0 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2012-05-26

tags:

removed: need-duplicate-check

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-05-26:

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 804943, 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.