There's some mismatch between Linux kernel 3.10 and [#KDE](https://fosstodon.org/tags/KDE) that wants to use clone3 to create a process thread. in c/kde@lemmy.kde.social
[-] zygoon@fosstodon.org 1 points 9 months ago

@Conan_Kudo @carlschwan @kde@lemmy.kde.social @kde@floss.social yeah, I strongly suspect seccomp. I’m debugging this now and I will share updates when I get to the bottom of the problem.

There's some mismatch between Linux kernel 3.10 and [#KDE](https://fosstodon.org/tags/KDE) that wants to use clone3 to create a process thread. in c/kde@lemmy.kde.social
There's some mismatch between Linux kernel 3.10 and [#KDE](https://fosstodon.org/tags/KDE) that wants to use clone3 to create a process thread. in c/kde@lemmy.kde.social
[-] zygoon@fosstodon.org 1 points 9 months ago

@brauner @kde@lemmy.kde.social @kde@floss.social

Thanks for the insight. I was surprised by EPERM, would have expected ENOSYS as well.

Looks like EPERM is most likely coming out of unknow system call name being filtered-out by snap-seccomp compiler. I'll update snapd to 2.61.1 to avoid chasing fixed bugs and then see if there's something to improve in the compiler.

1
There's some mismatch between Linux kernel 3.10 and #KDE that wants to use clone3 to create a process thread. (fosstodon.org)
submitted 9 months ago by zygoon@fosstodon.org to c/kde@lemmy.kde.social
7 comments fedilink

There's some mismatch between Linux kernel 3.10 and #KDE that wants to use clone3 to create a process thread.

Do I know anyone from @kde@lemmy.kde.social @kde@floss.social who is able to assist with debugging it further?

The system call clone3 has been added to linux 5.3 but it seems that KDE does not do any fallback in case the system call is rejected with EPERM.

zygoon

joined 3 years ago