On Thu, 2015-01-22 at 10:07 +0000, Joakim Tjernlund wrote:
>
> (evolution:5585): GLib-GObject-CRITICAL **: g_closure_unref:
> assertion 'closure->ref_count > 0' failed
>
> Could you look into the above glib error too? I sent a mail about
> that earlier.
Hi,
I'm sorry, but no. I told you, also earlier, that the bug is not in
Evolution, it's in WebKit. Get a backtrace [1] from it and you'll see
it yourself. There is nothing Evolution can do with it, except stop
using WebKit, which won't happen.
[1] $ gdb evolution --ex r --ex "b g_logv" --ex c --ex bt --ex c
which runs evolution, then let it finish its initial duties, find
a way to reproduce the critical warning, then press Ctrl+C once in
the terminal, which will set the breakpoint, then reproduce
the warning and if it'll be the first hit, then the shown backtrace
will provide info from where the warning comes. Feel free to repeat
the pair of commands "c" followed by "bt" to get more backtraces.
Quit gdb with a "q" command. As I said in the previous thread,
it's better to know, than to guess.
> >
> <ItemId
> Id="AAMkAGI1ZGRjZDViLTFiYTAtNDlmOC04MzcxLWY0YmU5YzViNWM4MgBGAAAAAACY+Y49jTA/TIVQQNL1ZZuvBwCFZzx/yfViToq1mDIZVK+jAAAAAAEMAACFZzx/yfViToq1mDIZVK+jAAADOr+cAAA="/>
>
evolution-ews asked for a message with the above ID (not much to tell
regular users, somehow)...
>
<m:ResponseMessages>
> <m:GetItemResponseMessage ResponseClass="Error">
> <m:MessageText>MIME content conversion
> failed.</m:MessageText>
>
...but the server failed to provide it, with the above error. It can
be that this error is incorrectly handled by the evolution-ews and
produces the useless error you see in the UI. I do not know what could
be a better option for this situation, because the server is failing,
thus the message cannot be retried in a way evolution-ews expects it.
Bye,
Milan
_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
