For some reason evolution-mail segfaults. Specifically, I see evolution
segfault when I click on mail and then the mail-settings option.
*** Bug 11 has been marked as a duplicate of this bug. ***
Ok, have a way of going around the issue (I think).
The problem seems to occur if the mailclient crashes before you close the
program the first time the configure-database gets corrupted.
If you directly after Evolution starts for the first time exits cleanly it seems
to be working as it should after that. Can this be confirmed somewhere else?
The shutdown-just-after-starting-the-first-time solution seems to work
just fine. Yayyyy!!! Changing severity to minor, now that we have a
I had this problem and had to login to my IMAP server first before opening mail
settings. I'm marking this as fixed since I think it's more of an evolution
issue than anything we're doing wrong.
Please don't do this. I am assigned to the bug and I haven't marked it as being
resolved since I want to look in to the issue. No other distributions has this
problem. I wan't to make sure it's not due to our default -O3 CFLAGS.
Hmmm. I often get a segfault when trying to print from an email, but it doesn't
happen all of the time. Worse, I don't see any pattern of when it happens.
Well, I don't know about you guys, but I segfault everytime I try to apply a new
filter. Just installed gentoo, so maybe I'm missing something? I can read and
delete email fine, just can't add filters. Not sure if this is related or should
be a new bug?
it's probably not related.
The filter crash is fixed in 1.0.1-r2.
*** Bug 563 has been marked as a duplicate of this bug. ***
*** Bug 602 has been marked as a duplicate of this bug. ***
First time installer of Gentoo, I got the iso image last week and finished
installing everything yesturday. This Evolution bug still appears to exist.
Emerge installed Evolution 1.0.5 and since I didn't exit after doing the wizard
the evolution-mail process keeps segfaulting.
After removing ~/evolution and following the work around it no longer segfaults
but this bug still happens.
Should be re-opened.