KDE Plasma 6.6.0 + Frameworks 6.23 is now in Fedora 43 (And soon in 42)!

Good morning everyone!

We have pushed the KDE Plasma 6.6.0 update AND the Frameworks 6.23.0 update to Rawhide, 44 (Branched) and 43!

For those wanting to test it, you can find the F43 update here: Making sure you're not a bot! You can find the release notes here: Plasma 6.6 - KDE Community

For F42, this will take us a bit more time, but the update will land soon.

12 Likes

will it have plasma login manager as a default in fedora 43

I’m curious to try the new logon manager. Looking at this project page it seems I’ll need to:

sudo systemd-sysusers
sudo systemctl disable sddm
sudo systemctl enable plasmalogin

…and reboot. My F43 system lacks both /etc/plasmalogin.conf and /usr/lib/plasmalogin/defaults.conf – should the defaults be sufficient?

I reckon I’ll set systemd.debug-shell=1 on my kernel command line and give it go. Fools rush in to where angels fear to tread!

PS. Nevermind…

(~)> sudo systemctl enable plasmalogin
Failed to enable unit: Unit plasmalogin.service does not exist

try installing plasmalogin first using sudo dnf install kcm-plasmalogin

seems to be working here by

sudo dnf install kcm-plasmalogin
sudo systemctl disable sddm
sudo systemctl enable plasmalogin

So far I don’t notice much difference to sddm. the only hint is the background image is different

Did all four steps. It works! Versus the original config it seems a little quicker to initially launch and display the password box. Also perhaps faster to logon and start the desktop.

I manually migrated my custom setting NumLock=on from /etc/sddm.conf.d/kde_settings.conf to etc/plasmalogin.conf.

Should Apply Plasma Settings work correctly now? It’s never worked 100% and it still doesn’t push my screen layout into the logon manager config:

Is this being held up by Fedora subject to testing? Or something that will not be pushed by discover until v.44?

It’s being managed as a Change Proposal, so it follows the release cycle and will land (as the default) when F44 releases.

2 Likes

This is really great! Thanks for remembering the older but still official/supported release. Many times, it gets overlooked by the packaging community.

I also want to try out the new Plasma Login. I don’t see any mention of this specifically (either way; supported or not supported), but does the new display manager work with Xorg?

According to this user, yes but it needs an SELinux workaround:

1 Like

Presumably Plasma Login Manager is not available yet for Atomic desktops that don’t support dnf

I think to make the plasma login manager work well requires more work than a simple update can do safely. F44 I expect to will make the change to login manager.

1 Like

I decided to try out the new Plasma Login Manager and it seems to work well so far. Only noticeable difference was I had to set up Autologin again, and changing settings in System Settings → Login Screen requests your password every single time and doesn’t seem to cache it at all.

Reporting back on plasma login w/Fedora 42 on Xorg w/nvidia-open.

I followed the steps as outlined by @awinterz and @richardm . I did not have to create a new selinux policy e.g. Maybe a bug with Fedora 43 KDE with the new 6.6 and plasma login manager . It worked, but it was way to big of a resolution for me. It wasn’t the same resolution as kwin/desktop.

I couldn’t get plasma login manager to run at the same resolution as kwin/desktop, so I reverted back to SDDM (which does run at the same resolution). I tried the usual (?) way: Apply Plasma Settings… in KDE Settings.

I did notice that one of the settings I have for SDDM has been removed from plasma manager (from /etc/sddm.conf):

[General]
# Enable Qt's automatic high-DPI scaling
EnableHiDPI=true

I am using a Dell U4025QW w/5120x2160 @ 120Hz over DP at 100% (no scaling).

I believe that plasma mananger was running at Ultrawide or Full HD+. I didn’t check but I can if there’s interest in knowing what it did run at. It’s large enough to be annoying.

:person_facepalming:

I get it now. PLM is launching a Wayland session at the Greeter/Login and not XOrg. Oye! That still doesn’t explain why the PLM Greeter/Login is 200%, but it at least explains why SDDM is at the correct resolution and PLM is not: PLM is Wayland and SDDM is XOrg.

The sddm.conf setting has no bearing and I have removed it. The default (EnableHiDPI=false) is Okie Dokie.