colord crashed with SIGSEGV in dbus_message_get_reply_serial()

Bug #957856 reported by Robert Avant
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
colord (Ubuntu)
New
Undecided
Unassigned

Bug Description

Bug occured while using Computer Janitor after updateing files 17 March 2012

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: colord 0.1.16-2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Sat Mar 17 11:34:29 2012
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f3ad1ac08d5: mov (%r12,%rdx,1),%edx
 PC (0x7f3ad1ac08d5) ok
 source "(%r12,%rdx,1)" (0x000000be) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading 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
 dbus_message_get_reply_serial () 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 in dbus_message_get_reply_serial()
UpgradeStatus: Upgraded to precise on 2012-03-13 (3 days ago)
UserGroups: scanner

Revision history for this message
Robert Avant (robertj-avant) 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 #844286, 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.