Will SDDM be continue to get support and new features? Or will it be dropped and KDE users asked to switch to plasma-login-manager?
Dont like the dependency plasma-login-manager has with systemd. It is going against basic Unix ethos to have independent apps/libraries and no hard-coded dependencies.
The reason for the fork was a lack of attention/support/development of sddm.
It may die or it may live.
plasma-meta has a hard dependency on plasma-login-manager.
@albersc2 did you install the package plasma-meta explicitly, i.e. on your own or was it installed as part of EOS installation?
I wonder if plasma-login-manager supports both X11 and Wayland or is it only Wayland?
Though it is not good for KDE team to introduce a dependency on systemd
I tried plasma login manager and it totally effed my computer, I put sddm back and itās all working again! 
Thatās weird. You followed the same steps given by @shadow359 ?
Works like a charm on my system.
Yeah. I had transparent windows with no blur so I couldnāt see anything, the monitors were re-arranged and better-blur-dx wasnāt even showing in the desktop effects. As I say, restoring sddm sorted it all out.
Yes, it was on my own. Iām sorry for the confusion.
If possible, can you please share the reasoning behind it? Not saying that it should not be done nor putting shade or challenging the decision to explicit install plasma-meta.
I am going to hold off on installation of plasma-login-managet or updating EOS for at least one more week. Wanna to see how it pans out.
If I remember correctly, I think it was a few months ago when there was a Plasma update and my printer stopped being recognised correctly in the KDE system settings, and it was doing some very strange things. I spent a few days testing it, without success. In the end, I had to add the printer via cups, http://localhost:631/. But thatās another story 
.
So unless EOS users have plasma-meta package installed, explicitly, they will not be offered plasma-login-manager.
Offcourse users can explicitly go and install plasma-login-manager without installing plasma-meta package.
Maybe EOS dev team should put this in the EOS news section in the GitHub.
As you may or may not be aware, Cachy switched to plasma-login-manager as the default login manager with the most recent ISO. Obviously as in the Arch way, existing configuration wasnāt changed.
But, many of us (I think) manually changed and there have really been no issues, it is after all a fork of the SDDM code, with some further changes since. Just like anything, it may or may not break at any point in development.
I just did pacman -Syu its all working. Thanks for the update info.
Are you using plasma-login-manager or sddm?
Found this:
I also had some issues, as the plasma-login-manager defaulted to an x11 session which my system somehow did not like and I forgot to check with the first login. Changed that after a restart, now it works well.
Donāt sweat about plasma-login-manager or sddm. If you update you will still use sddm since manual intervention is necessary. Switch whenever you feel comfortable.
If themes or extensions are used that mess around in the plasma internals like better-blur stick with sddm for now, since thereās a chance they are not updated and tested.
Ah. Maybe that was it, I didnāt think to check.