colord crashed with SIGSEGV

Bug #979398 reported by Nick Brooker
This bug report is a duplicate of:  Bug #840123: colord crashed with SIGSEGV. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
colord (Ubuntu)
New
Undecided
Unassigned

Bug Description

Just logged into Gnome session. Update manager and another program with an adobe flash update were also started.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: colord 0.1.16-2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu1
Architecture: amd64
Date: Thu Apr 12 10:02:28 2012
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f02c95a459e: cmpq $0x0,0x70(%rdi)
 PC (0x7f02c95a459e) ok
 source "$0x0" ok
 destination "0x70(%rdi)" (0x00000070) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: colord
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: colord crashed with SIGSEGV
UpgradeStatus: Upgraded to precise on 2012-03-20 (22 days ago)
UserGroups: scanner

Revision history for this message
Nick Brooker (nickbrooker) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #840123, so 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
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.