Ubuntu
blcr package

blcr-dkms 0.8.5-2: blcr kernel module failed to build

Bug #1327545 reported by Joao Constantino on 2014-06-07

This bug report is a duplicate of: Bug #1236154: blcr-dkms 0.8.5-2: blcr kernel module failed to build [configure: error: Unable to use kernel 3.11.0-031100-generic - unable to determine how to call attach_pid()]. Edit Remove

This bug affects 3 people

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

Bug Description

I get this bug after login

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: blcr-dkms
ProcVersionSignature: Ubuntu 3.11.0-23.40-generic 3.11.10.10
Uname: Linux 3.11.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
DKMSKernelVersion: 3.11.0-23-generic
Date: Sat Jun 7 13:27:44 2014
DuplicateSignature: dkms:blcr-dkms:0.8.5-2:configure: error: Unable to use kernel 3.11.0-23-generic - unable to determine how to call attach_pid()
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 0.8.5-2
SourcePackage: blcr
Title: blcr-dkms 0.8.5-2: blcr kernel module failed to build
UpgradeStatus: Upgraded to saucy on 2014-06-02 (4 days ago)

Tags:

Revision history for this message

Joao Constantino (jconstantino) wrote on 2014-06-07:

DKMSBuildLog.txt Edit (16.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-06-19:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in blcr (Ubuntu):
status:	New → Confirmed

Apport retracing service (apport) on 2014-07-01

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2014-07-01:

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