Software Engineer. Linux systems aficionado and developer in Fedora, CentOS, Mageia, and openSUSE. Ex Red Hat, Inc. Ex Datto, Inc. Views are my own.
Sponsor me if you like my work! https://github.com/sponsors/Conan-Kudo
Business inquiries: https://velocitylimitless.com
@imecth @cullmann @ohyran @UnityDevice @domi Ah, but this is not true. It wasn’t even true when Allan wrote that blog post, and it’s still not true now. As it is, Fedora Workstation has an open ticket about adding the appindicator extension because applications are broken without it and Ubuntu maintains and ships it to support a useful user experience.
Currently the ticket is deferred until we resolve updating the SNI spec.
@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.
@zygoon @carlschwan @kde@lemmy.kde.social @kde@floss.social It’s likely coming from some usage of libseccomp somewhere. This also afflicts the container stack and such, which is why RHEL 9 containers on RHEL 7 are not supported.
Container/sandbox runtimes using libseccomp need to explicitly always allow clone3() through, or otherwise it will not fail correctly on RHEL 7.
@imecth @cullmann @ohyran @UnityDevice @domi It wasn’t true when Allan wrote that blog post, and it’s still not true now. If you drop XEmbed and only support SNI (as Plasma did years ago), you have one way to handle it. As it is, Fedora Workstation has an open ticket about adding the appindicator extension because applications are broken without it and Ubuntu maintains and ships it to support a useful user experience.
Currently the ticket is deferred until we resolve updating the SNI spec.