GNOME Bugzilla – Bug 398229
Don't claim Evolution "quit unexpectedly" when the computer was restarted
Last modified: 2021-05-19 11:55:50 UTC
Evolution 2.8.1, Ubuntu 6.10 1. Start writing a message. 2. Restart the computer and log in. What should happen: Evolution reopens, and the message window appears exactly as it was when you left it. What actually happens: "Do you want to recover unfinished messages? Evolution quit unexpectedly while you were composing a new message. Recovering the message will allow you to continue where you left off." When the computer restarts, 99.9% of the time it's because I asked it to. Therefore it is not true that "Evolution quit unexpectedly".
What do you think about just killing that dialog altogether and always recovering unfinished messages without asking? I don't know why a user would answer No to that question, unless they clicked it without reading the dialog.
(That would apply to both session restarts and actual crashes.)
Yes probably it should go away. I am here because my evolution tends to freeze if I have that question popping up. I am not sure but it may mostly be problematic if I had a power cut. The winmdow does not react and evolution screen turns grey. Today this has been recurring 5 times and I am not yet in.
This bug was reported against a version which is not supported any more. Developers are no longer working on this version so there will not be any bug fixes for it. Can you please check again if the issue you reported here still happens in a recent version of GNOME and update this report by adding a comment and adjusting the 'Version' field? Again thank you for reporting this and sorry that it could not be fixed for the version you originally used here. Without feedback this report will be closed as INCOMPLETE after 6 weeks.
Resetting state to NEW. I don't really want to get rid of the dialog anymore so this bug will have to wait until we have proper session management in the shell. Then we should be able to distinguish between restoring a previous session and recovering from a crash.
Maybe it is not such a bad idea for Evolution to ask you if you want to recover the message. Maybe having this message is not such a bad thing as it gives you the chance to decline opening the email you were creating. It may be that there is a bug in Evolution that we don't know about and for some reason opening the message you created is causing Evolution to crash. I have just such a problem at this very moment that I will report if I don't find a solution to it in my research of past history. (That's how I stumbled upon this thread.) At this moment I have an email in my In-Box that, when I go to open it, is causing my Evolution to close unexpectedly. Luckily, when Evolution opens, it does not centre on this email; otherwise I would have a real problem on my hands as I really depend on my email for my work. So, although at first blush, it might seem like an unnecessary message to have to deal with and, if I were not confronted by this problem, I would have most probably agreed with the general sentiment, I'm now having second thoughts. Being to some extent swayed by that, I then think about the impression it made on me when this message first popped up and that was one of relief and a feeling of gratitude to the developers of this fine program. So maybe on a number of levels, having that message is not such a bad idea. Well I must get back to researching if anyone else has had a problem with an email message, on opening, causing Evolution to close unexpectedly. For the information of anyone interested, the email in question is unsolicited (and most probably SPAM) ASCII<info@asciisoftwaresolutions.com.au> FW:TSITC Meeting If worse comes to worst, I can go into my IMAP server and find the little critter that is causing this grief and send it to you...but first I will check out the facts rather than waste good people's time.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new bug report ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.