Well, you might’ve entered the password incorrectly a few times, and then faiilock faillocked the account. Can be fixed by going to another tty (e.g. Ctrl+alt+f3), logging in as root and faillock --reset --user your_username_here. If that doesn’t help, that’s probably neon’s issue (mb they messed up pam stuff or something).
On a side note, KDE neon is not exactly stable for daily driving, I’d suggest switching to another distro that’s not meant for testing recent KDE stuff
Kinda follows from the description on their website:
You should use KDE neon if you are an adventurous KDE enthusiast who wants the latest and greatest from the KDE community as soon as it’s available, with no delays, opinionated patches, or UX changes.
Although, yap, I may’ve put it a bit too harshly, and the same may be applicable to using KDE on many rolling release distros.
To be fair, the only problem I had while using it (except for the usual need to add a ppa to install literally anything) was exactly the same I encountered on arch: sddm just died after some updates and refused to start. What made it worse, however, was that they decided it was a great idea to configure the same keyboard layouts both for the graphical session and tty, so I couldn’tc even login to fix it :/
Yeah i woyld have entered right the second time. Numlock was off and it is a simple pass. The best i can tell is kde issued a buggy update to their de. Thats why the logon screen looked different and why issueing an update comand fixed it but reset my desktop settings.
I keep getting shocked with Arch lately. Software is getting better fast with AI to boost productivity. Blender runs at light speed on a laptop with an i7-6700hq, 16GB DDR4 and a GTX 970. Even Wayland works super well!
lemmy.world
Top