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 598452 - crashed with SIGSEGV in contact_list_store_iface_setup()
crashed with SIGSEGV in contact_list_store_iface_setup()
Status: RESOLVED FIXED
Product: empathy
Classification: Core
Component: Contact List
2.28.x
Other Linux
: High major
: ---
Assigned To: empathy-maint
: 598448 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-14 15:54 UTC by Sebastien Bacher
Modified: 2009-10-19 13:28 UTC
See Also:
GNOME target: 2.28.x
GNOME version: ---


Description Sebastien Bacher 2009-10-14 15:54:04 UTC 
the bug has been described on https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/448580

"empathy 2.28.0.1

After resuming from suspend I opened a chat window to a MSN contact.
As soon as it opene, I got the crash

+ Trace 218310

  • #0 contact_list_store_iface_setup
    at empathy-contact-list-store.c line 175
  • #1 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #2 ??
    from /lib/libglib-2.0.so.0
  • #3 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #4 IA__gtk_main
    at /build/buildd/gtk+2.0-2.18.2/gtk/gtkmain.c line 1216
  • #5 main
    at empathy.c line 910 






Comment 1


Sebastien Bacher





          2009-10-14 15:54:18 UTC
        



*** Bug 598448 has been marked as a duplicate of this bug. ***






Comment 2


Guillaume Desmottes





          2009-10-19 12:47:24 UTC
        



Looking at the trace priv has an invalid value, probably because the EmpathyContactListStore has been destroyed.

I guess the store has been destroyed before this callback is called, hence the crash.






Comment 3


Guillaume Desmottes





          2009-10-19 13:28:16 UTC
        



Fixed in 2.28 (will be in 2.28.1) and master.
Thanks for your bug report!

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.