https://bugs.kde.org/show_bug.cgi?id=417791
--- Comment #20 from Zygmunt Krynicki <m...@zygoon.pl> --- I think this is something we could look at fixing but the problem is that the userspace application must fall back to older clone version that is supported by the kernel. I will try to see if fixing the seccomp side unblocks the userspace to do the right thing. W dniu 3.01.2025 o 15:09 Scarlett Moore pisze: > https://bugs.kde.org/show_bug.cgi?id=417791 > > --- Comment #19 from Scarlett Moore <sgmo...@kde.org> --- > (In reply to Zygmunt Krynicki from comment #17) >> Hello, I'm one of the snapd maintainers in Fedora and EPEL. >> >> I just tested several snaps on RHEL 7, running kernel 3.10.0-1160.105.1.el7 >> with snapd 2.58.3-1.el7 on x86_64 and they all fail on startup due to the >> use of `clone3` that fails with EPERM. The system call is allowed by the >> source seccomp profile but is, most likely, not supported by seccomp used in >> the distribution or by the kernel alike. > > Alright, this bug needs to be filed with snapd then. Not something I can fix > on > my end. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
