Re: [Evolution] Evolution 1.4 spits multiple 'camel-WARNING...' messages.



They can be handled the same, although as you've probably guessed - the
"...parading as iso-8859-1" warning is nothing you should be concerned
about, it just means that a mailer sent you a message that claimed to be
in iso-8859-1 but was actually in the Windows-cp1252 charset.

Jeff

On Tue, 2003-06-24 at 10:26, Panos Platon Tsapralis wrote:
OK, 'Not Zed', thanks for the reply - as soon as I have some spare time,
I will apply your advice and will post the required data to bugzilla.

BTW, there are some other messages sent out by Evolution less
frequently. See below:

(evolution:1333): camel-WARNING **: Encountered Windows charset parading
as iso-8859-1,

(evolution:1317): GLib-GObject-WARNING **: gsignal.c:1705: instance
'0x450037c8' has no handler with id '4434',

(evolution:2234): Bonobo-CRITICAL **: file bonobo-event-source.c: line
376 (bonobo-event_source_client_remove_listener): assertion `object !=
CORBA_OBJECT_NIL' failed,

(evolution:1385): camel-CRITICAL **: file camel-folder.c: line 935
(camel_folder_free_message_info): assertion `info != NULL' failed.

Are these falling into the same ('warning') type of messages (I observed
that some of them seem to be considered CRITICAL...) or should I do
something different to handle them?

Regards,

On Tue, 2003-06-24 at 08:24, Not Zed wrote:
We tried to remove most of the spurious warnings, but I guess at least
one went through ...

This particular warning means we called a method saying we didn't care
it if failed, and internally its checking for failure ...

So I wouldn't worry about it specifically.  If you would like to help
clear it out to ease your state of mind, you could try generating a
backtrace to pinpoint where it happens, try the following:

gdb evolution
(gdb) r
... do some stuff, until it starts to happen ...
ctrl-c
(gdb) b g_log
(gdb) c
... next time a warning happens, it will stop ...
(gdb) where
... if that doesn't show any call to camel_exception_get_id ... then try
(gdb) theread apply all bt
... if that doesn't show anything, its probably stopped in the wrong
place or something ... *shrug*

And send it to a bug on bugzilla.

These sorts of bugs are trivial to fix.


On Tue, 2003-06-24 at 05:51, Panos Platon Tsapralis wrote:
While running Evolution (v.1.4) on the command line of an x-terminal, I
noticed that it repeatedly gives the following message:

(evolution:1397): camel-WARNING **: camel_exception_get_id called with
NULL parameter.

Evolution runs fine on my system (RH8, fully updated from RHN/Red
Carpet) - even better than older versions did (e.g., no more crashes
while managing the "Contacts" folder).

However, I fear that this message may be an indication of a headache
later on, so, if anybody has a clue on where this message comes from and
how I can eliminate it, be my guest...

TIA,

_______________________________________________
evolution maillist  -  evolution lists ximian com
http://lists.ximian.com/mailman/listinfo/evolution
-- 
Jeffrey Stedfast
Evolution Hacker - Ximian, Inc.
fejj ximian com  - www.ximian.com




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]