GNOME Bugzilla – Bug 792779
Evolution related processes remain active after application is closed
Last modified: 2018-01-26 07:05:47 UTC
Created attachment 367208 [details] screenshot I noticed that even after closing Evolution and waiting for some minutes several processes named evolution* remain active. openSUSE Leap 42.3, Plasma desktop.
Thanks for a bug report. Please note that except of evolution-alarm-notify (which comes from evolution) all other processes are from evolution-data-server (eds) and they are left running as long as anything is using them. The calendar factory can be used by the evolution-alarm-notify and if also the "Birthdays & Anniversaries" calendar is checked for reminders then that calendar has opened books which are set to be included in this calendar. But those eds processes can be used by any application, it's a "server", shared by many. Once you manage to close every used of the factory it'll close itself after ~10 seconds of inactivity. Note that some desktop environments can use them as well, for example GNOME Shell connects to the calendar factory to fill the clock popup with upcoming events.
Thanks Milan. But why are there such processes when I close Evolution at all? Considering I am not even running GNOME desktop but Plasma. Even without any other desktop app started these remain active.
(from comment #1) > ...The calendar factory can be used by the evolution-alarm-notify... Without it you won't be notified of upcoming events without evolution running. Try to kill it (kill --TERM `pidof evolution-alarm-notify`) then wait for a bit more than 10 seconds. After it, if nothing uses the others, they will be closed automatically.
On my system I have only the package evolution installed. I have never installed any additional packages about alarm or "server" or anything like that. Yet those keep running to infinity unless I kill them all. So the question comes down to: why do I have to kill anything which I didn't even start explicitly? That's why I reported a bug in the first place - because it is not normal an email client to start additional processes and not terminate them after exit.
Evolution is not only about mail. The evolution-alarm-notify is part of evolution. The evolution-alarm-notify is auto-started on system run, due to comment #3. It's also started on evolution run, if not already running. If you do not like it, then mark all your calendars/memo/task lists to not be checked for reminders (Edit->Preferences->Calendar and Tasks->Reminders). Then the evolution-alarm-notify will not be using them and the factories will close. Not the evolution-alarm-notify. Again, see the first sentence in this comment. I feel like we are moving in cycles. If you do not like evolution-alarm-notify, then remove it from the system, thus it could not be found, thus neither run (next package update will probably return it back). You cannot do that from evolution, because it's impossible to know what users want and what to do when they change their mind, like maybe you are not using the calendars/tasks reminders now, but maybe in several weeks/months you will and then you'll complain you are not notified of the reminders. I'm surely not going to change anything in this regard, I'm sorry, but I hope you understand that it's for a good reason.
Thanks for explaining. > The evolution-alarm-notify is auto-started on system run It is not. It seems to start only when Evolution is started. > If you do not like it, then mark all your calendars/memo/task lists to not be checked for reminders (Edit->Preferences->Calendar and Tasks->Reminders). Then the evolution-alarm-notify will not be using them and the factories will close. I disabled all reminders, closed Evolution, killed all evolution* processes, started Evolution and closed it again. The processes still remain running (including evolution-alarm-notify). Is that normal? > if you do not like evolution-alarm-notify, then remove it from the system I don't know if I like it or not (as I haven't really used it). I just found it strange that many processes remain after closing Evolution mail client. Also I can't remove evolution-alarm-notify - it is inside the evolution package, not a separate one.
(In reply to George from comment #6) > I disabled all reminders, closed Evolution, killed all evolution* processes, > started Evolution and closed it again. The processes still remain running > (including evolution-alarm-notify). Is that normal? The evolution-alarm-notify will be left running until session end. As long as it doesn't have any calendar/tasks list/memo list marked for reminders it should not cause the other factories running (only evolution-source-registry). Though I can be wrong with it. The evolution-source-registry will be left running too, until the end of the session. > Also I can't remove evolution-alarm-notify - it is inside the evolution > package, not a separate one. That's why I specifically mentioned the file, not the package.