GNOME Bugzilla – Bug 119117
glade crashes when I try to start a particular project
Last modified: 2004-12-22 21:47:04 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 ?? ()
+ Trace 39334
Thread 1 (Thread 1086152896 (LWP 3053))
------- 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.
Appears to be a unique stack trace, according to the simple-dup-finder. Setting severity to critical and marking as new.
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 ***