empathy-chat crashed with SIGSEGV in g_str_hash()

[yohgaz]

this bug appears when it's impossible to reconnect at facebook. When i close a chat facebook with a personne, all of windows chat closed

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic i686
ApportVersion: 1.90-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Mon Jan 16 19:19:18 2012
ExecutablePath: /usr/lib/empathy/empathy-chat
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: /usr/lib/empathy/empathy-chat
SegvAnalysis:
 Segfault happened at: 0xe105ba <g_str_hash+10>: movzbl (%ecx),%edx
 PC (0x00e105ba) ok
 source "(%ecx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_str_hash () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libgee.so.2
 ?? () from /usr/lib/libgee.so.2
 gee_abstract_map_has_key () from /usr/lib/libgee.so.2
 gee_map_has_key () from /usr/lib/libgee.so.2
Title: empathy-chat crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 g_str_hash (v=0x0) at /build/buildd/glib2.0-2.31.8/./glib/ghash.c:1709
 gee_hash_map_lookup_node (self=0x8fd0090, key=0x0) at hashmap.c:928
 gee_hash_map_real_has_key (base=0x8fd0090, key=0x0) at hashmap.c:967
 gee_abstract_map_has_key (self=0x8fd0090, key=0x0) at abstractmap.c:313
 gee_map_has_key (self=0x8fd0090, key=0x0) at map.c:270

[Bilal Shahid (s9iper1)]

Thank you for taking time in filing the bug to make ubuntu better,
* is it reproduceable?
* can you please provide the steps to reproduce it.?
* can you still reproduce it with empathy 3.3.4?
thanks

[Bilal Shahid (s9iper1)]

i have seen a bug got fixed in upstream same like this please check again update your system.than tell us

[Bilal Shahid (s9iper1)]

attaching the upstream bug.

[roothorick (8-roothorick-gmail-com)]

Got the same crash on 3.3.91.

[Bilal Shahid (s9iper1)]

folks fix will be release in somedays wait for it
https://bugzilla.gnome.org/show_bug.cgi?id=670523#c7

[Vitaly Korolev (vitaly-korolev)]

Crashed in 3.4.0 after I disabled wifi connection.

[Roman Vesely (roman-mm)]

Me too.
Crashed in 3.4.0 after I disabled wifi connection.

[Piotr Dopart (dopart-piotr)]

Crash window appeared during the time when my computer was idle, so there is
 no way for me to determine the direct cause - unless it was precisely
 that: the window crashed during a long time of inactivity. There is a
 chance that sometime during that period empathy tried to reconnect and
 failed, causing the mail window to crash. Unfortunately there is a lot
 of maybes here.

[Sven Romeike (lun4tic)]

Exactly Piotr. several programms seem to crash when you leave your computer alone for a while and then come back and want to use it again. It's probably connected to the screenlock programm.

[Anders Aagaard (aagaande)]

Hit this after wakeup from suspend to ram. Noticed empathy reconnected and I was marked online, then the chat window disapeared.

[Bilal Shahid (s9iper1)]

if you people are able to recreat it than you please just get the stacktrace and attach it here it will help us to resolve the problem.
http://live.gnome.org/GettingTraces/Details

[Bilal Shahid (s9iper1)]

https://bugzilla.gnome.org/show_bug.cgi?id=672980
is the duplicate of our bug marked by a developer in upstream attaching it it got fixed before 3 days ago.

[Brian Curtis (bcurtiswx)]

http://mail.gnome.org/archives/gnome-announce-list/2012-April/msg00029.html

Bug is fixed in folks 0.6.9, and folks is up to 0.7.0 currently in GNOME

[Brian Curtis (bcurtiswx)]

0.6.9 is the latest stale version though. So recommend to update to that in precise.

[Brian Curtis (bcurtiswx)]

It appears as if this has already been fixed in ubuntu with the debian sync of 0.6.8. Marking as fix released.