Re: [Gramps-users] another funny (error?) message -- invalid type

[Paul F. <pf....@gm...>]

Thank you for your reply.

On 3/9/10, Benny Malengier <ben...@gm...> wrote:
>> ...
>> I am using the F12 version of 3.1.3-1.  Thanks.
>>
>>
>> /usr/share/gramps/gramps.py:224: Warning: invalid uninstantiatable
>> type `(null)' in cast to `GObject'
>>  gtk.main()
>> /usr/share/gramps/gramps.py:224: Warning: g_object_notify: assertion
>> `G_IS_OBJECT (object)' failed
>>  gtk.main()
>
> As the error says, this is a warning from gtk, which is the GTK toolkit.

Thank you for that clarification.  I appreciate it.  (It may be obvious to
you but it wasn't obvious to me.  While I see the word "warning" it is
not near the words "gtk.main".)

> ...
> We can only have a hope of finding these issues if you can tell
> exactly what you need to do in Gramps for this warning to appear.

Well, that's too bad.  I was hoping the text I posted would give enough
information to at least point to the right area.  I don't normally have that
terminal window visible when I am running gramps but now that I know
you need more timely information I'll think if (or how) I can do that.

> If a save in Gramps does not happen, then or Gramps would hang, or you
> would see a full error message passing by.

Would this "error message" appear in some gramps-generated window
(perhaps popped up to inform me)?  Or would it appear in the original
terminal window I ran the "gramps" command in?

(I doubt it matters but I usually put gramps in the background
when I start it:
    ( gramps < /dev/null & ) < /dev/null
as that way I don't have to worry about accidental typein.)

> ... If you start all your programs from terminal, you will probably
> see some other applications that print a lot more warnings/errors to
> the terminal output.

I do indeed start all of my programs from my xterm terminal window
and I never see any error messages at all, from any that I can recall.

The classic commands I run (e.g., ls, date, ln, echo, sed, tr, mv, rm,
as well as more modern things like emacs) don't seem to produce
any error messages -- in years of use.

Perhaps that's why I'm somewhat dismayed that in only a week or
two of gramps usage I have now seen two.  Both of which were (I
claim) cryptic to a non-developer, non-Python, non-GTK-aware type
of person (e.g. me).

That's why I'm posting them, to learn more.

Thanks again for your kindness in replying.