empathy-chat crashed with SIGSEGV

[Vide]

I was just trying to open a contact chat from the message notificaction panel

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: empathy 3.6.0.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CrashCounter: 1
Date: Tue Nov 27 10:41:38 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/empathy/empathy-chat
InstallationDate: Installed on 2012-07-12 (138 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/lib/empathy/empathy-chat
SegvAnalysis:
 Segfault happened at: 0x7f729b9867d0: mov 0x8(%rdi),%rax
 PC (0x7f729b9867d0) ok
 source "0x8(%rdi)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
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: empathy-chat crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2012-10-02 (56 days ago)
UserGroups: adm lpadmin sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 _dbus_counter_adjust_size (counter=0x0, delta=173) at ../../dbus/dbus-resources.c:151
 _dbus_message_add_counter_link (message=message@entry=0x36dc150, link=link@entry=0x222b318) at ../../dbus/dbus-message.c:306
 _dbus_message_add_counter (message=0x36dc150, counter=0x222bb60) at ../../dbus/dbus-message.c:338
 _dbus_transport_queue_messages (transport=transport@entry=0x222b5d0) at ../../dbus/dbus-transport.c:1140
 do_reading (transport=transport@entry=0x222b5d0) at ../../dbus/dbus-transport-socket.c:851

[Bilal Shahid (s9iper1)]

thanks for the bug report
that belongs to telepathy-indicator

[Bilal Shahid (s9iper1)]

assigning to kenvandine i guess the stacktrace has enough info