Left over Flatpak processes

[Gnome Evolution - General mailing list]

[Linux Mint 19.3, Evolution 3.38 via Flatpak]

I'm not sure where the problem exists, so I'm posting here first. When
I close Evolution, I'm left with a bunch of processes that do not close
properly. Here's an example of the open processes on startup:

$ ps -ef | grep evolution
me  2527     1  0 17:53 ?        00:00:00 /usr/libexec/flatpak-bwrap --
args 33 evolution
me  2587  2527  0 17:53 ?        00:00:00 /usr/libexec/flatpak-bwrap --
args 33 evolution
me  2638  2587  0 17:53 ?        00:00:00 /bin/sh /app/bin/evolution
me  2715  2638  0 17:53 ?        00:00:00 /app/libexec/evolution-
source-registry
me  2985  2638  0 17:53 ?        00:00:00 /app/libexec/evolution-
addressbook-factory -r
me  3044  2638  0 17:53 ?        00:00:00 /app/libexec/evolution-
calendar-factory -r
me  3066  2638  1 17:53 ?        00:00:09 /app/bin/evolution.bin
me  3150  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-data-
server/evolution-alarm-notify

...and after shutdown:
$ ps -ef | grep evolution
me  2587     1  0 17:53 ?        00:00:00 /usr/libexec/flatpak-bwrap --
args 33 evolution
me  2715  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-
source-registry
me  2985  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-
addressbook-factory -r
me  3150  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-data-
server/evolution-alarm-notify

So far, when killing these processes (via 'flatpak kill
org.gnome.Evolution') and restarting Evolution, I have not had any
problems show up. I guess the question is: should I be concerned about
this? If you think this is a Flatpak-related problem, then I'll post on
their list.

P.S.: all of the minor glitches I've experienced in the past have been
fixed, so kudos to the devs.
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Pete Biggs]

>
> ...and after shutdown:
> $ ps -ef | grep evolution
> me  2587     1  0 17:53 ?        00:00:00 /usr/libexec/flatpak-bwrap --
> args 33 evolution
> me  2715  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-
> source-registry
> me  2985  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-
> addressbook-factory -r
> me  3150  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-data-
> server/evolution-alarm-notify
>
> So far, when killing these processes (via 'flatpak kill
> org.gnome.Evolution') and restarting Evolution, I have not had any
> problems show up. I guess the question is: should I be concerned about
> this? If you think this is a Flatpak-related problem, then I'll post on
> their list.
>

I don't know anything about flatpak and how it's supposed to work, but
those evolution processes are left because they are potentially used by
other parts of the Gnome system. Whether it is appropriate, or
sensible, to leave them running in a flatpak environment is another
matter; but they are left running normally.

There's no problem killing them: evolution will just start new ones
when necessary.

A question though, if you restart flatpak evolution without killing
those processes, does it re-use those same registry/factory processes
or does it start new ones? If the latter, then they should die along
with the main evolution process, otherwise you're going to end up with
possibly a load of useless processes.

P.

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Gnome Evolution - General mailing list]

On Sat, 2020-09-26 at 10:15 +0100, Pete Biggs wrote:

>
> >
> > ...and after shutdown:
> > $ ps -ef | grep evolution
> > me  2587     1  0 17:53 ?        00:00:00 /usr/libexec/flatpak-
> > bwrap --
> > args 33 evolution
> > me  2715  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-
> > source-registry
> > me  2985  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-
> > addressbook-factory -r
> > me  3150  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-
> > data-
> > server/evolution-alarm-notify
> >
> > So far, when killing these processes (via 'flatpak kill
> > org.gnome.Evolution') and restarting Evolution, I have not had any
> > problems show up. I guess the question is: should I be concerned
> > about
> > this? If you think this is a Flatpak-related problem, then I'll
> > post on
> > their list.
> >
> I don't know anything about flatpak and how it's supposed to work,
> but
> those evolution processes are left because they are potentially used
> by
> other parts of the Gnome system. Whether it is appropriate, or
> sensible, to leave them running in a flatpak environment is another
> matter; but they are left running normally.
>
> There's no problem killing them: evolution will just start new ones
> when necessary.
>
> A question though, if you restart flatpak evolution without killing
> those processes, does it re-use those same registry/factory processes
> or does it start new ones? If the latter, then they should die along
> with the main evolution process, otherwise you're going to end up
> with
> possibly a load of useless processes.
>

At first glance, it looks like a new instance of Evolution is reusing
the old processes. Thanks for the info.
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Gnome Evolution - General mailing list]

On Sat, 2020-09-26 at 10:15 +0100, Pete Biggs wrote:

>
> >
> > ...and after shutdown:
> > $ ps -ef | grep evolution
> > me  2587     1  0 17:53 ?        00:00:00 /usr/libexec/flatpak-
> > bwrap --
> > args 33 evolution
> > me  2715  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-
> > source-registry
> > me  2985  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-
> > addressbook-factory -r
> > me  3150  2587  0 17:53 ?        00:00:00 /app/libexec/evolution-
> > data-
> > server/evolution-alarm-notify
> >
> > So far, when killing these processes (via 'flatpak kill
> > org.gnome.Evolution') and restarting Evolution, I have not had any
> > problems show up. I guess the question is: should I be concerned
> > about
> > this? If you think this is a Flatpak-related problem, then I'll
> > post on
> > their list.
> >
> I don't know anything about flatpak and how it's supposed to work,
> but
> those evolution processes are left because they are potentially used
> by
> other parts of the Gnome system. Whether it is appropriate, or
> sensible, to leave them running in a flatpak environment is another
> matter; but they are left running normally.

Having run both the native and the flatpak version of evolution ... the
behavior is the same for both.  Exiting the main gui in either version
leaves the same processes running.

With the flatpak version, you also get flatpak-bwrap processes left
running as well as an unkillable  evolution.bin process.



_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Gnome Evolution - General mailing list]

On Sat, 2020-09-26 at 11:34 -0500, Japhering, Anonymous via evolution-
list wrote:
> Having run both the native and the flatpak version of evolution ...
> the
> behavior is the same for both.  Exiting the main gui in either
> version
> leaves the same processes running.
>
> With the flatpak version, you also get flatpak-bwrap processes left
> running as well as an unkillable  evolution.bin process.

I'm finding that using 'flatpak kill org.gnome.Evolution' will properly
shutdown everything (flatpak version 1.8.2).
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Gnome Evolution - General mailing list]

On Sat, 2020-09-26 at 03:12 +0200, Douglas Summers via evolution-list
wrote:
> should I be concerned about this?

        Hi,
as had been said in the other replies to this thread, it's normal to
see those processes running. The evolution-alarm-notify makes sure you
receive notifications about upcoming meetings/events/tasks, without it
running you cannot get anything. The process uses evolution-calendar-
factory (weird it's not in your list), which in turn can use the
evolution-addressbook-factory (the Birthdays & Anniversary calendar)
and all these three talk to the evolution-source-registry. The
factories can close on their own when nothing else talks to them for
more than 10 seconds (when all clients are gone). The source registry
is left running ad infinity/till the session end.

These are part of the Evolution's Flatpak sandbox, not talking to the
host system processes.

I hope this makes things a bit clearer.
        Bye,
        Milan

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Gnome Evolution - General mailing list]

On Tue, 2020-09-29 at 09:53 +0200, Milan Crha via evolution-list wrote:

> On Sat, 2020-09-26 at 03:12 +0200, Douglas Summers via evolution-list
> wrote:
> > should I be concerned about this?
>
>         Hi,
> as had been said in the other replies to this thread, it's normal to
> see those processes running. The evolution-alarm-notify makes sure
> you
> receive notifications about upcoming meetings/events/tasks, without
> it
> running you cannot get anything. The process uses evolution-calendar-
> factory (weird it's not in your list), which in turn can use the
> evolution-addressbook-factory (the Birthdays & Anniversary calendar)
> and all these three talk to the evolution-source-registry. The
> factories can close on their own when nothing else talks to them for
> more than 10 seconds (when all clients are gone). The source registry
> is left running ad infinity/till the session end.
>
> These are part of the Evolution's Flatpak sandbox, not talking to the
> host system processes.
>
> I hope this makes things a bit clearer.
>         Bye,
>         Milan
>

Thanks for this, Milan. I wonder if the calendar processes are shutdown
because I've disabled all Evolution notifications/reminders (using my
phone instead)?
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Gnome Evolution - General mailing list]

On Tue, 2020-09-29 at 18:05 +0200, Douglas Summers via evolution-list
wrote:
> I wonder if the calendar processes are shutdown
> because I've disabled all Evolution notifications/reminders (using my
> phone instead)?

        Hi,
I suppose you disabled it in the system, not in Evolution. The
evolution-alarm-notify doesn't know the system settings, it's the
opposite. It always sends the notification, but the system ignores it
when it's off. On the other hand, when you disable all calendars/task
lists in Evolution in Edit->Preferences->Calendar and Tasks->Reminders
tab, then the evolution-alarm-notify doesn't have opened any calendar,
thus the evolution-calendar-factory has no client, thus it closes on
its own.

That's my theory at least. There's also an option that the calendar
factory crashed for some reason.

        Bye,
        Milan

_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list

[Gnome Evolution - General mailing list]

On Wed, 2020-09-30 at 08:35 +0200, Milan Crha via evolution-list wrote:

> On Tue, 2020-09-29 at 18:05 +0200, Douglas Summers via evolution-list
> wrote:
> > I wonder if the calendar processes are shutdown
> > because I've disabled all Evolution notifications/reminders (using
> > my
> > phone instead)?
>
>         Hi,
> I suppose you disabled it in the system, not in Evolution. The
> evolution-alarm-notify doesn't know the system settings, it's the
> opposite. It always sends the notification, but the system ignores it
> when it's off. On the other hand, when you disable all calendars/task
> lists in Evolution in Edit->Preferences->Calendar and Tasks-
> >Reminders
> tab, then the evolution-alarm-notify doesn't have opened any
> calendar,
> thus the evolution-calendar-factory has no client, thus it closes on
> its own.
>
> That's my theory at least. There's also an option that the calendar
> factory crashed for some reason.
>

I think is was the latter. I checked the processes last night after I
shutdown Evolution in preparation for a reboot and the calendar was
still running.
_______________________________________________
evolution-list mailing list
[hidden email]
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list