GNOME Bugzilla – Bug 265205
'Evolution' hangs if 'Evolution' is closed while sending mail
Last modified: 2006-03-09 06:38:41 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: Steps to reproduce the problem: 1. Select on "inbox' of user, then click on 'New'. 2. Type a valid mail-address and some text in subject.Then 'Send' 3. Click on Outbox, then on 'Sent Items' 4. Message arrives on status bar 'Sacnning for changed messages' on L.H.S. & 'Storing Folder Personal/Inbox' on other side. This takes a long time 5. So when clicked on 'x' to close evolution, it threw error message 'U have unsent messages, do u wish to quit'. 6.Click on Quit, After sometime message occurs 'Evolution Warning' is not responding. Attached traces and screen shot of error message Actual Results: Expected Results: How often does this happen? Additional Information:
This being an exit time issue, not critical.
As per the ethics of testing, any application hang is classified as major/critical/blocker depending upon the scenario, because the code block behind the hang has to be anyway fixed since it could lead to other unforeseen problems. We can consider fixing these types of bugs for an appropriate milestone. Hence, marking this as 'MAJOR'
Sorry, This still doesn't qualify for Major. Also, Please provide complete details as to how often this happens etc. (The criteria for various Priorities can be obtained by clicking Priority link)
Please attach a back trace [ of evolution, evolution-data-server and evolution-exchange processes ] for this hang. Also, mention the frequency of occurrence of this bug.
Created attachment 44222 [details] Stack traces of Evolution, Exchange-data-server, Exchange-storage
I tested the same scenario by sending a mail with 64MB attachment so that the mail wont get delivered instantaneously. Wehn the sendign is in progress, I switched folders and close Evo. It popped up the same error dialog and asked if I want to quit even if I have messages in Outbox. I clicked Quit. Though it appears to be hung at this stage it is not. It sent the mails from outbox and then closed properly. The stack traces show the least symptom of a hang. Can you test what happens at your end?
Closing as obsolete. Reopen if it happens again. I observe "Sending message" will help the user to identify what is happening. The user can also choose to kill the client manually if he doesnt want the mail transfer to get finished.