Bug 609417 - Crash when I double click in notification icon (panel)
Crash when I double click in notification icon (panel)
Status: RESOLVED NOTGNOME
Product: empathy
Classification: Core
Component: General
2.29.x
Other Linux
: Normal critical
: ---
Assigned To: empathy-maint
empathy-maint
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2010-02-09 12:58 UTC by Fabio Durán Verdugo
Modified: 2010-02-12 18:17 UTC (History)
1 user (show)

See Also:
GNOME target: ---
GNOME version: ---


Attachments
Empathy Log (343.96 KB, text/plain)
2010-02-09 14:49 UTC, Fabio Durán Verdugo
Details
Log (290.76 KB, text/plain)
2010-02-09 23:29 UTC, Fabio Durán Verdugo
Details
valgrind empathy (150.59 KB, text/plain)
2010-02-11 20:36 UTC, Fabio Durán Verdugo
Details

Description Fabio Durán Verdugo 2010-02-09 12:58:52 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
  • #0 status_icon_activate_cb
    at empathy-status-icon.c line 571
  • #1 IA__g_cclosure_marshal_VOID__VOID
    at /build/buildd/glib2.0-2.23.2/gobject/gmarshal.c line 77
  • #2 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.23.2/gobject/gclosure.c line 767
  • #3 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.23.2/gobject/gsignal.c line 3243
  • #4 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.23.2/gobject/gsignal.c line 2976
  • #5 IA__g_signal_emit
    at /build/buildd/glib2.0-2.23.2/gobject/gsignal.c line 3033
  • #6 emit_activate_signal
    at /build/buildd/gtk+2.0-2.19.4/gtk/gtkstatusicon.c line 1270
  • #7 gtk_status_icon_button_press
    at /build/buildd/gtk+2.0-2.19.4/gtk/gtkstatusicon.c line 1737
  • #8 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.19.4/gtk/gtkmarshalers.c line 84
  • #9 IA__g_closure_invoke
    at /build/buildd/glib2.0-2.23.2/gobject/gclosure.c line 767
  • #10 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.23.2/gobject/gsignal.c line 3243
  • #11 IA__g_signal_emit_valist
    at /build/buildd/glib2.0-2.23.2/gobject/gsignal.c line 2986
  • #12 IA__g_signal_emit
    at /build/buildd/glib2.0-2.23.2/gobject/gsignal.c line 3033
  • #13 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.19.4/gtk/gtkwidget.c line 4949
  • #14 IA__gtk_propagate_event
    at /build/buildd/gtk+2.0-2.19.4/gtk/gtkmain.c line 2447
  • #15 IA__gtk_main_do_event
    at /build/buildd/gtk+2.0-2.19.4/gtk/gtkmain.c line 1608
  • #16 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.19.4/gdk/x11/gdkevents-x11.c line 2372
  • #17 g_main_dispatch
    at /build/buildd/glib2.0-2.23.2/glib/gmain.c line 1960
  • #18 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.23.2/glib/gmain.c line 2513
  • #19 g_main_context_iterate
    at /build/buildd/glib2.0-2.23.2/glib/gmain.c line 2591
  • #20 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.23.2/glib/gmain.c line 2799
  • #21 IA__gtk_main
    at /build/buildd/gtk+2.0-2.19.4/gtk/gtkmain.c line 1219
  • #22 main
    at empathy.c line 919

    
Comment 1 Guillaume Desmottes 2010-02-09 14:11:30 UTC
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".
Comment 2 Fabio Durán Verdugo 2010-02-09 14:23:27 UTC
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:~$
Comment 3 Guillaume Desmottes 2010-02-09 14:36:34 UTC
no, you have to use:
EMPATHY_DEBUG=all empathy
Comment 4 Fabio Durán Verdugo 2010-02-09 14:49:13 UTC
Created attachment 153330 [details]
Empathy Log 

Ok, so sorry :-) attach the log file.
Comment 5 Guillaume Desmottes 2010-02-09 17:14:35 UTC
The Segmentation fault (core dumped) doesn't appear in this log. Did it crash as it the other log?
Comment 6 Fabio Durán Verdugo 2010-02-09 23:29:11 UTC
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
Comment 7 Guillaume Desmottes 2010-02-10 12:10:57 UTC
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.
Comment 8 Fabio Durán Verdugo 2010-02-11 20:36:30 UTC
Created attachment 153575 [details]
valgrind empathy
Comment 9 Guillaume Desmottes 2010-02-12 12:06:42 UTC
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.
Comment 10 Guillaume Desmottes 2010-02-12 17:33:40 UTC
This should be fixed in https://edge.launchpad.net/ubuntu/lucid/+source/empathy/2.29.90-0ubuntu2
Comment 11 Fabio Durán Verdugo 2010-02-12 18:17:25 UTC
Thank Guillaume, I can confirm this is FIXES.
Great :-)

Note You need to log in before you can comment on or make changes to this bug.