I updated some software components once more on my Linux system today.
Unfortunately, I was surprised by the following information on my subsequent login retry for another graphical desktop session.
Which component variants?
What does “long version translation” mean?
How does graphics chip relate to particular Plasma components? Which GPU(s) do you have?
Likely I have more experience with zypper locks than anyone else here. Of my 20 or more TW installations that include Plasma, on only 3 have I allowed migration to version 6. My TW locks file is the same on each of those installations, currently @8,937 bytes. On none is SDDM installed. Given presence of sddm among your error messages, I suggest you give a different DM a try. Most of mine use either KDM3 or TDM, neither of which are in standard repos. 1 or 2 use LightDM. If switching DM doesn’t work, or even if it does, it may be that you can login on a vtty, then start a session using XDG_SESSION_TYPE=XXX dbus-run-session startplasma-XXX, where XXX would be wayland or x11.
Transition (for example):
KDE 3, 4, 5, 6 (Plasma) …
Such feedback sounds promising.
I can eventually try other display managers out to check if they provide a working login interface also on my system.
It depends on the aspect if corresponding parameters can be selected in a “convenient” way.
Do what Mrmazda said, try another display manager. This is just speculation, not advice, but I wonder is holding sddm back could have prevented your issues.
As already pointed out in the bugreport. There is nothing to improve regarding dependencies. They_are_working. You decided to break the dependencies by applying locks to packages without the appropriate knowledge of the consequences. As can easily be seen at your zypper ll list, you decided to lock random Plasma 5 packages. This lead to an inconsistent Plasma 5/6.0/6.1/6.2 system. So you shot yourself in the knee and try to blame the devs for it.
There is nothing what devs can do when some users decide to willingly break their system.
You were not even able to explain why you believe the locks for Plasma 5 are necessary. Instead of „answering“ questions from devs with unrelated counter questions, you could have easily checked within 5 minutes, that for all of your locked Plasma 5 packages the equivalent v6 packages are available since ages.
long version transition
It seems that some contributors have got understanding difficulties with the reasons for temporarily locked packages.
It seems that the selection of corresponding graphical user interface alternatives is working (as expected) also by 