According to nvtop, on both my nvidia and AMD computers, kscreenlocker_greet uses 200-400MB of VRAM while the screen is locked -- doesn't that feel excessive for a simple screen locker (I do realize that it's QML and thus in theory can use as much VRAM as say plasmashell).
This is kind of annoying as I was trying to set up a chatbot using my main desktop while it's idle, and would like that extra 400MB back for a higher context length.
Wasn't sure if this was a bug or just how software is nowadays so I opted to start a discussion rather than finishing filing a bug at bugs.kde.org.
Anyway, anyone know of an alternative screenlocker for kwin_wayland?
I thought I would disable kscreenlocker completely (by setting the screen to never lock?) and use something like swayidle and swaylock, but it doesn't look like kwin supports the wayland extensions required to use swaylock.
I also use krunner but unless I've misconfigured it, I wouldn't call it fast (and it freezes a lot since it runs in the background).
Compared to when I used rofi on hyprland (which was really fast). I'm back on KDE cause of the hyprland toxicity debacle, and honesty the only thing that isn't fast, customizable, and reliable is the app runner.
Krunner also has a weird quirk where as it loads entries, it will change the currently selected option so when you hit Enter, it will actually not execute the one you want, but instead run "Install "
Talking out loud I should probably bind alt+space to back to rofi or try Fuzzel or something