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 170576 - Glade crashes after deleting a Filechooser object
Glade crashes after deleting a Filechooser object
Status: RESOLVED DUPLICATE of bug 167951
Product: glade-legacy
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Damon Chaplin
Damon Chaplin
Depends on:
Blocks:
 
 
Reported: 2005-03-16 16:17 UTC by Nicholas Gillotte
Modified: 2005-03-17 15:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nicholas Gillotte 2005-03-16 16:17:06 UTC 
Steps to reproduce:
1. Open Glade.
2. Create a window.
3. Create a filechooser object.
4. Delete either the window or the filechooser object. (The stack trace is from
deleting the filechooser object).
 

Stack trace:
(glade-2:5656): Gtk-CRITICAL **: gtk_container_foreach: assertion
`GTK_IS_CONTAINER (container)' failed

Program received signal SIGSEGV, Segmentation fault.

+ Trace 56942

Thread 1083117248 (LWP 5656)

  • #0 gail_scrolled_window_scrollbar_visibility_changed
    from /opt/gnome/lib/gtk-2.0/modules/libgail.so
  • #1 IA__g_cclosure_marshal_VOID__PARAM
    at gmarshal.c line 531
  • #2 IA__g_closure_invoke
    at gclosure.c line 437
  • #3 signal_emit_unlocked_R
    at gsignal.c line 2485
  • #4 IA__g_signal_emit_valist
    at gsignal.c line 2244
  • #5 IA__g_signal_emit
    at gsignal.c line 2288
  • #6 g_object_dispatch_properties_changed
    at gobject.c line 593
  • #7 g_object_notify_dispatcher
    at gobject.c line 234
  • #8 IA__g_object_notify
    at gobjectnotifyqueue.c line 123
  • #9 IA__gtk_widget_hide
    at gtkwidget.c line 2099
  • #10 gtk_widget_dispose
    at gtkwidget.c line 6465 

Other information:
using SuSE 9.2, glade 2.6.8, gdb 6.2.1
Comment 1 Damon Chaplin 2005-03-17 15:28:39 UTC 
This looks like a duplicate of bug 167951.

To work around it you can delete the widget from the XML file using a text editor.

*** This bug has been marked as a duplicate of 167951 ***