@Conan_Kudo@fosstodon.org cover
@Conan_Kudo@fosstodon.org avatar

Conan_Kudo

@[email protected]

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

This profile is from a federated server and may be incomplete. View on remote instance

Conan_Kudo , to Random
@Conan_Kudo@fosstodon.org avatar

Now, @sysrich is introducing @opensuse Aeon at !

Conan_Kudo , to Random
@Conan_Kudo@fosstodon.org avatar

Now at , @89luca89 presents how to use to develop software on @opensuse Aeon!

Conan_Kudo ,
@Conan_Kudo@fosstodon.org avatar

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

kde , (edited ) to KDE
@kde@floss.social avatar

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!

This is @druonysus and he needs help managing the KDE booth at Scale 21x.

https://floss.social/@[email protected]/111887967308318720

If you are located in or visiting the Los Angeles area on the days of the event, DM Drew so you can just turn up and help!

@kde

Conan_Kudo ,
@Conan_Kudo@fosstodon.org avatar

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

zygoon , to KDE
@zygoon@fosstodon.org avatar

There's some mismatch between Linux kernel 3.10 and that wants to use clone3 to create a process thread.

Do I know anyone from @kde @kde 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.

Conan_Kudo ,
@Conan_Kudo@fosstodon.org avatar

@zygoon @carlschwan @kde @kde 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 ,
@Conan_Kudo@fosstodon.org avatar

@zygoon @carlschwan @kde @kde 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.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • All magazines
    •