On Wed, 31 Jan 2024 at 12:00, Michael Catanzaro <mcatanzaro(a)redhat.com>
wrote:
On Wed, Jan 31 2024 at 04:42:08 PM +01:00:00, Clemens Lang
<cllang(a)redhat.com> wrote:
> Throwing some ideas out there, is it possible that evolution runs
> with a seccomp filter or other BPF program configured to kill the
> process on violation, and that’s what’s happening here?
I don't think so. flatpak does use seccomp filters [1], but on
violations the syscalls should just fail with EPERM or ENOSYS, not kill
the process.
Could the problem with evolution be really with something else and getting
masked out ? I saw there was another thread about bogofilter killing
evolution due to the database needing to change from berkeley to sqllite by
running a helper. If the helper is being run but it runs out of memory,
would that cause the whole chain of OOM ?
--
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren