@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.
@carlschwan @kde@lemmy.kde.social @kde@floss.social
Yeah, RHEL 7 uses it out of the box and is still supported, at least until June 2024: https://www.redhat.com/en/blog/end-maintenance-red-hat-enterprise-linux-7-almost-here
@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.
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.
Zygmunt Krynicki @fosstodon.org zyga aka zygoon, Dad, FOSS programmer, Canonical, ex-Huawei, ex-Samsung. IRC: zyga, GitHub: zyga, GitLab: zyga-aka-zygoon photograph bees and shitpost about the state of FOSS from time to time.
Snapd developer with unlimited enthusiasm.