Set how long before it times out; either just revealing the backdrop or turning off the display (black).
Preference for me would to have it always visible and go black if I don’t interrupt before times out. Currently I reverted back to SDDM so I get this. It makes sense that the lock screen does this since user intention is likely to walk away. But for login it’s reasonable to expect the user is intending to be present to login.
Yes it has always done that. It’s a relatively new install. Fresh Fedora 44 KDE Plasma 6 install. When it boots I get the login background and nothing happens until I click a key. In which case I get the users, name, password, option buttons and the other stuff at the bottom of the screen. I have clock turned off.
Hmm so it’s an issue. I’m new to Linux so I didn’t realise this. I started out on Fedora 43 KDE using an old computer to get familiar with Linux while I built a new machine for it. Was bad timing if you know what I mean. When I finished the computer I started fresh on it as aforementioned version. I don’t recall what it was like on the old machine. I could probably dig it out from the shed. Pretty sure it’s still setup till I dismantle for parts and dispose of the rest.
For me, both on Fedora and KDE Linux, I get the login prompt straightaway. So I wonder why there is this difference between our systems!
Do you have multiple screens? I could imagine that if you have, say, a laptop with an external monitor connected, the system could start off showing the prompt on the “wrong” screen.
It’s a desktop with a single display. No unusual peripherals that could be confused for a display. Unless there was a setting somewhere that altered this without being obvious. For example; in Screen locking is a checkbox under the “Lock screen automatically” called (the checkbox label) “Lock after waking from sleep”. Perhaps it considers startup waking from sleep. Suppose I should check that…
I’ll need to revert back to Plasma Login Manager and try a few things. Will post a response after looking though other sort of related settings just in case it’s just how I have configured things.
Well when I reinstalled the OS and logged back in with my user the login screen was functioning as expected. But because I had changed over it needed to be setup again and now it’s doing that thing again. I looks as though it is a setting i’m choosing that’s doing it.