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 119117 - glade crashes when I try to start a particular project
glade crashes when I try to start a particular project
Status: RESOLVED DUPLICATE of bug 105694
Product: glade-legacy
Classification: Deprecated
Component: general
unspecified
Other other
: Normal critical
: ---
Assigned To: Damon Chaplin
Damon Chaplin
Depends on:
Blocks:
 
 
Reported: 2003-07-04 21:45 UTC by rbk34
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description rbk34 2003-08-04 19:14:54 UTC
Package: glade
Severity: normal
Version: 1.1.3
Synopsis: glade crashes when I try to start a particular project
Bugzilla-Product: glade
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

When I try to open my project it segv's.  I did an strace on glade and
found the following:
write(2, "\n(glade-2:3079): Gtk-CRITICAL **"..., 129
(glade-2:3079): Gtk-CRITICAL **: file gtkiconfactory.c: line 1906
(gtk_icon_set_get_sizes): assertion `icon_set != NULL' failed
) = 129
getpid()                                = 3079
brk(0)                                  = 0x8374000
brk(0x8375000)                          = 0x8375000
write(2, "\n(glade-2:3079): Gtk-CRITICAL **"..., 129
(glade-2:3079): Gtk-CRITICAL **: file gtkiconfactory.c: line 1906
(gtk_icon_set_get_sizes): assertion `icon_set != NULL' failed
) = 129
--- SIGSEGV (Segmentation fault) @ 0 (0) ---

This only happens on one pre-existing project.  I would like to continue
working on it with glade if possible.


Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?


Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/glade-2'

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1086152896 (LWP 3053)]
0xffffe002 in ??
    ()

Thread 1 (Thread 1086152896 (LWP 3053))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gb_image_new
  • #4 gb_image_new
  • #5 gb_widget_load
  • #6 gb_widget_load
  • #7 gb_widget_load
  • #8 gb_widget_load
  • #9 gb_widget_load
  • #10 gb_widget_load
  • #11 gb_widget_load
  • #12 gb_widget_load
  • #13 gb_widget_load
  • #14 gb_widget_load
  • #15 gb_widget_load
  • #16 load_project_file
  • #17 load_project_file
  • #18 glade_project_open
  • #19 glade_project_window_open_project
  • #20 glade_project_window_new
  • #21 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #26 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 _gtk_button_paint
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #29 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #31 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #34 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 _gtk_button_paint
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #38 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #39 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #40 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #42 gtk_widget_send_expose
    from /usr/lib/libgtk-x11-2.0.so.0
  • #43 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #44 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #45 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #46 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #47 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #48 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #49 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #50 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #51 main
  • #52 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-08-04 15:14 -------

Unknown version 1.1.x in product glade. Setting version to the default, "unspecified".
The original reporter (rbk34@netzero.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, damon@gnome.org.

Comment 1 Elijah Newren 2003-08-05 17:18:37 UTC
Appears to be a unique stack trace, according to the
simple-dup-finder.  Setting severity to critical and marking as new.
Comment 2 Damon Chaplin 2003-08-21 19:24:21 UTC
Looks like a duplicate of bug 105694.
Upgrading to 2.0.0 should fix it.

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