Re: [Evolution] Query about console messages

[Milan Crha <mcrha redhat com>]

On Sun, 2009-03-08 at 16:53 +0530, Ruchir Brahmbhatt wrote:
> Hi All,
>
> I repeatedly get below warnings when I run evolution in console. Can
> anyone let me know why they are coming?
>
> (evolution:17948): camel-WARNING **: Trying to check junk data is
> OBJECT 'CamelObject'
>
> (evolution:17948): camel-CRITICAL **: camel_object_is: assertion
> `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
>
> (evolution:17948): camel-CRITICAL **: camel_object_unhook_event:
> assertion `CAMEL_IS_OBJECT (obj)' failed
>
> (evolution:17948): camel-WARNING **: Trying to check junk data is
> OBJECT 'CamelObject'
>
> (evolution:17948): camel-CRITICAL **: camel_object_is: assertion
> `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
>
> (evolution:17948): camel-CRITICAL **: camel_object_unref: assertion
> `CAMEL_IS_OBJECT(o)' failed
>
> (evolution:17948): camel-WARNING **: Trying to check junk data is
> OBJECT 'CamelObject'
>
> (evolution:17948): camel-CRITICAL **: camel_object_is: assertion
> `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
>
> (evolution:17948): camel-CRITICAL **: camel_object_unhook_event:
> assertion `CAMEL_IS_OBJECT (obj)' failed
>
> (evolution:17948): camel-WARNING **: Trying to check junk data is
> OBJECT 'CamelObject'
>
> (evolution:17948): camel-CRITICAL **: camel_object_is: assertion
> `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
>
> (evolution:17948): camel-CRITICAL **: camel_object_unref: assertion
> `CAMEL_IS_OBJECT(o)' failed
>
>
> Thanks,
> Ruchir


        Hi,
it would be nice if you could install debug info packages for evolution,
evolution-data-server, evolution-exchange (if you use) and gtkhtml, and
you could find the source of these messages. The easiest way is probably
running evolution within gdb and setting a breakpoint to g_logv
function, and adding result of "bt" command when it'll stop with some
camel related message. The only bad thing is that it'll show the message
itself after the stop, thus you should guess the message by the domain
(I guess it requires debug info package for glib too, but that doesn't
help always too).

Please file a bug in http://bugzilla.gnome.org and let's move any
further investigation there, I doubt many readers of this list are
interested in this. (Please post here a bug number, for a reference).
        Thanks and bye,
        Milan