Dear Evolution folks,
the following messages are printed a lot to the terminal.
[…]
(evolution:3553): evolution-mail-CRITICAL **: cmp_array_uids: assertion
`md1 != NULL' failed
(evolution:3553): evolution-mail-CRITICAL **: cmp_array_uids: assertion
`md
I'm using Evolution (versions below) on Fedora 15 with Exchange 2003.
I'm finding that sometimes if I read and reply to a message it gets
marked as read and replied in my inbox, but next time a message arrives
(or maybe when evo checks for a new message) that message reverts to
unread and not repl
install the debug
packages (`evolution-dbg`, `evolution-data-server-dbg` and so on). Then
use `ps aux | grep evolution` to find out Evolution process ID and
attach to the hanged using `gdb --pid x`.
Afterward please do `set logging on /tmp/20110908--evolution-hang.bt` to
enable logging and then `t a a bt
On Thu, 2011-09-08 at 12:20 +0100, Joao Ferreira Gmail wrote:
> Hello,
>
> Ever since I upgraded (Debian box) to Evolution 3.0.2-1 I have been
> experiencing both hangs and crashes.
>
> Can I do something about it ?
Yes, upgrade to evo 3.0.3. I don't know why this version ever went into
testing,
Hello,
Ever since I upgraded (Debian box) to Evolution 3.0.2-1 I have been
experiencing both hangs and crashes.
Can I do something about it ?
Here is the output of a hang. I started Evolution used it for 30
minutes, then it hanged while fetching mail from my accounts. After a
while I had no choi
