After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685831 - empathy-chat crashed with SIGSEGV
empathy-chat crashed with SIGSEGV
Status: RESOLVED INCOMPLETE
Product: empathy
Classification: Core
Component: Chat
3.6.x
Other Linux
: Normal critical
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2012-10-09 18:41 UTC by Bilal Shahid
Modified: 2012-12-28 10:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bilal Shahid 2012-10-09 18:41:48 UTC
Originally reported at:
  https://bugs.launchpad.net/bugs/1061141

This happened after opening 2 new chats from the message indicator (2 new Tabs) and begin typing.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: empathy 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic x86_64
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Oct  3 20:02:25 2012
ExecutablePath: /usr/lib/empathy/empathy-chat
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64+mac (20120922)
ProcCmdline: /usr/lib/empathy/empathy-chat
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Comment 1 Bilal Shahid 2012-10-09 18:42:00 UTC


  • #0 __memmove_ssse3_back
    at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S line 2010
  • #1 memmove
    at /usr/include/x86_64-linux-gnu/bits/string3.h line 58
  • #2 delete
    at ../../dbus/dbus-string.c line 1175
  • #3 delete
    at ../../dbus/dbus-string.c line 2695
  • #4 _dbus_string_delete
    at ../../dbus/dbus-string.c line 1200
  • #5 load_message
    at ../../dbus/dbus-message.c line 4171
  • #6 _dbus_message_loader_queue_messages
    at ../../dbus/dbus-message.c line 4245
  • #7 _dbus_transport_get_dispatch_status
    at ../../dbus/dbus-transport.c line 1101
  • #8 _dbus_transport_queue_messages
    at ../../dbus/dbus-transport.c line 1128
  • #9 do_reading
    at ../../dbus/dbus-transport-socket.c line 851
  • #10 do_reading
    at ../../dbus/dbus-transport-socket.c line 706
  • #11 socket_handle_watch
    at ../../dbus/dbus-transport-socket.c line 932
  • #12 _dbus_transport_handle_watch
    at ../../dbus/dbus-transport.c line 885
  • #13 _dbus_connection_handle_watch
    at ../../dbus/dbus-connection.c line 1515
  • #14 dbus_watch_handle
    at ../../dbus/dbus-watch.c line 700
  • #15 io_handler_dispatch
    at dbus-gmain.c line 221
  • #16 g_main_dispatch
    at /build/buildd/glib2.0-2.34.0/./glib/gmain.c line 2715
  • #17 g_main_context_dispatch
    at /build/buildd/glib2.0-2.34.0/./glib/gmain.c line 3219
  • #18 g_main_context_iterate
    at /build/buildd/glib2.0-2.34.0/./glib/gmain.c line 3290
  • #19 g_main_context_iteration
    at /build/buildd/glib2.0-2.34.0/./glib/gmain.c line 3351
  • #20 g_application_run
    at /build/buildd/glib2.0-2.34.0/./gio/gapplication.c line 1620
  • #21 main
    at empathy-chat.c line 162

Comment 2 Guillaume Desmottes 2012-10-11 13:34:47 UTC
Looks like either a libdbus bug or, more likely, a memory corruption. Is that reproducible?
Comment 3 Fabio Durán Verdugo 2012-12-09 02:53:09 UTC
Hi Bilal, can you reply the comment 2 ?, thank
Comment 4 Guillaume Desmottes 2012-12-28 10:04:52 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!