Installed on 2 different machines, Can't login

[bearsfan]

I have installed the latest version on 2 different machines and logging in gets no response.  The live versions work on both machines before installing.  Is there a password length or character requirement?

[scholle1]

Welcome to siduction.

Did you set a user and root password during installation?

Is there a password length or character requirement?

No, but  but strongly recommended to set both.

[bearsfan]

Yes, I set a username and password on both machines during the installation, I was wondering if there is a password length requirement maybe?  My keyboard is the english default, the install goes on no problem, boots to the sign in screen but then no response from the keyboard. I tried logging in as Root also but same response.

[bearsfan]

when I say no response from the keyboard, I mean, I can type the letters but pressing enter or clicking on login has no response.

[bearsfan]

Also, I am installing the KDE Plasma version.

[scholle1]

Which ISO did you use?

https://isobuilds.siduction.org/kde/siduction-2024.1.0-Shine_on-kde-amd64-202412261719.iso

[bearsfan]

siduction-2024.1.0-Shine_on-kde-amd64-202412261719.iso

[bearsfan]

I just downloaded the LXQT ISO, I'm going to try that to see if I get the same result.

[bearsfan]

Just installed the LXQT on Vbox and it logged in fine, I'm currently installing on the other machine.

[scholle1]

First try to reset the password (two variants):

• On boot, press the "e" key when grub display the menu.
  Then go to the kernel line. Add at the end " 3", then press "F10" to boot.
  This bring you into the terminal.
  Set the user password again. and type "init 5 && exit" to start the graphical target.
• Use the chroothelper in the live system. Klick on the icon and choose your installation partition.
  Inside chroot set the user password again.

[bearsfan]

Just an FYI, the LXQT installed and logged in no problem.  Maybe something with the KDE ISO?

[scholle1]

Not really. Try it again on one of your machines.
Many new packages have arrived since December 2024, especially Plasma 6.

Please read the manual. Then perform a full upgrade.
Go to the multi-user target with <Strg> + <Alt> + <F3>, login as root and

Code Select Expand

init 3
apt update && apt full-upgrade
More than 1000 packages will probably be updated.

[bearsfan]

Neither one of those options did anything.  Pressing enter or clicking on the login button gets no response, almost like they aren't active.

[scholle1]

If you can log into a terminal with one of the two variants, then try a "apt full-upgrade" as described above.

[ro_sid]

This is a periodically (re-)appearing effect, that to my knowledge is unique to the combination of the "sddm" display manager and KDE/plasma. The effect is, that the enter/return key does not do anything. I, myself, experienced it regularly when upgrading a live (Siduction) KDE-iso image. Sometimes even the window-decorations get lost.

Why am I telling this: Apart from @scholle1's valuable tip to boot into a terminal screen instead of the graphical greeting screen, you can also always do it, even once you are "on sddm". The "ctrl-alt-F?"-mechanism still works, even then!
So press (e.g. ctrl-alt-F3) and you are on a terminal window ("F1" contains the startup messages, "F2" is the sddm-screen"). After logging in from there, you can do anything that does not require "graphics", especially you can update/upgrade.
Usually after some time, when sddm/kde/plasma/qt got their act together, everything works "normal" again!
Such things only happen with rolling releases or sid/unstable (or experimental) versions, not the stable ones and rarely in testing(/trixie). It is the price we have to pay for it, especially during transitions.