I just disabled the password prompt when waking from hibernation—obviously, that solved the problem, haha.
So I’d really like to know why a password is being entered that seems incorrect, since I haven’t configured anything like that! Just to remind you, none of this happened in Plasma 6.6.X, and—most importantly—keep in mind that the problem occurs on different hardware and on a clean install on both devices.
Can you explain in more detail exactly what is happening and when? And is that before or after you disabled the password prompt?
Additionally some extra information (output of kinfo as a minimum, but inxi -zv8 would be ideal) for both devices would be handy.
are you using SDDM or the new plasma login screen?
when you say “extended sleep mode” do you mean hibernation (S4 state)?
I explain very clearly what happens, when, and how. I frequently put my two Dell laptops into sleep mode, and it’s when I wake them up that I see “Unlock failed”—even though I didn’t even enter a password. I’ve also mentioned several times that I never had this bug with Plasma 6.6.X and 6.5.X, kernel 6.13 and earlier. Since version 6.7.0 and later, I’ve been experiencing this bug—even after a clean install on both devices. How do you explain this bug appearing with KDE Neon Plasma 6.7.X and not before?
It’s as if, for the past hour, I’ve discovered that the latest Flatpak version of Tor Browser no longer works since upgrading to Plasma 6.7.5 yesterday 
on both devices at the same time—how strange is all this? I uninstalled and reinstalled the Flatpak version of Tor Browser, but it no longer appears and I can’t see it in the apps or processes. So I uninstalled and reinstalled the Ubuntu Noble version of Tor Browser—all through Discover—and now Tor Browser works. It’s an older version than the Flatpak one, but I don’t care about that!
I’ve noticed that things are changing at KDE, and we’re very happy about it, but it’s acting up quite a bit—and I’m just a basic user, though I have a lot of experience with computers.
I hope you’re not going to ask me where the “sleep” option is 
Here are the results from `kinfo`; let’s see if I can get anything with the other command:
Operating System: KDE neon User Edition
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.1
Kernel Version: 7.0.0-31-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i7-1185G7
I can tell you, however, that I don’t experience this “unlock failure” bug when the PC wakes from screen sleep on either of these two laptops; it only happens when using the physical power button or the Linux menu and the sleep button. That’s when the bug occurs if the screen lock settings are configured to lock the screen after waking from sleep—this bug is completely messed up.
For Tor Browser, I mean Flathub from Discover, not Flatpak
Does anyone know how to explain this bug and why the Flathub version of Tor Browser has stopped working since Plasma 6.7.5? Are there other users experiencing these issues?
OK, now I know what you’re talking about because it also occurs on my system (also a Dell - not sure if that matters). But it started after upgrading to Plasma 6.7.4. On my system it doesn’t occur every time but I haven’t bothered looking for a fix because it only takes 2 seconds for the input to reset so I can enter a password. In my case, I wake the system by pressing the power button which is also a fingerprint reader, although the drivers don’t exist for my system so it is disabled. The kernel driver is loaded however, so perhaps it is picking up some input from that???
Operating System: Manjaro Linux
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.2.4-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8705G CPU @ 3.10GHz
Memory: 16 GiB of RAM (15.5 GiB usable)
Graphics Processor 1: Intel® HD Graphics 630
Graphics Processor 2: AMD Radeon RX Vega M GL Graphics
How do you wake them? Keyboard press, power button press???
Where have you mentioned this? Can you link to your other posts so we don’t need to go over the same troubleshooting?
I’m sure you can appreciate the ever widening amount of hardware linux and KDE Neon run on and need to cater for. It is inevitable that fixing one problem may occasionally break something else, but with people reporting these issues they can hopefully be resolved quickly.
This would be a unrelated separate issue, and a separate thread should be created for it. This ensures troubleshooting steps are clear and not mixed up, but perhaps more importantly leaves a clear record of how each issue was troubleshooted and what the solution is for anyone else looking for a solution to the same or similar problem. This is how issues are resolved quickly when they inevitably do occur.
Also when posting to the forum, if you think of another question or want to add more information and you are already the last person to reply, please edit your last post and add the information there rather than making multiple replies consecutively.
For clarification the issue is in KDE lock-screen. When waking the device from sleep the KDE lock-screen is displayed already with “Login Failed” as though an incorrect password was entered. It appears as though KDE lock-screen is picking up some input from the power button press to wake the system. This started occurring after KDE Plasma 6.7.4 update.
It may be related to this bug although its presentation is slightly different: https://bugs.kde.org/show_bug.cgi?id=481808
At last an exact description of what is happening. The same here except I wake the system up by pressing any keyboard key. Dell Optiplex 3090 here. I’m just ignoring it.
Wrong—the problem has been present since Neon Plasma 6.7.0 and not before; that’s an important point to clarify, and does it persist with the latest updates? Wrong—it’s not the power button, which also serves as a fingerprint reader, that’s causing this problem. In fact, on my computer, that reader isn’t recognized or configured, but it’s not an issue for Windows—still a mystery for Linux in 2026. Wrong, because as I already pointed out, the bug occurs simply by selecting “Sleep” from the KDE menu or using Ctrl-Alt-Delete.
I’ll check out your link to see what it’s about and let you know.
It’s not a big deal, and it certainly doesn’t cause any major issues—it’s just that this bug wasn’t present in versions of Neon Plasma prior to 6.7.X, and it’s worth figuring out why and fixing it
Well it’s likely fixed in KDE 6.8. As per bug link I sent previously.