colord crashed with SIGSEGV

[Mijalce Santa]

it showed that it crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: colord 0.1.11-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
Date: Sat Sep 3 08:23:57 2011
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7fdd47d7757e: cmpq $0x0,0x70(%rdi)
 PC (0x7fdd47d7757e) ok
 source "$0x0" ok
 destination "0x70(%rdi)" (0x00000071) 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 oneiric on 2011-09-02 (0 days ago)
UserGroups: scanner

[Apport retracing service (apport)]

StacktraceTop:
 _dbus_message_add_counter_link (message=0x1, link=0x25fc120) at ../../dbus/dbus-message.c:233
 _dbus_message_add_counter (message=0x1, counter=0x25f8f30) at ../../dbus/dbus-message.c:278
 _dbus_transport_queue_messages (transport=0x25f89f0) at ../../dbus/dbus-transport.c:1138
 do_reading (transport=0x25f89f0) at ../../dbus/dbus-transport-socket.c:851
 do_reading (transport=0x25f89f0) at ../../dbus/dbus-transport-socket.c:706

[David Clayton (dcstar)]

Affects (at least) 71 people and masses of bug reports which duplicate this. Nothing changed since June 2012.

I am getting a little tired of this error myself, any danger of a fix in the next decade?

[JW (arch0njw)]

Error still persisting. Is there any fix to this?