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 730537 - Allow to quit geary with --quit command line
Allow to quit geary with --quit command line
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: client
master
Other Linux
: Normal normal
: 0.12.0
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-05-21 18:30 UTC by Yosef Or Boczko
Modified: 2016-09-24 15:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Yosef Or Boczko 2014-05-21 18:30:19 UTC
See bug 714644#8.
Comment 1 Landry Breuil 2014-12-20 09:52:04 UTC
Yes please - right now, there's no way to exit geary besides killing it the hard way, since when you close its window it will hide itself churning cpu and io in the background. I dont know if in gnome environments its supposed to have an icon in the indicator panel, but in environments with only systrays or taskbars, if you close the window, there's no way to know geary is still running.
Comment 2 Jim Nelson 2014-12-22 21:27:36 UTC
You can fully exit Geary by choosing Quit from the application menu or pressing Ctrl+Q.
Comment 3 Landry Breuil 2014-12-22 21:32:58 UTC
Hah, thanks for the hint. Anyway, that feels so different from usual usage.. when i want an app to stay running in the background, i minimize it, or if it hides itself when using the close button from the WM, at least there's a systray icon showing that it's still here in the background..
Comment 4 Jim Nelson 2014-12-22 21:43:04 UTC
<sigh> ... there's a contentious debate about system tray usage, and it doesn't help that GTK+ keeps threatening to mark that API as deprecated.  The system we landed on for running Geary in the background was the best compromise we could find.
Comment 5 Landry Breuil 2014-12-22 21:44:43 UTC
Don't worry, i dont want to start a flamewar about it, i know it's a hard debate still going on. At least now i know how it behaves :)
Comment 6 Michael Gratton 2016-09-24 15:48:28 UTC
Fix pushed to master as 65c5363.