KDE

5362 readers

104 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago

MODERATORS

carlschwan@lemmy.kde.social

Bro666@lemmy.kde.social

herzenschein@pawb.social

Aniqakhokhar@lemmy.kde.social

KDE Linux is a work-in-progress name of a KDE-owned general-purpose Linux distribution proposed at Akademy 2024 (community.kde.org)

submitted 3 weeks ago by Lemmchen@feddit.org to c/kde@lemmy.kde.social

21 comments fedilink hide all child comments

Non-goals

Does not have to support the runtime installation of kernel modules. This will prevent the out-of-the-box installation of, for example:

Proprietary NVIDIA kernel driver (NVIDIA GPUs must either be new enough to use the open-source kernel modules that can be distributed in-tree, or else use Nouveau)

VirtualBox (requires out-of-tree modules; QEMU/KVM probably do a better job anyway)

Vendor-specific VPNs that require custom out-of-tree kernel modules that cannot be redistributed with the kernel due to license incompatibility

Does not have to support the use case of developing low-level system components like the kernel, drivers, systemd, etc., as this can be troublesome with an immutable base OS.

Does this part mean there will also be no support for ZFS?

you are viewing a single comment's thread
view the rest of the comments

[–] bunitor@lemmy.eco.br 1 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Arch is almost always up to date with the latest stable releases of libraries and Qt making it an ideal base for KDE Plasma which is a fast moving desktop.

are you involved in this project? i have a little bit of a gripe with this approach. unless your idea is to aim this os at enthusiasts instead of the general public, the user should not have to worry about large upgrades that might leave the system in a broken state. this is why debian is always a little behind: making sure a bunch of different components in a million possible different combinations all work well together is hard work and it takes time. i'm not even saying it's not possible to use a rolling release model and have a user friendly distro (opensuse tumbleweed does it pretty well), but reliability comes before software recency imo.

edit: btw this is why i said i'm unsure making an os is the job of application developers. what's ideal for the developers might not be ideal for users.

[–] justin@lemmy.kde.social 2 points 3 weeks ago (1 children)

Yes I am involved in the project. As for not worrying about large system upgrades, things break, no matter how much testing you do on them. For running KDE I prefer to run the latest, it has the least bugs and the newest features.

There will be at minimum 3 editions of this OS, one for developers and those who love to live on the bleeding edge, one for enthusiasts and one for general users. The one for general users will be well tested and aim to have zero showstopping bugs.