newest gimp won't run

[Harry Putnam]

I ran yum on all gimp packages .. installing:
gimp-2.2.2-3
gtkam-gimp-0.1.12-2
gimp-data-extras-1.2.0-12
gimp-print-plugin-4.2.7-3
gimp-help-2-0.1.0.6.1
gimp-print-4.2.7-3

No errors showed up.  But now when I attempt to run gimp.  I get a
errors like this (and no gimp comes up):

(gimp:12373): GLib-GObject-WARNING **: specified class size for type
  `GimpContainerEntry' is smaller than the parent type's `GtkEntry'
  class size

(gimp:12373): GLib-GObject-CRITICAL **: file gtype.c: line 2319
  (g_type_add_interface_static): assertion `G_TYPE_IS_INSTANTIATABLE
  (instance_type)' failed

(gimp:12373): GLib-GObject-CRITICAL **: file gobject.c: line 819
  (g_object_new): assertion `G_TYPE_IS_OBJECT (object_type)' failed
  gimp: symbol lookup error: gimp: undefined symbol:
  g_return_if_fail_warning

[Nils Philippsen]

On Mon, 2005-01-17 at 08:57 -0600, Harry Putnam wrote:
> I ran yum on all gimp packages .. installing:
> gimp-2.2.2-3
> gtkam-gimp-0.1.12-2
> gimp-data-extras-1.2.0-12
> gimp-print-plugin-4.2.7-3
> gimp-help-2-0.1.0.6.1
> gimp-print-4.2.7-3
>
> No errors showed up.  But now when I attempt to run gimp.  I get a
> errors like this (and no gimp comes up):
>
> (gimp:12373): GLib-GObject-WARNING **: specified class size for type
>   `GimpContainerEntry' is smaller than the parent type's `GtkEntry'
>   class size
>
> (gimp:12373): GLib-GObject-CRITICAL **: file gtype.c: line 2319
>   (g_type_add_interface_static): assertion `G_TYPE_IS_INSTANTIATABLE
>   (instance_type)' failed
>
> (gimp:12373): GLib-GObject-CRITICAL **: file gobject.c: line 819
>   (g_object_new): assertion `G_TYPE_IS_OBJECT (object_type)' failed
>   gimp: symbol lookup error: gimp: undefined symbol:
>   g_return_if_fail_warning

Is this an FC3 or an FC4 (development/Rawhide) system? I assume the
former -- in that case please install the package built for FC3 then
(gimp-2.2.2-0.fc3.3 should hit the download servers with then next
push), you shouldn't use Rawhide packages on FC3.

Nils

[Harry Putnam]

Nils Philippsen  writes:
> Is this an FC3 or an FC4 (development/Rawhide) system? I assume the
> former -- in that case please install the package built for FC3 then
> (gimp-2.2.2-0.fc3.3 should hit the download servers with then next
> push), you shouldn't use Rawhide packages on FC3.

Its sort of a hybrid.  Mostly rawhide.  
Cat /etc/fedora-release just shows:
   Fedora Core release Rawhide (Rawhide)

I always get confused about the
version thing.  I just update out of rawhide intermittenly.  Do you
know what other packages might be causing the problem?

Shouldn't the dependancy routines have returned something about a
problem?

Currently I have 238 packages to update.  Any ideas which would be most
likely to help this?.   My system is fairly stable right now.  I'd
like to just update whats needed at the moment for gimp.

[seth vidal]

> Its sort of a hybrid.  Mostly rawhide.  
> Cat /etc/fedora-release just shows:
>    Fedora Core release Rawhide (Rawhide)
>
> I always get confused about the
> version thing.  I just update out of rawhide intermittenly.  Do you
> know what other packages might be causing the problem?
>
> Shouldn't the dependancy routines have returned something about a
> problem?
>
> Currently I have 238 packages to update.  Any ideas which would be most
> likely to help this?.   My system is fairly stable right now.  I'd
> like to just update whats needed at the moment for gimp.

dependencies being solved does not, in any way, guarantee that the
program will run w/o problems.

-sv

[Harry Putnam]

seth vidal  writes:
> dependencies being solved does not, in any way, guarantee that the
> program will run w/o problems.

Not sure why you felt a need to make such a comment.
I didn't suggest it did.  No mention of guarantees whatever.

Not showing any dependancy errors should be a good indicator the
probram won't break due to dependancy problems. I don't know if this
is even dependency related.  That is what I was asking.

[Nils Philippsen]

On Mon, 2005-01-17 at 23:07 -0600, Harry Putnam wrote:
> Nils Philippsen  writes:
> > Is this an FC3 or an FC4 (development/Rawhide) system? I assume the
> > former -- in that case please install the package built for FC3 then
> > (gimp-2.2.2-0.fc3.3 should hit the download servers with then next
> > push), you shouldn't use Rawhide packages on FC3.
>
> Its sort of a hybrid.  Mostly rawhide.  
> Cat /etc/fedora-release just shows:
>    Fedora Core release Rawhide (Rawhide)
>
> I always get confused about the
> version thing.  I just update out of rawhide intermittenly.  Do you
> know what other packages might be causing the problem?

The only way to reliably find out what may be causing this were to debug
it deeply. A good guess would be gtk2 and related packages, but if you
want to be safe, do this:

0) Start with the gimp, gimp-devel packages
1) find out what packages are required ("rpm -q --requires ...")
2) find out which packages provide these requirements ("rpm -q
   --whatprovides ...")
3) update these packages if necessary
4) repeat steps 1 through 3 until all packages are updated that gimp and
gimp-devel require

Alternatively you can update the whole system which is much easier ;-).
> Shouldn't the dependancy routines have returned something about a
> problem?

No, they don't have information about library symbol changes.
> Currently I have 238 packages to update.  Any ideas which would be most
> likely to help this?.   My system is fairly stable right now.  I'd
> like to just update whats needed at the moment for gimp.

If you want a fairly stable system, why do you use Rawhide?

Nils

[Harry Putnam]

Nils Philippsen  writes:
> Start with the gimp, gimp-devel packages
> find out what packages are required ("rpm -q --requires ...")
> find out which packages provide these requirements ("rpm -q
> --whatprovides ...")
> update these packages if necessary
> repeat steps 1 through 3 until all packages are updated that gimp and
>
> gimp-devel require

[...] snipped nifty step thru

Hey thanks.  I'd never thought to do that in the 7-8 yrs I've been
using redhat then fedora.  Seeing it in print it looks terribly
obvious. hehe.
> If you want a fairly stable system, why do you use Rawhide?

I like new stuff, and have found over the years that I can run from
rawhide with a little care.  Even before there was a fedora, there was
rawhide.  From experience I'd say rawhide since the Advent of fedora
is more likely to be stable than before.

I also suspect the dire warning about rawhide are a little overstated.

[Harry Putnam]

Nils Philippsen  writes:
> The only way to reliably find out what may be causing this were to debug
> it deeply. A good guess would be gtk2 and related packages, but if you
> want to be safe, do this:

[...] Nice!

Just a little feedback and another `thank you'.
I started with `rpm -q --requires gimp.

Then selected from that list just gtk2 and glib2 by updating just the
devel versions which usually pulls in other needed stuff.

After just going thru those two.  Which updated both versions of each
and Pango (+ devel).  Is all it took to get gimp running.

Thanks for the nifty logical proceedure.