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 621637 - Canceling closing of compose window does not work
Canceling closing of compose window does not work
Status: RESOLVED DUPLICATE of bug 617557
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[composer]
Depends on:
Blocks:
 
 
Reported: 2010-06-15 13:10 UTC by Pascal Terjan
Modified: 2010-06-16 11:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description Pascal Terjan 2010-06-15 13:10:14 UTC 
(Using 2.30.1.2)

If I start editing an email, then click on the window manager cross to close the window I am asked confirmation.

I can either forget the changes, go on editing or save a draft.

If I say "go on editing" the window gets closed.
Comment 1 Pascal Terjan 2010-06-15 13:16:15 UTC 
Setting importance as critical because this causes data loss.
Comment 2 Akhil Laddha 2010-06-16 11:18:26 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 617557 ***
Comment 3 Pascal Terjan 2010-06-16 11:22:58 UTC 
It does not seem to be a duplicate.
The question is asked, and I don't ask to save, I ask to continue editing.
Comment 4 Akhil Laddha 2010-06-16 11:28:16 UTC 
I tried your scenario and it works fine after fix from bug 617557

specially https://bugzilla.gnome.org/show_bug.cgi?id=617557#c17
Comment 5 Pascal Terjan 2010-06-16 11:31:05 UTC 
OK sorry, reading the patch it seems correct indeed even if it was not intended to fix this one