After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 508732 - Evolution Crash Detection dialog
Evolution Crash Detection dialog
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Shell
2.24.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 502571 519798 530345 (view as bug list)
Depends on:
Blocks: 502515
 
 
Reported: 2008-01-11 11:05 UTC by Michael Meeks
Modified: 2013-09-13 00:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
crash recovery ? (21.25 KB, image/png)
2008-01-11 11:13 UTC, Michael Meeks
  Details
Proposed patch (15.84 KB, patch)
2008-08-15 19:15 UTC, Matthew Barnes
committed Details | Review

Description Michael Meeks 2008-01-11 11:05:05 UTC
Could this be the world's most irritating dialog ?

I have no idea what decision it is asking me to make, or indeed - why it is so important that I have to make it right-now before I can do anything with evo.

OTOH - since I don't understand it, I'm scared to make it go away.

Can we remove it ? or better make it default to "Do not show this message [ever!] again", to reduce confusion that it might actually be useful ;-)
Comment 1 Michael Meeks 2008-01-11 11:13:05 UTC
Created attachment 102580 [details]
crash recovery ?
Comment 2 André Klapper 2008-01-11 12:54:49 UTC
+1
Comment 3 Matthew Barnes 2008-03-03 12:05:11 UTC
It's trying to avoid the problem of some particular mail (or calendar event or whatever) causing Evolution to crash on startup when it tries to automatically preview the thing.  It's inspired by Epiphany's crash recovery dialog.

I agree it could use some rewording.  For starters, the buttons should be phrased in more of a "Do Action" / "Don't Do Action" style.  Maybe something like:

    [Leave Preview Panes Alone]  [Hide Preview Panes]


Also, selecting "Do not show this message again" tells GConf to automatically "Hide Preview Panes" / "Recover" in the future even if I choose "Leave Preview Panes Alone" / "Ignore" this time.  That's a bug.  Maybe this wording would be clearer:

    [ ]  Apply my choice to future crash recoveries


Any other suggestions?
Comment 4 Matthew Barnes 2008-03-03 12:46:29 UTC
*** Bug 502571 has been marked as a duplicate of this bug. ***
Comment 5 Matthew Barnes 2008-03-03 13:01:33 UTC
*** Bug 519798 has been marked as a duplicate of this bug. ***
Comment 6 Matthew Barnes 2008-03-11 00:35:11 UTC
Bumping version to a stable release.
Comment 7 Andrew Conkling 2008-04-29 02:31:05 UTC
*** Bug 530345 has been marked as a duplicate of this bug. ***
Comment 8 Andrew Conkling 2008-04-29 02:34:00 UTC
An additional comment:
*** (From Bug 530345) ***
> User's don't care about our skepticism in detecting crashes.  The phrase
> "Evolution appears to have exited unexpectedly..." implies that we're not sure.
> But we are sure from the state of the files, correct?  For simplicity, this
> should read "Evolution exited unexpectedly the last time..."
Comment 9 Patrick van Staveren 2008-04-29 11:50:08 UTC
Thanks Andrew for matching this up.

Re-summarizing so others can find this bug.
Comment 10 Martin Meyer 2008-04-29 13:14:39 UTC
Can I suggest some alternate text?

Windows title: "Evolution exited unexpectedly (i.e. it crashed)"

"Evolution exited unexpectedly when it was last running. If you are experiencing repeated crashes immediately after opening Evolution, this could be a problem with the message which is displaying in the "Message Preview" panel.

Would you like to hide the Message Preview panel to prevent this crash from repeating? Note: you can re-enable the Message Preview by selecting View -> Preview -> View Message Preview, or by pressing ctrl+M."

[ ] Remember this option every time.

[ Hide Message Preview ] | [ Keep Message Preview ]


Note that as mentioned in the initial report for Bug 530345, this dialog probably shouldn't be displayed at all if the folder selected when Evolution crashed didn't have a Message Preview panel showing. Can we even tell if that's the case at the point where the dialog is presented though?
Comment 11 Frank Quist 2008-05-08 19:30:08 UTC
I'd suggest replacing this dialog with something nonmodal, such as a notification in place of the preview dialog that is has been temporarily hidden because of an earlier crash. 
Comment 12 Eric Polin 2008-07-10 09:30:02 UTC
I am afraid that the Remember option contradicts the very purpose of the message, which is to help the average user handle the rare case where the preview causes the crash.
I would rather suggest the following:

1) Open Evolution without the preview

2) Show a modal or non-modal dialog box (I guess a modal one is good enough) in front of it containing:

"Evolution exited unexpectedly when it was last running. This might
be a problem with the message which is displaying in the "Message Preview"
panel. The display of this panel has therefore been suspended.

Note: if you choose to keep the preview hidden, you can re-enable it later by selecting View ->
Preview -> View Message Preview, or by pressing ctrl+M."

[[ Resume Message Preview Display ]] | [ Keep Message Preview Hidden ]

3) If Resume is clicked, reactivate Preview immediately

I believe that solves everything and above all there is no need for the user to think: in 99.9% of the case he default is the good choice, and in the remainder 0.1% it is a good test ;-)
Comment 13 David Moore 2008-07-13 18:50:30 UTC
Can't we just leave the preview window blank in the case that evolution is starting up after a crash?  This is how it appears if you deselect the current message.

That way, no dialog box is necessary.

Comment 14 Michael Meeks 2008-07-14 14:03:43 UTC
an empty preview window, with no selected mail would be by far the simplest, and least painful solution surely ? [ would also reduce our LOC count presuambly ;-]
Comment 15 Sebastien Bacher 2008-08-12 09:04:57 UTC
the issue is also mentionned on https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/235427, could this dialog be changed before the string freeze? the buttons label are especially confusing and should be easy to update
Comment 16 Srinivasa Ragavan 2008-08-12 10:39:18 UTC
evolution --disable-preview does similar to what Michael suggessted.

But surely, I did heard from multiple people that the dialog is useful. But I agree it might need work like storing the right choices, as Matt described.
Comment 17 André Klapper 2008-08-12 10:44:06 UTC
Srini: We talk about the bad and confusing strings of the buttons. We don't discuss the dialog itself.
Comment 18 Srinivasa Ragavan 2008-08-12 12:11:38 UTC
(In reply to comment #17)
> Srini: We talk about the bad and confusing strings of the buttons. We don't
> discuss the dialog itself.

My comment was for Michael and David Moore. Atleast, thatz what I got from it. 

Comment 19 David Moore 2008-08-12 15:45:38 UTC
(In reply to comment #16)
> But surely, I did heard from multiple people that the dialog is useful.

Can you please explain how it's useful?
Comment 20 Matthew Barnes 2008-08-12 20:21:59 UTC
(In reply to comment #16)
> evolution --disable-preview does similar to what Michael suggessted.

The suggestion is to disable the mail/task/memo _selection_ instead of fiddling with preview pane visibility.  --disable-preview fiddles with preview pane visiblity.  No selection == nothing in the preview pane == user has a chance to avoid a rendering crash.

Having lived with the crash recovery dialog for awhile now, I think I'd prefer to kill it and just silently unselect everything on startup after a crash.
Comment 21 André Klapper 2008-08-12 20:45:09 UTC
I should spend more time to actually *read* the bug reports. I love the latest idea. Get rid of that dialog, save us the strings, the confusion, and the poor user docs section for it.
Comment 22 Srinivasa Ragavan 2008-08-13 04:04:15 UTC
(In reply to comment #19)
> (In reply to comment #16)
> > But surely, I did heard from multiple people that the dialog is useful.
> 
> Can you please explain how it's useful?

Much easier than before to recover from a crash on last selected mail than manually modifying cmeta file of the last viewed folder.
 

Comment 23 Srinivasa Ragavan 2008-08-13 04:07:14 UTC
(In reply to comment #20)
> (In reply to comment #16)
> > evolution --disable-preview does similar to what Michael suggessted.
> 
> The suggestion is to disable the mail/task/memo _selection_ instead of fiddling
> with preview pane visibility.  --disable-preview fiddles with preview pane
> visiblity.  No selection == nothing in the preview pane == user has a chance to
> avoid a rendering crash.
> 
> Having lived with the crash recovery dialog for awhile now, I think I'd prefer
> to kill it and just silently unselect everything on startup after a crash.
> 

Sounds fine to me, but Im not sure of the feasibility. Shell doesn't offer so much support to the components. This handling should be at the components and shell should be the first point of crash detection. May be we can try extend it.
Comment 24 Matthew Barnes 2008-08-13 11:49:44 UTC
I was thinking along the lines of adding a boolean argument ("select_item", perhaps) to the createView() Bonobo method, though I think only the mailer would currently honor it.  Clunky, but should be good enough for now.

In a post-Bonobo world, where the shell is accessible to components, they could just call something like e_shell_crash_detected().
Comment 25 Matthew Barnes 2008-08-15 19:15:49 UTC
Created attachment 116701 [details] [review]
Proposed patch

I think I got this.  Does away with the startup dialog (and the user docs section for it) and just prevents a message from being selected at startup if a crash was detected.  Implementation follows what I described above.  The shell changes are pretty straight-forward but the mailer took some trial and error to get right.
Comment 26 Srinivasa Ragavan 2008-08-18 03:27:46 UTC
This should work well. UI freeze starts later today. Commit before that and announce.
Comment 27 Matthew Barnes 2008-08-18 04:37:46 UTC
Committed to trunk (revision 36009).  Will announce.