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

Thanks for reporting about your experiences here.

I’m using hardly any customization on my Plasma6-setup (and Plasma5-setup for that matter), so it’s good to know about what happens when you do customize. Other people have noticed similar problems, I believe.
As such my use case is rather boring as a test-scenario.

Widgets/extensions are indeed lagging behind. Let’s hope that once Qt6/Plasma6 is less of a moving target, people will start updating their widgets as well.

1 Like

Hurray! :slight_smile:

Some problems found so far:

  • CPU and Memory usage widgets crash the entire shell if I clicked (expected behavior is to open a popup with detailed information). I thought it was the old version, I removed it and installed it directly from the widget panel, but the problem persisted. It’s not exactly a problem, since I only need them to view system information, I just don’t click.

    Screenshot_20240218_124141

  • I’m finding the memory consumption excessive, at least on my system. It’s starting with 1.8~2GB, whereas previously on Plasma 5 it was somewhere between 1.1 GB. When I open Firefox, watching a simple video on YouTube and the forum tab open, it was consuming 7.2 GB. I opened 2 more tabs now, from a Google search and a shopping site and it jumped to 10.5 GB!
    Is there a memory leak somewhere?
    I looked at the system monitor and the plasmashell was consuming half of the total RAM usage. Firefox at 2 GB, the rest are other KDE applications in the background.

  • From time to time I notice some stutters in the system. Using the FPS extension, it shows that kwin is framepaced, running between 58~60 fps all the time. Then when you open some applications, or use something like YouTube in 4K, the stutters are a little more aggressive, going at 40 fps. It could be due to the Nvidia driver, I’m using the 545.

Which widgets are you using? I’ll see if I can reproduce.

I’ll look at memory consumption on my Plasma 6 tomorrow.
On Plasma 5 with only FireFox, I´m seeing 2.04 Gb memory usage. Which is more than you experience?

Have you looked at bugs.kde.org to see if people have reported similar symptoms?

1 Like

I’ll take a look, I had looked on that site earlier about widgets, but nothing very conclusive, the search there is not very precise. Regarding memory usage, mixed responses, but many said that Wayland was the main culprit, but again, nothing very conclusive.

Usage is currently very low. I went to lunch, closed all open apps and left just the desktop empty. When I started using the PC again, the usage was no longer as high, now it is around 6 GB. When I monitored earlier, the one that increased memory usage was the plasmashell.

About the widgets, they are Total CPU usage and Memory Usage. These are widgets that already come with Plasma, I added them to the taskbar.

I’m also using Weather3, which I downloaded from Github, but I’ve already tested without it and it doesn’t seem to be the culprit (but maybe it’s the culprit of the memory leak, I’ll test again without it).

Sorry, I’m not able to do much testing ATM- things happened that need my attention now.

1 Like

Going to nuke KDE when they have there final release here soon, seems to be CPU hog compared to Gnome. Might try it again in 6 months to see if things have improved but it was fun testing.

2 Likes

could also be an issue where Plasma falls back to software rendering instead of using Vulkan/OpenGL. If you have time, you could try to investigate further.
In case you test in a VM, that could also be the cause for Plasma to use software rendering.

If Plasma 6 would be generally CPU hungry, it would definitely worry the devs, too.

1 Like

Yes using QEMU for testing, using the same settings for Gnome and KDE, both with Wayland.

Apparently Plasma 6 is ready enough to be used as sales argument:

https://kde.slimbook.es/

4 Likes

lol as a computer geek, it always surprises me how much people value pre-installed software.
Well, my outstanding bugs list are: the screen dimming that doesn’t restore brightness and shutdown/restart that doesn’t work without the workaround (I read that as a bug).
Still disappointed that the plugins basically still haven’t been updated.
Two days to release…

https://community.kde.org/Schedules/Plasma_6
Release is next week and weekly bugfix releases after

1 Like

Whoops, can I plead eye surgery (2 days ago)? Really just skimming to blame though :slight_smile: Anyway, it’s close…

I hope it went well!

2 Likes

yeah, but I am pretty sure that Arch will never see 6.0.0 in stable. I don’t even expect 6.0.1 to come to stable. 6.0.2 in stable could happen though.

So that i understand: if this is the case, this will mean that the normal repos of arch/eos will not get Plasma 6 until plasma 6.0.2 is released?

We don’t really know (I think) what the devs will do. I presume their presumption is based on past evidence of such releases.

The actual, specific versioning number is irrelevant as it is not up to the KDE (or, equivallently, GNOME) devs and their products’ lifecycles, but rather up to the distro’s definition of “stable”.

Arch GNOME never lands at .0 release, as those are treated as unstable.
GNOME releases land on stable at least after the X.1 stage of the lifecycle.
Not sure what’s the case with KDE specifically, but it would make sense that it’s similar if not exactly the same.

Essentially it will land in stable, when it is considered just that (stable) by Arch packagers/maintainers.

1 Like

For the moment Plasma update come 2/3 days after testing in the unstable repo. IMO its probably going to be even faster this time.

KDE is asking the widget developers to port their widgets to plasma 6.

2 Likes