Ubuntu
blcr package

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

Bug #919593 reported by cabanas on 2012-01-21

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

Description: Ubuntu 11.10
Release: 11.10

blcr-dkms:
  Instalados: 0.8.2-15ubuntu1
  Candidato: 0.8.2-15ubuntu1
  Tabla de versión:
*** 0.8.2-15ubuntu1 0
        500 http://es.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: blcr-dkms
ProcVersionSignature: Ubuntu 3.0.0-15.25-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
DKMSKernelVersion: 3.0.0-15-generic
Date: Sat Jan 21 10:19:08 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
PackageArchitecture: all
PackageVersion: 0.8.2-15ubuntu1
SourcePackage: blcr
Title: blcr-dkms 0.8.2-15ubuntu1: blcr kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

cabanas (r-cabanas) wrote on 2012-01-21:

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

Apport retracing service (apport) on 2012-01-21

tags:

removed: need-duplicate-check

Revision history for this message

Ubuntu Foundations Team Bug Bot (crichton) wrote on 2012-01-21:

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.