Testing Plasma 6 (Beta) on Endeavour OS - is this approach any good?

Crosspost from : Just say yes to replace - #40 by SemLraug.

I´d like to help test Plasma 6 by installing it on EOS.
I’m no expert or developer, but have some experience with testing.

Would this be the right approach to get set up correctly?

  1. Download Cassini Nova R3 ISO
  2. install it on a spare partition
  3. run yay to update, reboot, login
  4. add kde-unstable to /etc/pacman.conf, as per [1]
  5. run yay to update to get Plasma6 on board
  6. reboot
  7. start using the install

Step 8) would be: report any bugs I encounter. But I’m unsure as to where Plasma-bugs are supposed to be submitted. I did find where and how to report KDE-bugs[2], but is that the right place for Plasma6 reports?

Any pointers, pitfalls or problems with this approach appreciated.

[1] https://wiki.archlinux.org/title/Official_repositories#kde-unstable
[2] https://community.kde.org/Get_Involved/Issue_Reporting


The plasma 6 packages all have different names so think you would have to actually install them.

Yes. Assuming they are bugs with KDE and not packaging bugs.

That looks like the way to go. The 6 alpha should drop next week, we will see.

In the past Arch handled the KDE plasma pre-releases through kde-unstable very well. The recent undergoing package renaming with the (plasma/kde/qt) 5 suffix indicates Arch packagers are on the case.

Best place for reporting bugs is probably [1]. Find the component you have issues with and file it there - try to find it with the “New” button at the top. Don’t worry to much if it fits a particular category a 100%, the KDE people will move it to the right place if necessary. As a version specify “6ish” or “5.<veryHighNumberThatIndicatesAlpha|Beta>” - That isn’t available in the bug filing system yet, but I assume it will pop up soon.

Also search before filing bugs. Esp. in the beginning there’s a high chance for duplicates. Avoiding processing those saves time for the KDE people.

Thanks for the info.

I appreciate duplicates can be a problem.


I tried to find which packages I need to install to fully install Plasma 6 - I have not found many sources [1,2].
The suggestion I found is to build from sources from upstream, which is well beyond my skill level.

If Plasma 6 packages need to be installed, how do I find out which they are?

[1] https://www.reddit.com/r/openSUSE/comments/14oree6/try_plasma_6/
[2] https://www.reddit.com/r/kde/comments/14qhfg0/plasma_6_on_archmanjaroendeavouros/

I am not sure what the plan for packaging them is. They may come in as replacements in which case you won’t need to do anything.

Having already looked at some of the plasma 6 stuff, it’s not that unstable and could possibly be ran as your daily driver (an approach I would suggest before too long in the development cycle). Most things seem basically at parity with KDE5 at present (based on not checking it out a whole lot).
However, for first looks, being isolated sounds like a good game plan. I went with KaOS and let demm do the heavy lifting for my quick look.

1 Like

Would be my preferred approach :rofl:.

When plasma 6 alpha/beta drops on Arch kde-unstable the packages should be offered automatically. They will feature a much higher 5.x version number (in the hundreds) at the beginning, which should also pull required, newer dependencies from kde-unstable in the same range.

If you subscribe to kde-unstable and everything goes well it will just be offered to you automatically.

I supposed testing Plasma 6 specifically on EOS is of some value for the EOS community as well.

Would that be true, though?

That would be ideal for a non-expert like me. :+1:

kde-unstable does not appear to contain Qt6 yet, just v5.24 plasma Qt5:


I found [1]: kde-unstable is normally empty unless there is a beta, it seems.

I’m confused now… :confused:

I’ll do some more digging.

[1] https://lists.archlinux.org/archives/list/arch-general@lists.archlinux.org/thread/VQZZHRL567I5W4PV2T5B35N5MKZITZVT/?sort=date

KaOS is basically Arch (imo), and that’s close enough for me to be comfortable with it.
I don’t think there will be much difference in the desktop between any two Arch derivatives.
I do get using it where you’re most comfortable though. For that matter, there’s value to be gained in looking at differences (but that’s not about KDE6 specifically).

1 Like

It normally is. There are currently framework packages in kde-unstable that will only make sense if the plasma desktop alpha drops - which it didn’t do yet. If you look at kde-unstable those framework packages are versioned at 5.240. The alpha release frameworks will be 245.

Apparently Arch package managers are getting their ducks in the row for a once in decade occasion. Don’t worry.:tm: If you’re on kde-unstable you’ll receive it when it is out.

KaOS isn’t an Arch derivative it all. It uses pacman, but that about it. They do all their own packaging from upstream sources.

I know…but it feels Arch-like (with pacman) and seems a compatible philosophy.


I’ll start preparing my spare partition, install EOS+KDE/Plasma and add kde-unstable.

I assume the resulting system wil be stable enough to use - until they open the sluices on Plasma 6, perhaps. :wink:

Thanks all.

Qt6 is already in the stable repo’s. Plasma 5.240 IS Plasma6 pre-alpha. The 0 in this case is important.

not likely. At the moment, none of those packages in KDE-unstable has a “replaces” or “conflicts” entry. All the Plasma 5 packages currently in stable have the 5 added to their package names, KDE-unstable has no 5 or 6 in their package name. Therefore, it will only be an update when “replaces” entries are added. Without “replaces”, the packages have to be installed manually because they are different packages.
My guess is that Plasma 6 will either nether get a replaces entry, or earliest when Plasma 6 stable is released in February next year

Manually installing it will be easy though, because


So a sudo pacman -S kf6 will install all the packages currently in KDE-unstable. The currently missing packages should also see a groups - entry at least if they remain consistent in package management.

@BS86 thanks for your quick reply. Not sure I understand what you are saying. Let me try:

My “workflow” to get going with testing Plasma 6 is:

  1. Download Cassini Nova R3 ISO
  2. install it on a spare partition
  3. run yay to update, reboot, login
  4. add kde-unstable to /etc/pacman.conf, as per [1]
  5. run sudo pacman -S kf6 to get pre-alpha Plasma 5.240/Plasma6 on board
  6. reboot
  7. start using the install
  8. run sudo pacman -S kf6 regularly to get updates and packages which will be added later
  9. report bugs as per [2].

[1] https://wiki.archlinux.org/title/Official_repositories#kde-unstable
[2] https://community.kde.org/Get_Involved/Issue_Reporting