Do you have the keyboard enabled in System Settings?
it is working for me when I touch the screen on my system. But not if I use my mouse. Once I have clicked something with that that, I have to use my keyboard.
Yes, also i don’t have a touch screen but as i said earlier:
At least on my last system it worked without touch screen, i could use the mouse to open the virtual keyboard and type my password to unlock the screen!
I think it could actually come from Wayland, because my last install was on X11 cause Wayland was way to buggy back then (KDE 5)… I’ll test the locked screen in X11 and comeback here!
So report this, the one I linked to may be the appropriate one, though. Using the on screen keyboard on a non-touch device may not see that much user usage, and this might not be noticed by devs.
Ok so, update on this, this has definitely fixed a lot of issues, I still had 1 or 2 crashes for some specific cases but now I have much less crashes for sure, so great news, thanks again for the help! @skyfishgoo
Sorry to hear about all your issues, @NitramO_Off, I have noticed that with Chromium-based browsers, like Brave, there’s some default settings that need to be applied otherwise the browser tends to bloat and even stay running when you think it’s closed.
Go into Brave’s menu → Settings → System category → and turn OFF the “Continue running background apps when Brave is closed”.
That one setting has caused computers to run hot and run out of memory and eat into swap space.
Then scroll down a bit and in the Performance section, under Memory Saver, consider enabling it and making sure it’s set to Balanced.
It’s not clear but you need to right-click on the ⌄ in the system tray, then in the pop-up menu, choose Configure System Tray… → Entries tab → scroll down and find Notifications and change it from “Shown when relevant” to “Always shown”
I’m experiencing this too on a dual GPU laptop and I’m not sure what is causing it either, or where to report it. Is it at the Plasma level? The Ubuntu 24.04 level?