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 752532 - Closing a search makes embedded composers disappear
Closing a search makes embedded composers disappear
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: composer
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 795219
Blocks:
 
 
Reported: 2015-07-17 14:48 UTC by Alberto Ruiz
Modified: 2019-08-02 02:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Backtrace with 0.10 (5.88 KB, text/plain)
2016-04-12 05:50 UTC, Michael Gratton
Details

Description Alberto Ruiz 2015-07-17 14:48:46 UTC
I did a conversation search, and while I was editing a reply I cleared the search entry box, a dialog showed up asking me to discard the draft or cancel the operation, I cancelled. Then the conversation list was empty and the conversation window was empty too. I clicked on Drafts and the same dialog appeared again, after clicking cancel for the second time the application crashed.
Comment 1 Michael Gratton 2016-04-12 05:50:22 UTC
Created attachment 325762 [details]
Backtrace with 0.10
Comment 2 Michael Gratton 2017-02-28 14:14:46 UTC
No longer crashing on current master, but hitting Cancel still lets the composer disappear, which is bad.
Comment 3 Michael Gratton 2019-08-02 02:29:35 UTC
Once https://gitlab.gnome.org/GNOME/geary/merge_requests/270 lands, a Discard/Cancel/Keep prompt will now be issued. Discard and Keep works as expected and the composer will be closed. If Cancel is selected, the composer will remain open, but the conversation list will be in an odd state.

This is better than before, and while the real fix is to cancel closing the search if Cancel is clicked, that's a lot of work for a corner case that will go away once we get persistent composers in the main window.

As such, while it's not perfect, marking as fixed.