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 648845 - empathy crashed with SIGSEGV in g_strdup()
empathy crashed with SIGSEGV in g_strdup()
Status: RESOLVED OBSOLETE
Product: empathy
Classification: Core
Component: General
2.33.x
Other Linux
: Normal normal
: ---
Assigned To: empathy-maint
empathy-maint
Depends on:
Blocks:
 
 
Reported: 2011-04-28 07:16 UTC by Omer Akram
Modified: 2011-10-24 09:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Omer Akram 2011-04-28 07:16:15 UTC 
the issue occurs when you click to put you password

+ Trace 226915

  • #0 __strlen_sse42
    at ../sysdeps/x86_64/multiarch/strlen-sse4.S line 32
  • #1 g_strdup
    at /build/buildd/glib2.0-2.28.6/./glib/gstrfuncs.c line 101
  • #2 gtk_status_icon_set_image
    at /build/buildd/gtk+2.0-2.24.4/gtk/gtkstatusicon.c line 1882
  • #3 status_icon_blink_timeout_cb
    at empathy-status-icon.c line 369
  • #4 g_timeout_dispatch
    at /build/buildd/glib2.0-2.28.6/./glib/gmain.c line 3882
  • #5 g_main_dispatch
    at /build/buildd/glib2.0-2.28.6/./glib/gmain.c line 2440
  • #6 g_main_context_dispatch
    at /build/buildd/glib2.0-2.28.6/./glib/gmain.c line 3013
  • #7 g_main_context_iterate
    at /build/buildd/glib2.0-2.28.6/./glib/gmain.c line 3091
  • #8 g_main_loop_run
    at /build/buildd/glib2.0-2.28.6/./glib/gmain.c line 3299
  • #9 IA__gtk_main
    at /build/buildd/gtk+2.0-2.24.4/gtk/gtkmain.c line 1257
  • #10 main
    at empathy.c line 566 






Comment 1


Guillaume Desmottes





          2011-04-28 09:01:23 UTC
        



Which empathy version is that? Can you reproduce it?
I suspect a memory corruption, a valgrind log would be nice.






Comment 2


Brian Curtis





          2011-05-23 18:07:12 UTC
        



Hi Guillaume, 

The reporter in LP says they no longer have this issue, and therefore you can close this bug report as well.






Comment 3


Guillaume Desmottes





          2011-10-24 09:01:17 UTC
        



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






Comment 4


Pacho Ramos





          2011-10-24 09:32:57 UTC
        



(In reply to comment #3)
> *** Bug 662513 has been marked as a duplicate of this bug. ***

Looks like some people is still having this problem after resuming from suspend (that would probably point to the memory corruption problem pointed by Guillaume)