> > On Sun, 19 Jun 2005 13:55:49 -0400 (EDT) > [EMAIL PROTECTED] (Stuart Brorson) wrote: > > > > I don't get any such warnings. Can you post a few of them (at least > > > starting from the first ones)? > > > > Here's the spew I get when I run the prog, open an existing .pcb file > > using the file browser, and then close down: > > > > [EMAIL PROTECTED] ~]$ /home/sdb/geda-install/bin/pcb > > > > (pcb-bin:3146): Gtk-WARNING **: Unable to locate theme engine in > > module_path: "bluecurve", > > You may need to reinstall your bluecurve gtk-enigines package. > Do you have something like a libbluecurve.so in > /usr/lib/gtk-2.0/2.4.0/engines?
Hmmm, I can look at this. FWIW, all gEDA programs -- as well as may others -- spew this bluecurve warning, but don't complain about anything else. Therefore, I wasn't very worried about this particular warning. > > (pcb-bin:3146): Gtk-WARNING **: Could not find the icon > > 'gnome-fs-home'. The 'hicolor' theme > > was not found either, perhaps you need to install it. > > You can get a copy from: > > http://freedesktop.org/Software/icon-theme/releases > > Looks like some more theme problems. The gnome-fs-home icon > would be found in packages like gnome-themes-extra or gnome-icon-theme. > I'm on a Debian system so these packages might be different if you > run something else. Possibly, although I am running an unmodified, vanilla version of FC2. That is, I haven't played around with the theme settings at all. I would expect that everything should just work. :-) > > (pcb-bin:3146): Gtk-CRITICAL **: file gtksettings.c: line 447 > > (gtk_settings_get_for_screen): assertion `GDK_IS_SCREEN (screen)' > > failed > > The gtk_settings_get_for_screen() function is called from several > places from within Gtk including the theme code, so I suspect > this is also related to the theme problems but can't say for sure > until the first two WARNINGS get cleared up... > > > (pcb-bin:3146): GLib-GObject-WARNING **: invalid (NULL) pointer > > instance > > I think all these remaining WARNINGS likely have to do with the initial > theme problems and have nothing to do with a need for some > code castings in gpcb. Meebe. The warnings which worry me are these: (pcb-bin:3146): GLib-GObject-CRITICAL **: file gsignal.c: line 2122 (g_signal_emit_valist): assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (pcb-bin:3146): GLib-GObject-WARNING **: invalid (NULL) pointer instance FWIW, I am running Fedora Core 2 on the machine spewing these errors. I will try FC3 later this evening. In any event, I'd like to track at least the last two down, because the amount is spewage is quite large, and noobies running gEDA on something other than a well-configured Debian box (yes, there are lots of non-Debian systems out there) might be scared off. [1] I'll spend some quality time looking. . . . . Stuart [1] I do not mean to disparage your totally awesome work with gPCB, by the way! When I first showed gattrib to Ales it also spewed lots of warnings. Ales -- in his infinite goodness -- helped me eliminate almost all of the problems. I'd like to at least try to help somebody else in the same way.
