Bug 404541 - application freeze when trying to send email
Summary: application freeze when trying to send email
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 8
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-11-29 15:09 UTC by markm
Modified: 2008-01-15 18:08 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2008-01-15 18:08:58 UTC

Attachments (Terms of Use)

Description markm 2007-11-29 15:09:51 UTC
Description of problem:

Basically spam test are taking too long and making application freeze for couple
of minutes! But when I accidentally press 'send' button while evolution is
receiving new emails, it freezes and I need to kill application.

Version-Release number of selected component (if applicable):

latest from fedora.download.com

How reproducible:


Steps to Reproduce:
1. write email
2. send it while application is receiving something in the background
Actual results:

application freeze and email is lost (after restart of course it allows me to
recover an email, but... recovered email doesn't have my text, I've typed).

Expected results:

working smoothly... without freezes and hangs - it's really annoying.

Additional info:

Comment 1 Milan Crha 2007-11-29 18:50:23 UTC
Can you install debug info packages of evolution, evolution-data-server and
gtkhtml (and evolution-exchange, if you use exchange) and when it freezes,
attach gdb to the process and attach here result of command "thread apply all
bt", please? We will see where it get stuck. Thanks in advance.

Comment 2 Matthew Barnes 2007-11-29 19:07:35 UTC
Also, which spam filtering plugin are you using -- SpamAssassin or Bogofilter?

If SpamAssassin, it turns out the behavior for the "Include remote tests" option
is inverted -- it runs remote tests if the option is UNCHECKED.  Remote tests
make spam filtering more accurate but can really slow things down.

I fixed this upstream just recently but it hasn't trickled down yet.

Comment 3 markm 2008-01-15 14:32:10 UTC
I believe it's fixed in current release as it works fine for me now.

Comment 4 Matthew Barnes 2008-01-15 18:08:58 UTC
Thanks for the update.  Closing as CURRENTRELEASE.

Note You need to log in before you can comment on or make changes to this bug.