SOLVED: I installed CatchyOS, updated to extra-testing and now on Plasma 6. Seems perfectly fine, and Plasma 5.27.10 looks and feels dated in comparison. Not only Plasma 6 but I got a Calamares install of ZFS as a bonus. I don’t mean to be snarky, as this info may help some folks get Plasma 6 sooner than later on a secondary machine without going down the Neon path.
3 Likes
Or on any regular Arch or derivative like Endeavor by switching to the Testing repos.
You can also get it from KaOS without changing repos at all, and test it directly from the ISO if you like.
Or probably dozen other ways.
1 Like
It looks and feels 99% the same to me. 
3 Likes
To me that means most, if not all customizations work as they should, which is very good in my opinion especially if you think about the Gnome 45 upgrade…
2 Likes
I mean, I don’t use any customizations. I also removed all or most of the plasma settings and cache in .config and .cache. The most annoying thing for me at the moment is long 30 second ksplash animation after logging in.
Same. I’ve spent quite a lot of time optimizing my startup time, so that all of my mounts are automounted when they necessary only, not from the beginning. I’ve also delayed the start of many services until after login only. I think my splash screen is about 10 seconds.
$ systemd-analyze
Startup finished in 8.190s (firmware) + 3.426s (loader) + 4.740s (kernel) + 7.270s (userspace) = 23.628s
graphical.target reached after 7.241s in userspace.
$ systemd-analyze --user
Startup finished in 152ms (userspace)
default.target reached after 152ms in userspace.
But I do have quite a few customizations, I think.
That’s probably the best endorsement I have seen yet…
I already have ‘Extract and Delete Archive’ - it’s now built in, and it seems the changes are all positive at least.
Well, I’ve got it up-and-running, in a QEMU VM running EndeavourOS, and…well, let’s say I’m impressed.
Quite obviously some of the more custom things, like my Window decorations for example, aren’t working, which I’m guessing is because they’re not available for 6 yet.
But most, if not all of my other customizations are working. Even my theme is available, so that’s very cool.
I’m still in no hurry to switch, but considering that is Wayland it makes me feel much calmer for when the time comes that I have to.
Installed KaOS in a VBox virtual machine, and as long as X11 is graphics platform it works quite well–even seamless mode . Neon, on the other hand, was impossible to install.
When I tried KaOS however little bit ago it also worked well.
The main issues were that my touchpad was not recognized and the craziness of having a side-oriented panel … on the right.
Neither of which was all that reflective of KDE 6 itself.
Over here on manjaro I forgot about the new SDDM while using sddm-git, so was greeted with an unstyled login page. Same after reconfig. Current repo version works as expected though.
Interesting.
I installed KDE Neon Stable with Wayland and KDE6 using QEMU, and it works fine, including full update. While I tried KaOS, and I could not get it to boot after install.
I’m waiting till Plasma 6 hits Arch stable, then I jump into Manjaro unstable, create a backup, install Plasma 6, and see if it has major breaking points for me. If not, it will stay. If there will be problematic bugs, I restore backup and wait for 6.0.1.
I guess, I also have to remember of backing up home as well, because Plasma 6 may alter configs in some way, that restoring without home may cause issues.
3 Likes
Yeah, I had to set hardware accelerated video to get KaOS to boot…
1 Like
Out of curiosity I added the extra-testing repository from Arch and upgraded to KDE 6 and I can say that everything works fine. In 4 days of experimentation I didn’t encounter any problems.
All I’ve noticed are a few black screen issues after locking the screen in an X11 session, which are solved by simply pressing any button. The wayland based session just works. Themes, plugins and widgets from KDE 5 don’t work as expected, you have to wait for the authors to update them (I heard that they may add backwards compatibility in version 6.1, but I’m not sure). Also the Tor browser behaves strangely in a wayland session, it works on the basis of programmatic rendering, which creates performance problems, but firefox works fine. This problem is not present in KDE 5
If anyone is interested I use the following repository:
[extra-testing]
Server = https://ftp5.gwdg.de/pub/linux/archlinux/extra-testing/os/x86_64/
And an nvidia graphics card.
I don’t suggest you test this on your main computer unless you can take a system snapshot and understand exactly what you’re doing. Good luck
3 Likes
You added arch extra-testing to manjaro? Then it’s a lucky coincidence that everything “works fine”.
1 Like
There’s a better way for this:
I don’t see anything “lucky” about this, I have always used the unstable branch in manjaro and if you look at the composition of this repository you will realize that there are mainly kde, libreoffice and haskell packages. So there are no package conflicts, again I did not suggest using this for those who do not understand what they are doing.
@Mirdarthos
Yes, I saw this topic, oddly enough it didn’t work for me, so I did it differently
1 Like
After the kde-unstable this was the next step
I do something similiar - it is a great way of testing Plasma 6
And with my system - completely compatible …
It’s lucky that nothing in extra-testing depends on something from core-testing, which should also be enabled, FYI.
Maybe, but, there just aren’t any packages out there that could depend on core-testing. If I had included core-testing it would have been a complete hybrid system. In any case, I suggest not to pay so much attention to this “disagreement”.