Ubuntu
fglrx-installer package

fglrx 2:8.960-0ubuntu1.1: fglrx kernel module failed to build

Bug #1214533 reported by Bruce Stough on 2013-08-20

This bug report is a duplicate of: Bug #938489: package fglrx 2:8.723.1-0ubuntu6 failed to install/upgrade: fglrx kernel module failed to build [Makefile: No such file or directory]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	fglrx-installer (Ubuntu)	New	Undecided	Unassigned

Bug Description

Update-manager was trying to do some updates, including the kernel.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx 2:8.960-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-51.77-generic 3.2.48
Uname: Linux 3.2.0-51-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
DKMSKernelVersion: 3.2.0-52-generic
Date: Tue Aug 20 13:44:44 2013
InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta amd64 (20120228)
MarkForUpload: True
PackageVersion: 2:8.960-0ubuntu1.1
SourcePackage: fglrx-installer
Title: fglrx 2:8.960-0ubuntu1.1: fglrx kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Bruce Stough (sbsrs) wrote on 2013-08-20:

DKMSBuildLog.txt Edit (714 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (3.8 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (686 bytes, text/plain; charset="utf-8")
FglrxBuildLog.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2013-08-20

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-08-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 938489, 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.