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 @carlschwan @kde@lemmy.kde.social @kde@floss.social The clone3() call is done implicitly and automatically by glibc. It started with glibc 2.34. This is most likely a problem in the Ubuntu Core 22 runtime that KDE snaps are built on.
The fix is to patch out the logic that uses it for clone() in Ubuntu’s glibc.