colord crashed with SIGSEGV

[Stephen Rees-Carter]

Occured after a unity --reset &

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: colord 0.1.11-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
Date: Tue Sep 6 10:00:52 2011
ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110812)
ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7fcfea45d950: mov 0x10(%rdi),%rdx
 PC (0x7fcfea45d950) ok
 source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
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
 ?? () 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-08-13 (24 days ago)
UserGroups: scanner

[Apport retracing service (apport)]

StacktraceTop:
 _dbus_counter_adjust_unix_fd (counter=0x0, delta=0) at ../../dbus/dbus-resources.c:181
 _dbus_message_add_counter (message=0x7fcfe40501a0, counter=0x7fcfe4056b70) at ../../dbus/dbus-message.c:278
 _dbus_transport_queue_messages (transport=0x7fcfe4056630) at ../../dbus/dbus-transport.c:1138
 do_reading (transport=0x7fcfe4056630) at ../../dbus/dbus-transport-socket.c:851
 do_reading (transport=0x7fcfe4056630) at ../../dbus/dbus-transport-socket.c:706

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[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 #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.