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.

  • m4m4m4m4@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    3 days ago

    I’d be surprised if there was any alternative, to be honest.

    I’d file the bug - your case is not common. I run kscreenlocker just fine and it’s not such a ram hog here.

    • kelvieOP
      link
      fedilink
      arrow-up
      4
      ·
      3 days ago

      VRAM or regular RAM? It doesn’t use that much regular RAM.

  • ExtremeDullard@lemmy.sdf.org
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    3 days ago

    I use the Cinnamon screen saver with i3wm. It’s just a Python script, it’s reasonably light in resources, it looks smart enough and it comes with a nice command to remote-control it if you need to start the screen saver, lock or unlock it programmatically.

    I’m not sure it works in Wayland though. I only use Xorg. I suppose it should since Cinnamon works in Wayland too now.

    • kelvieOP
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      3 days ago

      I’m specifically looking for something that works with kwin_wayland, this being the KDE instance and all.

      • ExtremeDullard@lemmy.sdf.org
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        3 days ago

        The reason why I posted this is because there’s nothing that prevents you from using any old screensaver / screenlocker out there in KDE. As I said, I use the Cinnamon screen saver in i3, which is not the Cinnamon environment.

        That’s the beauty of Linux: you can mix and match things to your heart’s content.

        • kelvieOP
          link
          fedilink
          arrow-up
          1
          ·
          edit-2
          3 days ago

          I actually did already mention, in Wayland you need to coordinate screen locking with the compositor (kwin), otherwise I’d be using swaylock.

          • ExtremeDullard@lemmy.sdf.org
            link
            fedilink
            arrow-up
            1
            arrow-down
            1
            ·
            edit-2
            3 days ago

            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.