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 105694 - glade-2 edit menus keeps cpu busy or segmentation fault
glade-2 edit menus keeps cpu busy or segmentation fault
Status: RESOLVED FIXED
Product: glade-legacy
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: Damon Chaplin
Damon Chaplin
: 103263 110704 110776 111142 112062 112667 113083 114574 117394 119117 125639 126533 128079 130104 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-02-10 02:30 UTC by anthony
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description anthony 2003-02-10 02:30:29 UTC 
When selecting "Edit Menus..." on a menubar widget my cpu processor usage
goes to 100% and glade-2 must be killed.

I'm not sure if this has anything to do with the above but, I also get many
of the following errors when starting up glade-2 (ver 1.1.3):

(glade-2:18095): Gtk-CRITICAL **: file gtkiconfactory.c: line 1906
(gtk_icon_set_get_sizes): assertion `icon_set != NULL' failed
Comment 1 Vesa Halttunen 2003-02-19 15:11:30 UTC 
I get this too and find this extremely annoying. GNOME 2.2 final, GCC
3.2.1, glibc 2.3.1, XFree86 4.2.1, Linux 2.4.20.
Comment 2 Damon Chaplin 2003-02-19 23:40:20 UTC 
What Linux distribution are you both using?
Which version of Glade - GTK+ or GNOME?

I'll check the code. Thanks.
Comment 3 anthony 2003-02-20 02:30:56 UTC 
I am using RedHat version 8.0 beta (phoebe)

glade-2 version 1.1.3

gtk-config --version
1.2.10

gnome-config --version
gnome-libs 1.4.1.7

This is an upgraded system from RH7.2
Comment 4 anthony 2003-02-24 15:19:35 UTC 
I just compiled the latest glade-1.1.3 from source on my RH8.0 (phoebe
beta) and tried glade-2

When starting glade-2 I get many of these errors:
(glade-2:19737): Gtk-CRITICAL **: file gtkiconfactory.c: line 1906
(gtk_icon_set_get_sizes): assertion `icon_set != NULL' failed


Then when trying to edit a menu I get a segmentation fault.
Maybe my backtrace will help decipher the problem:
$ gdb glade-2 core.19686 

(gdb) bt

+ Trace 34213

  • #0 _int_malloc
    from /lib/tls/libc.so.6
  • #1 calloc
    from /lib/tls/libc.so.6
  • #2 g_malloc0
    from /usr/lib/libglib-2.0.so.0
  • #3 gtk_tooltips_set_tip
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 glade_menu_editor_construct
    at glade_menu_editor.c line 736
  • #5 glade_menu_editor_new
    at glade_menu_editor.c line 1183
  • #6 gb_menu_bar_on_edit_menu
    at gbmenubar.c line 304 






Comment 5


Vesa Halttunen





          2003-02-24 20:44:11 UTC
        



I'm not using any distribution (self built system). Glade is 1.1.3
from
ftp://ftp.gnome.org/pub/gnome/sources/glade/1.1/glade-1.1.3.tar.bz2.
It's built with Gnome support. I can't get it to crash (at least not
reproducably) - it just hangs and goes into a busy loop. To reproduce
all I need to do is to start Glade, create a new GTK+ project, create
a window, put a menubar or optionmenu in it and try to edit the menus.






Comment 6


Damon Chaplin





          2003-02-28 13:49:38 UTC
        



I've just upgraded to GNOME 2.2 to test this, but still can't
reproduce it.

However, I have a feeling it is related to the theme you are using.
Which themes are you using?
Can you try switching to the default theme and see if that fixes it?

Anthony: yes, I think it is related to the critical warning you got.
My current idea is that some themes don't have icons for all stock
items. That would confuse Glade and cause this sort of problem.
This is a bad bug so I'd like to get it sorted out for the next
version.






Comment 7


anthony





          2003-02-28 23:56:54 UTC
        



The theme was my problem. I was using BlueCurve. 

I performed the following to solve the problem:
 Preferences/Theme/Details/Controls/Metal/Close/Close

Thank you Damon!






Comment 8


Vesa Halttunen





          2003-03-04 19:11:42 UTC
        



I was using PrettyOkayish and yes, that seemed to be the problem.
Using other themes this won't happen. Thanks!






Comment 9


Håvard Wigtil





          2003-03-14 14:47:16 UTC
        



Do you know if the problem is with Glade or the individual theme? I.e.
should I wait for a Glade fix or try to contact the individual theme
author?






Comment 10


Damon Chaplin





          2003-03-15 12:49:54 UTC
        



I'd guess it is a Glade problem. Unfortunately I still can't reproduce
it even with the BlueCurve theme.






Comment 11


Damon Chaplin





          2003-04-10 21:43:02 UTC
        



I've made the code more careful here, so hopefully this is fixed.
Reopen if you still see it.






Comment 12


anthony





          2003-04-10 22:38:03 UTC
        



The problem still exists in the Apr 10 18:09 1.1.3 build. The cpu is
busy when editing menus while using the Bluecurve theme but not when
using the Raleigh theme.






Comment 13


Damon Chaplin





          2003-04-12 00:03:24 UTC
        



I'm using RedHat 8.0 (on Intel) and the BlueCurve theme, and I don't see
the problem.

Can you think of anything else that could be a factor? Anything
theme-related you've changed from the default?






Comment 14


Damon Chaplin





          2003-04-19 21:03:40 UTC
        



*** Bug 111142 has been marked as a duplicate of this bug. ***






Comment 15


Damon Chaplin





          2003-04-19 21:05:38 UTC
        



I finally managed to reproduce this, on RedHat 9.0, with Glade 1.1.3.

But Glade 2.0.0 does fix it for me. Can you check if it fixes it for
you. It is at http://ftp.gnome.org/pub/GNOME/sources/glade/2.0/






Comment 16


anthony





          2003-04-19 21:43:48 UTC
        



This bug is fixed now with Glade2.0.0 under RH8.0 (phoebe beta for RH9).

Thank you Damon!






Comment 17


Damon Chaplin





          2003-04-20 11:33:13 UTC
        



*** Bug 110776 has been marked as a duplicate of this bug. ***






Comment 18


Damon Chaplin





          2003-04-20 11:34:11 UTC
        



*** Bug 103263 has been marked as a duplicate of this bug. ***






Comment 19


Damon Chaplin





          2003-04-20 11:36:30 UTC
        



*** Bug 110704 has been marked as a duplicate of this bug. ***






Comment 20


Damon Chaplin





          2003-05-03 12:13:13 UTC
        



*** Bug 112062 has been marked as a duplicate of this bug. ***






Comment 21


Damon Chaplin





          2003-05-10 19:33:15 UTC
        



*** Bug 112667 has been marked as a duplicate of this bug. ***






Comment 22


Damon Chaplin





          2003-05-18 14:39:34 UTC
        



*** Bug 113083 has been marked as a duplicate of this bug. ***






Comment 23


Damon Chaplin





          2003-06-14 14:57:11 UTC
        



*** Bug 114574 has been marked as a duplicate of this bug. ***






Comment 24


Damon Chaplin





          2003-08-21 19:24:20 UTC
        



*** Bug 119117 has been marked as a duplicate of this bug. ***






Comment 25


Damon Chaplin





          2003-08-21 19:26:06 UTC
        



*** Bug 117394 has been marked as a duplicate of this bug. ***






Comment 26


Damon Chaplin





          2003-10-28 09:40:03 UTC
        



*** Bug 125639 has been marked as a duplicate of this bug. ***






Comment 27


Damon Chaplin





          2003-11-28 10:28:54 UTC
        



*** Bug 128079 has been marked as a duplicate of this bug. ***






Comment 28


Damon Chaplin





          2003-11-30 11:44:42 UTC
        



*** Bug 126533 has been marked as a duplicate of this bug. ***






Comment 29


Damon Chaplin





          2003-12-02 09:08:38 UTC
        



*** Bug 128340 has been marked as a duplicate of this bug. ***






Comment 30


Damon Chaplin





          2003-12-29 10:42:38 UTC
        



*** Bug 130104 has been marked as a duplicate of this bug. ***