GNOME Bugzilla – Bug 609417
Crash when I double click in notification icon (panel)
Last modified: 2010-02-12 18:17:25 UTC
when I double click in notification icon (panel) Program received signal SIGSEGV, Segmentation fault. status_icon_activate_cb (status_icon=0x831f3a8, timestamp=135605040, icon=0x2) at empathy-status-icon.c:571 571 empathy-status-icon.c: No such file or directory. in empathy-status-icon.c (gdb) bt full
+ Trace 220498
Which Empathy version are you using? Can you easily reproduce this bug? If yes, empathy log could help be helpful; run empathy using "EMPATHY_DEBUG=all empathy".
the version is 2.29.90 for ubuntu lucid fabio@OptimusPrime:~$ empathy EMPATHY_DEBUG=all ** (empathy:7373): WARNING **: Couldn't write avatar image:0x9543748 with length:9812 to pixbuf loader: Error interpreting JPEG image file (Unsupported marker type 0x09) ** (empathy:7373): WARNING **: Couldn't write avatar image:0x9553820 with length:13239 to pixbuf loader: Error interpreting JPEG image file (Unsupported marker type 0x35) Segmentation fault (core dumped) fabio@OptimusPrime:~$
no, you have to use: EMPATHY_DEBUG=all empathy
Created attachment 153330 [details] Empathy Log Ok, so sorry :-) attach the log file.
The Segmentation fault (core dumped) doesn't appear in this log. Did it crash as it the other log?
Created attachment 153374 [details] Log Yes it crash, and always is crash if I clicked in status icon I run EMPATHY_LOGFILE=empathy.log EMPATHY_DEBUG=all empathy
Humm logs don't really help unfortunatelly. Could you try to run Empathy in valgrind and reproduce the crash please? Use "G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=20" to run valgrind.
Created attachment 153575 [details] valgrind empathy
Thanks a lot for this log Fabio. I took me a while but I finally found the problem. This crash is because of a Ubuntu specific patch. The 20_libindicate.patch introduces the following change: static void -status_icon_activate_cb (GtkStatusIcon *status_icon, +status_icon_activate_cb (GtkStatusIcon *status_icon, guint timestamp, Which is obviously wrong as the "activate" signal doesn't have this timestamp argument. See http://library.gnome.org/devel/gtk/stable/GtkStatusIcon.html#GtkStatusIcon-activate I will notify Ubuntu guys about that but it's probably best to open a bug on launchpad.
This should be fixed in https://edge.launchpad.net/ubuntu/lucid/+source/empathy/2.29.90-0ubuntu2
Thank Guillaume, I can confirm this is FIXES. Great :-)