colord crashed with SIGSEGV in link_before()

[Albert Damen]

The crash message popped up right after logging in, without noticeable impact.
According to the time stamp of the crash file, the crash happened during this boot, it was not a crash during the previous shutdown.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: colord 0.1.12-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Fri Sep 30 09:52:21 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: 0x7f04ae60863c <_dbus_list_prepend_link+12>: mov (%rax),%rdx
 PC (0x7f04ae60863c) ok
 source "(%rax)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: colord
StacktraceTop:
 link_before (link=0x7f04a804b348, before_this_link=0x1, list=0x7f04a8057170) at ../../dbus/dbus-list.c:120
 _dbus_list_prepend_link (list=<optimized out>, link=<optimized out>) at ../../dbus/dbus-list.c:313
 _dbus_list_append_link (list=0x7f04a8057170, link=<optimized out>) at ../../dbus/dbus-list.c:295
 _dbus_message_add_counter_link (message=0x7f04a8057100, link=0x7f04a804b348) at ../../dbus/dbus-message.c:249
 _dbus_message_add_counter (message=0x7f04a8057100, counter=0x7f04a8057100) at ../../dbus/dbus-message.c:278
Title: colord crashed with SIGSEGV in link_before()
UpgradeStatus: Upgraded to oneiric on 2011-06-02 (119 days ago)
UserGroups: scanner

[Apport retracing service (apport)]

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