Open sunweaver opened 4 years ago
Hmm. I kill it regularly when testing things, but it never affects the indicator - could you provide some specifics? You know, what exactly you do, what exactly happens :)
note that my messages indicator is started via XDG autostart (so a one-time shot)...
If you already use the ayatana-indicators.target for systemd, you won't notice the "crash" of the messaging indicator, because systemd will restart the indicator immediately.
I am logging into a Debian MATE session, kill the process ID of the ayatana-webmail process and then the messages indicator disappears from the panel.
This is going to be hard for me to test, but I remember something from the Ubuntu days: When you booted with unity-mail autostart disabled, and the messages indicator had no other clients, it did not show up. The minute you started-u-m and it registered itself, the indicator showed up. The same was true for murder: if you killed the last client of the indicator, it went away (if there were more clients, it stayed). I guess this was a "feature".
I am wondering if the ayatana version really crashes when a-w is killed, or just decides it is time to go away because it has no clients.
I think we should move this to ayatana-indicator-messages.
@sunweaver
I have just re-tested it with the current git build, the issue is no longer present. I may have magically fixed it during the CMake transition. I would like to close this, but it would be nice if you could confirm my findings.
When killing
ayatana-webmail
, the messages indicator dies with it. This should not happen IMHO.