colord crashed with SIGSEGV in dbus_message_get_reply_serial()

[J Cord]

This will probably get marked as duplicate of an ongoing problem with colord crashing which was fixed in 12.04 but not fixed, and now having the same thing in 12.10 Q, Happens almost every login , reboot, I had just rebooted from todays updates after Software Updater (sic), crashed without updating, and had opened terminal to complete the update before I could , Colord crashed, and so here I am as apport popped up. Anyway it's the same old bug, just carried over to Quantel. I tried to file a bug report on Software Updater (sic), but apport reports already known bug to developers.

Good Luck, and Best Wishes

Ubuntu 12.10 Alpha 1, Quantal

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: colord 0.1.16-2
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
Uname: Linux 3.4.0-5-generic x86_64
ApportVersion: 2.2.2-0ubuntu2
Architecture: amd64
Date: Wed Jun 13 15:02:27 2012
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2)
ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7fc6d7ffd8d5: mov (%r12,%rdx,1),%edx
 PC (0x7fc6d7ffd8d5) ok
 source "(%r12,%rdx,1)" (0x000000aa) 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: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

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.