GNOME Bugzilla – Bug 605654
evolution can not send mails sometimes
Last modified: 2013-09-13 01:07:40 UTC
OS: opensuse 11.2 Evolution: 2.29.4 I noticed that in 2.29.x, some times sending mails doesn't work. Mail stays in outbox and status keep showing "Sending mail 100%". If we cancel this task by clicking cancel button for that task and then try to send by right clicking outbox and selecting flush outbox or clicking send/receive button, it has no effect. I have to restart evolution to send the mail. Steps: 1. Send mail. If it doesn't go through after some time, follow below steps. 2. Right click outbox and select flush outbox. This will do nothing. 3. Click send/receive button. This will also do nothing.
This increases CPU usage as well. Also it hangs evolution. The backtrace is as below:
+ Trace 220364
Thread 2 (Thread 0x7f168dbb5910 (LWP 28998))
Currently on 2.29.6. This has become even worse. Once it stucks to send mail, further action like compose or reply hangs evolution and renders it useless until restart. The process keeps consuming ~100% CPU and heating it like anything. Fan starts making noise. I have to kill evolution and restart it.
Sorry I forgot to mention in original report that I use Gmail IMAP account with calendar and addressbook also gmail.
Are you sure evolution is the process maxing out the CPU? Can you please run "top" when this happens and get a backtrace from whatever process is going nuts?
Yes I'm sure evolution is using the CPU. When I reproduce it again, I'll post cpu usage and backtrace.
Here we go. Top: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 8440 ruchir 20 0 720m 146m 23m S 100 5.9 4:56.81 evolution Backtrace:
+ Trace 220488
Looks like either a gnome-keyring or libdbus issue to me. I'd bet gnome-keyring.
This is repeating many times during the day and I have to keep killing and restart evolution many times. I'm afraid if this will corrupt my mailbox. I hope this can be marked blocker.
Surprisingly it doesn't happen on my new install on my new laptop. I wonder what was causing the issue on my old laptop.
NEEDINFO: Any change with later GNOME 2.29 releases?
Haven't noticed recently so we can close it for now.