Ubuntu
lttng-modules package

lttng-modules-dkms 2.4.0-1ubuntu1: lttng-modules kernel module failed to build

Bug #1363042 reported by Jürgen Altschäffl on 2014-08-29

This bug report is a duplicate of: Bug #1396758: lttng-modules-dkms fails to build on updated kernel. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	lttng-modules (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

lttng-modules

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: lttng-modules-dkms 2.4.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
DKMSKernelVersion: 3.13.0-34-generic
Date: Thu Aug 28 18:16:42 2014
DuplicateSignature: dkms:lttng-modules-dkms:2.4.0-1ubuntu1:/var/lib/dkms/lttng-modules/2.4.0/build/probes/../instrumentation/events/lttng-module/../../../probes/lttng-events.h:151:6: error: conflicting types for ‘trace_block_rq_complete’
InstallationDate: Installed on 2014-05-21 (99 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
PackageVersion: 2.4.0-1ubuntu1
SourcePackage: lttng-modules
Title: lttng-modules-dkms 2.4.0-1ubuntu1: lttng-modules kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Jürgen Altschäffl (ja-on) wrote on 2014-08-29:

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

Apport retracing service (apport) on 2014-08-29

tags:

removed: need-duplicate-check

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-08-30:

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

Changed in lttng-modules (Ubuntu):
status:	New → Confirmed

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2014-09-03:

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