Skip Navigation

Zygmunt Krynicki
Zygmunt Krynicki @ zygoon @fosstodon.org
Posts
1
Comments
3
Joined
4 yr. ago

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

Jump

  • @ConanKudo @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 that wants to use clone3 to create a process thread.

    Jump

  • @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

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

    Jump

  • @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.

    • KDE @lemmy.kde.social
    Zygmunt Krynicki @fosstodon.org

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