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

Bug #1263320 reported by guziy
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
blcr (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

KDE was constantly asking if I want to report this on login.
Description: Ubuntu 13.10
Release: 13.10

blcr-dkms:
  Installed: 0.8.5-2
  Candidate: 0.8.5-2
  Version table:
 *** 0.8.5-2 0
        500 http://ca.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: blcr-dkms 0.8.5-2
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
DKMSKernelVersion: 3.11.0-15-generic
Date: Sat Dec 14 00:17:15 2013
DuplicateSignature: dkms:blcr-dkms:0.8.5-2:configure: error: Unable to use kernel 3.11.0-15-generic - unable to determine how to call attach_pid()
InstallationDate: Installed on 2010-03-19 (1373 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
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 2013-10-18 (64 days ago)

Revision history for this message
guziy (guziy-sasha) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in blcr (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.