There's some mismatch between Linux kernel 3.10 and #KDE that wants to use clone3 to create a process thread.
There's some mismatch between Linux kernel 3.10 and #KDE that wants to use clone3 to create a process thread.
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.
You're viewing a single thread.
@zygoon @kde@lemmy.kde.social @kde@floss.social because any reasonable implementation will treat EPERM from a process creation system call as a fatal error. If this is e.g., blocked through seccomp. ENOSYS is the correct error to return. It's just naive seccomp sandboxes that started this EPERM nonsense. So I'd rule that out first. Unless you're using something that requires specific capabilities such as creating a process with a specific PID. That can legitimately return EPERM.
@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.