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 actually did already mention, in Wayland you need to coordinate screen locking with the compositor (kwin), otherwise I’d be using swaylock.
Ah okay, I didn’t know that. I personally try to stay away from Wayland as long as possible so support for it gets better before I have to jump in. I’m not an early adopter for that sort of thing - even though Wayland is 16 years old at this point, but amazingly it’s still too green for my taste.