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

Yeah, I tried it and can verify that it breaks everything. Thankfully, I didn’t prevent packages from being upgraded by pacman. I had to chroot into my system and do an update to fix my screwup.

1 Like

Guess we’re just waiting for a lot of things to get fixed downstream with Qt 6.7. At least the latest update fixed system settings pages getting cut off at the top. The only bug I’m really anxious to get fixed right now is the “Get New…” button bug. I hate not being able to install icons and themes from inside system settings.

Edit: Oh joy! I just noticed that Konsole and Dolphin are opening now without the plugin panels being activated! Bugs are being fixed slowly but surely.

I meant to ask earlier, is anyone else getting these weird white dividing lines in System Settings and Discover? I don’t like them…

Thanks for testing it. :+1:t2:

I’ll have a look later today.

I thought that was the normal. Maybe I’m wrong.

Not only that I got them, the whole pane on the right was misaligned vertically; the topmost part was cut out.

This is what it looks like on my setup.

I don’t know what it should look like, though.

1 Like

I’ll check my color scheme. My dividers are too pronounced.

I’m on breeze dark.

Same here. :+1:t2:

Just ran the latest update and the dividers seem to be less pronounced:

Or am I seeing things? :thinking:

The only bug I’m really anxious to get fixed right now is the “Get New…” button bug

Do you use window previews in the task manager?

Is anyone else having any problems with “Suspend” (after inactivity of X minutes) with Plasma 6.0 RC1? I am on KDE-unstable and the testing repositories and use Wayland (and have a NVIDIA graphics card). When I try to resume after Suspend, I just get a black screen with a cursor and no way to move forward.

It seems KDE specific because if I log into a Gnome (Wayland) session, Suspend works fine. The only alteration I’ve made to my system is I use a /etc/sddm.conf.d/10-wayland.conf file (per https://wiki.archlinux.org/title/SDDM) with the following in it:

[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1```

I haven’t had issues, but then Wayland and AMD get along better than Nvidia.
It sure is nice to see the konsole w/o all that stuff…and the little formatting problems, as Nate’s blog mentioned correcting text formatting.

1 Like

I’m not using suspend at all, so can’t say. Hopefully someone else has some ideas.

They’ve found the problem and a merge request has been done.

https://bugs.kde.org/show_bug.cgi?id=479574

1 Like

There have been quite a few reports about nvida+sleep = broke.
Could be https://bugs.kde.org/show_bug.cgi?id=477738 but apparently this stopped beeing an issue for people (or they gave up).

Does this only happen with wayland SDDM?
Can you ALT+F2 and restart plasmashell with plasmashell --replace or switch to a tty and upload a journald log?

Welcome, @Duha! Thanks for chiming in, and helping out.

Thank you very much @Duha for your response. I am unable to get a terminal with ALT+F2 (or any other key combination I tried), so I could not try the plasmashell --replace idea and get the resulting journal. Oddly enough, if I type systemctl suspend in the terminal, it seems to work. Also if I invoke “Sleep” from the Application Launcher, it also seems to work. It’s just when the system puts itself to sleep due to inactivity that I seem to have this problem. I will keep investigating; thanks again.