overview for Conan

The Adwaita Icon Theme no longer follows the FDO icon naming spec breaking KDE applications on Fedora 40 Workstation and Co. in c/kde@lemmy.kde.social

[–] Conan_Kudo@fosstodon.org 10 points 6 months ago

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

The Adwaita Icon Theme no longer follows the FDO icon naming spec breaking KDE applications on Fedora 40 Workstation and Co. in c/kde@lemmy.kde.social

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! in c/kde@lemmy.kde.social

[–] Conan_Kudo@fosstodon.org 2 points 9 months ago (1 children)

@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. in c/kde@lemmy.kde.social

[–] Conan_Kudo@fosstodon.org 1 points 10 months ago* (last edited 10 months ago)

@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. in c/kde@lemmy.kde.social

[–] Conan_Kudo@fosstodon.org 2 points 10 months ago (3 children)

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