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 569336 - change in gtkbutton klass is causing crash when activating menu item
change in gtkbutton klass is causing crash when activating menu item
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
2.15.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 569311 570410 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-01-27 14:18 UTC by Frederic Crozat
Modified: 2009-02-03 19:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Frederic Crozat 2009-01-27 14:18:10 UTC
in gtk 2.15.2, rev 22227 is causing massive crash when activating a menu item :

* gtk/gtkbutton.c: Activate the action in a regular clicked
        handler instead of the default handler, to make it work with
        derived classes which don't chain up their clicked handler.

Reverting this patch fixes the crash.

This is caused by  gtktogglebutton.c:505

GTK_BUTTON_CLASS (gtk_toggle_button_parent_class)->clicked (button);

since now, clicked is NULL.

Exemple of stacktrace : gedit, then do File / Open File :

(gdb) bt
  • #0 ??
  • #1 gtk_toggle_button_clicked
    at gtktogglebutton.c line 505
  • #2 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #3 g_type_class_meta_marshal
    at gclosure.c line 878
  • #4 IA__g_closure_invoke
    at gclosure.c line 767
  • #5 signal_emit_unlocked_R
    at gsignal.c line 3174
  • #6 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #7 IA__g_signal_emit
    at gsignal.c line 3034
  • #8 IA__gtk_button_clicked
    at gtkbutton.c line 1106
  • #9 location_mode_set

Comment 1 Matthias Clasen 2009-01-27 15:09:05 UTC
        * gtk/gtktogglebutton.c: Don't chain the clicked handler
        up unconditionally.
Comment 2 Vincent Untz 2009-01-27 17:13:52 UTC
*** Bug 569311 has been marked as a duplicate of this bug. ***
Comment 3 Owen Taylor 2009-02-03 19:11:02 UTC
*** Bug 570410 has been marked as a duplicate of this bug. ***