Yeah, most newcomers don’t even know about the spins and labs since they are quite hidden. So this is a great thing for getting Fedora KDE Spin on an equal footing in visibility and promotion.

Install pam_pkcs11 package, which contains the missing library

They do give a refund for this. I got it after they added it to EA Sports WRC. Explained to them that it was not in the original contract and that it prevents me using the product I licensed on Steam Deck and GNU/Linux and they refunded me.

Well and behind it is stealing other peoples’ work (posts and comments, moderation and administration) and selling them as yours. The oldest capitalist criminal trick in the book: privatization AKA primitive accumulation AKA enclosure of the commons.

KDE Plasma on all my computers and also as desktop mode on Steam Deck. because it supports the latest technologies especially when it comes to graphics (HDR, VRR) also has best support for Wayland and multi-monitors. It looks great out of the box and it has a lot of features out of the box and I do not need to battle with adding some extensions that break with almost every update. KDE Plasma is also the most flexible desktop and I can set the workflow really to fit my desires and I can actually set many options and settings. And despite all these built-in features and configurability it still uses very few system resources and is very fast and smooth. Oh and the KDE community is one of the most welcoming I have met in FOSS world, and they listen to their users instead of the our way or the high way mentality I have so often encountered in GNOME for example. So yeah TLDR KDE Plasma is the one I like the most of all in the industry, even when compared to proprietary closed alternatives.

Agree with this. Also they extensively use OpenQA CI and testing framework and it is what makes the rolling release openSUSE Tumbleweed the most stable rolling release distribution I have used since they can quickly catch an updated package that would cause problems and halt it being introduced. And even if something problematic would get through they really have excellent integration of BTRFS snapshoting with zypper and GRUB and system in general so you can easily boot from the last known working snapshot before the problematic update. And I would also say they have the best integration of KDE Plasma and KDE software of any distro out there. so yeah for these reasons I also consider openSUSE the bets GNU/Linux distribution out there.

KDE Plasma desktop and apps also have a Kiosk mode/framework for deployment and lockdown built-in, that can come in handy

Kiosk - Simple configuration management for large deployment

The Kiosk framework provides a set of features that makes it possible to easily and powerfully restrict the capabilities of a KDE environment.

Introduction

The Kiosk framework provides a set of features that makes it possible to easily and powerfully restrict the capabilities of a KDE environment based on user and group credentials. In addition to an introductory overview, this article covers configuration setting lock down, action and resource restrictions, assigning profiles to users and groups and more.

As far as I remember you can only compare after you upload a benchmark test/suite result to the site. For example when you upload a VkMark benchmark your result should be shown on that test page under Recent Test Results. You can then select your result and some other to compare them. And if you select to re-run a test suite from Latest Test Results the text at the top gives you the command to run it and automatically compare the results, e.g. for GPU CPU HDD Usage and Temperature test Unigine Heaven Fullscreen 2560x1440:

Compare your own system(s) to this result file with the Phoronix Test Suite by running the command: phoronix-test-suite benchmark 2410251-MRPI-241025885

Better to use Kubuntu edition, much better desktop and less crap that is nowdays in Ubuntu.

Already reported on bugs.kde.org.

I don’t. Had very bad experience with these and toxicity they enabled on Xitter and one of the main reasons why I left it for mastodon quite early. I would much more like to see if they focused on making it possible to also migrate posts when you change an instance/server.

I use the testing ebuilds system-vide.

Best to report the issue you have with as much information as possible to bugs.kde.org

Installed on my openSUSE Tumbleweed and Gentoo computers and so far Plasma 6.2 working great 👍

Cloning the system and home partitions always worked fine for me with openSUSE Tumbleweed with KDE Plasma desktop. Another option openSUSE offers is AutoYaST

AutoYaST is a system for unattended mass deployment of openSUSE Leap systems. It uses an AutoYaST profile that contains installation and configuration data.

Anyone else having the problem with the new kernel that graphics in games/benchmarks is quite a lot slower (about 15-20%) then with older kernel (I used 6.10.7 before I upgraded). This is with Powercolor Hellhound AMD Radeon RX 7900 GRE? Even Einstein@Home GPU tasks take about 20% longer now (28 min with previous kernel to about 34 min now).

Nope. here it is about the good DRM: Direct Rendering Manager

It’s the heavy graphics used which looks like it uses WebGL and this is disabled in LibreWolf since it can easily be used for fingerprinting a user. It would be great if they could not use such heavy graphics if WebGL is not supported and just used simple static image or something like that. Well it would be great in general not just for privacy reasons.

From my experince AMD drivers are pretty close, I’d even say slightly better on GNU/Linux, definitely more stable and consistent. For Nvidia, yeah they are bad at supporting GNU/Linux. Improved a lot through the years but still not there. For Intel, well not exactly an option for gaming, at least not the integrated GPUs I have used so far, but still better than in Windows in a similar way as in AMD case.

P.S. Another great thing with libre/opensource GNU/Linux drivers: When you report a bug with Mesa3D drivers the bug is quite quickly fixed, especially when you can provide them with backtrace and/or Vulkan/OpenGL API trace. Doing a bisect of source code commits amd identifying the commit that introduced a regression also help a great deal. Good luck doing the same with closed/Windows drivers: you can wait for years and no fix.

It’s totaly messed up in general and has been for a long time. They try to hack it for the new CPU model and stab you in the back for older CPUs, I’d say it is FUBAR.