GNOME Bugzilla – Bug 603958
Error while Sending message.
Last modified: 2011-11-30 05:35:01 UTC
Created attachment 149234 [details] Error Message Error while Sending message. Timed out trying to get lock file on /home/milz04/.evolution/mail/local/Outbox. Try again later. After trying to send a message, using the Exchange Plugin, the program closes. This happens quite often when sending a message using Ctrl+Enter, although the problem is not 100% reproducible. After re-opening evolution, you get a message with a recovery option, although the sent e-mail is already lying on the Outbox folder. After replying "no" to the recover message, I hit on "Send/receive" and the above mentioned error message comes up. I'd be happy to provide any further information
the program closes?? if true then: Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 149240 [details] evolution --debug
that is just a preview debug report using evolution --debug. I will perform a stack trace shortly...
Created attachment 149241 [details] Stack Trace
Above is the Stack Trace. This is while trying to send a mail with 2 attachments. It doesn't matter if I do Ctrl+Enter or click on "SEND". Program exits and mail remains on Outbox. After re-opening evolution, mail is still on outbox (no recover popup) but the attachments are gone.
please: http://live.gnome.org/GettingTraces/Details#gdb-only-applet
Sorry for that. As soon as this error reproduces, I will provide the Stack Trace.
Created attachment 149423 [details] Stack Trace stack trace using gdb
This happened after pressing SEND. The program froze this time, it did not crash like it did in the past. Maybe because of the same reason?
(gdb) thread apply all bt Cannot find new threads: generic error (gdb) bt
+ Trace 219597
The same as above, evolution froze after hitting send. I'm still trying to get that stack trace where the program exits, although this is just as bad.
Again, evolution froze after hitting send. Regards, Harald Program received signal SIGSEGV, Segmentation fault. magazine_chain_pop_head (mem_size=24) at /build/buildd/glib2.0-2.22.2/glib/gslice.c:474 474 /build/buildd/glib2.0-2.22.2/glib/gslice.c: No such file or directory. in /build/buildd/glib2.0-2.22.2/glib/gslice.c (gdb) bt
+ Trace 219630
Again, froze after hitting send. Message is always lying in Outbox and after re-opening evolution, the recovery message appears. (gdb) bt
+ Trace 219631
This morning the application closed after sending a message but I did not have the debugger on! Short after that, the application froze after sending a message. Here is the stack trace: (gdb) bt
+ Trace 219871
Although the bug has changed its behaviour, its still a bug and I'd like to know if this is still of any interest to you, as I have not received any answer to the posted traces since 07-12-2009... I find it tedious having to restart Evolution every now and then after sending a message! // or should I post a new bug report with the new behaviour?? Regards, Harald
Again, program freeze after sending a message. Here the stack trace: (gdb) bt
+ Trace 219872
Here, again. This time I got a trace of all running threads: (gdb) thread apply all bt
+ Trace 219873
Thread 1 (Thread 0x7ffff7f9f7f0 (LWP 13666))
Again, program froze after sending a message. Full thread trace below: (gdb) thread apply all bt
+ Trace 219890
Thread 1 (Thread 0x7ffff7f9f7f0 (LWP 2917))
can somebody take a look at this bug? Evolution crashes 2-3 times a day when sending a message... I have sent a lot of traces but have obtained no feedback since 09-12-2009!
here is another trace of the Evolution crash after sending a message: (gdb) thread apply all bt
+ Trace 219902
Thread 1 (Thread 0x7ffff7f9f7f0 (LWP 6249))
Info sent!
Here is another trace, same issue: (gdb) thread apply all bt
+ Trace 219903
Thread 174 (Thread 0x7fffcc0ff910 (LWP 13591))
Thread 17 (Thread 0x7fffd236b910 (LWP 13240))
Ok, but we need wait for develop answers for path the bug, patience please. Thank for you report.
I am trying to be patient but this is tedious. I don't know if anyone else is having this problem. I need to restart Evolution 5-10 times a day because of crashes after sending a message. After the crash I need to restart Evolution a few times untill it establishes a successful Connection to the Exchange Backend. I think this should have some priority... Thanks.
Further info: Evolution crashes when an E-Mail is sent to a LOCAL Address Book Group with more than 1 Recipient. This happens 3/5 times a Mail is sent. If I insert the Recipients one by one, Evolution does not crash. Maybe this information will help in issuing a fix. Regards, Harald
I can confirm this. I have been using Evolution for 2 days, without using Local Groups from the Address Book as Recipients and have experienced no crashes! I just tried to send a mail to a local Address Book Group and Evolution CRASHED. Regards, Harald
*** Bug 616523 has been marked as a duplicate of this bug. ***
*** Bug 620512 has been marked as a duplicate of this bug. ***
*** Bug 619503 has been marked as a duplicate of this bug. ***
Can you please check again whether this issue still happens in Evolution 3.0.3 or 3.2.0 and update this report by adding a comment and changing the "Version" field? Thanks a lot.
Sorry, since our company upgraded to Exchange Server 2010, I have no longer used Evolution. Regards, Harald