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

When i reported bugs I did specifically mention that my system was on QT6.7, and that is also what kinfo showed. So, I’m really confused.

This is how @Schlaefer explained it in this thread earlier:

Yeah that strange to “downgrade” the QT version. The following link seem to corroborating what @chalex20 said.
https://community.kde.org/Schedules/Plasma_6

1 Like

If life was fair and logical, then QT would have gone for the release first, then Plasma behind. But well, it all rolls downhill (part of an aphorism)…

1 Like

So it did. Qt 6.6, that is :wink:

1 Like

Do only I use “Help Center” in KDE?

I commented out unstable and added in extra-testing, and I have no GUI. I just rebooted to another partition and didn’t feel like looking into it…but will in the morning.
Did you more successful folks leave extra-testing at the default position in the pacman.conf file?

core-testing is needed too i think… i had the same try first only with extra-testing and was not able to load a session… i had no time checking deeper on that …

If you enable extra-testing, you need also to enable core-testing and multilib-testing.

Postscript: As you mentioned “position”, may as well say that the testing repos must come before the regular.

So, core-testing, then core, then extra-testing, etc.

1 Like

I thought so, but the order in the default file was much lower (after regular for sure).
Well, I’ll boot single-user and make my mods and try again in a bit. Thanks :slight_smile:

1 Like

Thanks - followed this approach and got my KDE without a hitch. Does not look hugely different to KDE 5.27 so far, but it’s very early days.

1 Like

Yeah, seems like a lot of tweaks from 5, TBH. Some big changes to the UI when configuring things.

I was under the impression it would have baked-in auto tiling, so I’m a bit disappointed. I’ll add in the tiling script thing sometime.

I’m back! I stopped testing Plasma 6 on EndeavourOS after RC1 because of the QT 6.7 bugs, and jumped to Fedora Rawhide (which used QT 6.6). I found myself using Plasma 6 on Fedora a lot more than my daily driver Plasma 5.27 build on EndeavourOS. Yesterday, I decided to upgrade my Plasma 5.27 daily driver on EndeavourOS to Plasma 6, after learning that QT was rolled back to 6.6.

So far everything is running smoothly. It’s even smoother than the Fedora build. I guess it’s time to reclaim that hard drive space!

Quick question, how do we disable testing and switch back to main once Plasma 6 is officially released? Is it as simple as disabling the repositories in pacman.conf and running an update?

Yes.

Ok, I spoke too soon. I found two minor issues:

  1. Automatic screen rotation stopped working (I have a tablet PC) and the option is not available in the Display Settings.

  2. The Scarlet Tree (default Plasma 6) wallpaper is not changing to the light version during daytime. It’s still stuck on the dark version that’s used at night.

1 Like

Multilib is new to me.

I got the info about which repositories to add to get testing from

https://wiki.archlinux.org/title/Official_repositories#kde-unstable

Multilib is only relevent if one needs 32bit apps?

According to the Arch forums, that’s a negative. it should be enabled with the other testing repos.

Yes. Basically, you only need to enable multilib-testing if you have multilib enabled. They should either both be enabled or disabled if you are using the testing repos.

As I don’t use 32bit apps, and have not enabled multilib, multilib-testing would not be relevant in my case. That seems to be indicated as I’ve been using my Plasma 6 (testing) setup for months now and have not come across problems which were caused by a missing repository.

As I said, I’m reporting what has been said in the Arch forums.

I’ve seen similar advice within the past month, but this was the first to come up with a quick search.

Either way, YMMV.

1 Like