Skip Navigation
You know how a lot of people say they would love to contribute to Free Software but can't code? No more! Become a KDE Booth Buddy and help out at ScaLE!

  • @Bro666 @Bigou It shouldn't break anything. We explicitly have KDE PIM as a separate install group because people want to remove it or make custom minimal installs. It *does* reduce the functionality of KDE Plasma, but it shouldn't break it.

    •
    There's some mismatch between Linux kernel 3.10 and [#KDE](https://fosstodon.org/tags/KDE) that wants to use clone3 to create a process thread.

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

    •
    There's some mismatch between Linux kernel 3.10 and [#KDE](https://fosstodon.org/tags/KDE) that wants to use clone3 to create a process thread.
    • There's some mismatch between Linux kernel 3.10 and [#KDE](https://fosstodon.org/tags/KDE) that wants to use clone3 to create a process thread.

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

    • Conan_Kudo Neal Gompa (ニール・ゴンパ) :fedora: @fosstodon.org

    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

    Posts 0
    Comments 3