Ubuntu
blcr package

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

Bug #1004330 reported by Robert Norris on 2012-05-25

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

I'm not entirely sure what happened exactly. After installing Elmer and configuring it, a crash notification popped up. Elmer now crashes when I try to start it. I will try purging the package and re-installing it.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: blcr-dkms 0.8.2-15ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
DKMSKernelVersion: 3.2.0-23-generic
Date: Thu May 24 23:42:20 2012
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
PackageVersion: 0.8.2-15ubuntu2
SourcePackage: blcr
Title: blcr-dkms 0.8.2-15ubuntu2: blcr kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Robert Norris (rnorris7756) wrote on 2012-05-25:

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-25

tags:

removed: need-duplicate-check

Revision history for this message

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

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.