Searched for a few weeks and could not find any solid solution. Found a KDE thread that said it was a issue with flatpak but I don’t even have flatpak installed. Others say it’s Wayland, Do non KDE users on wayland get this too?

I know it’s for security but it’s too damned annoying to be worth it! Should I setup a tiling WM and be done with it? It really is that bad.

All I want to do is play Skyrim without seeing this every 15 minutes!

  • Maiq@lemy.lolOP
    link
    fedilink
    arrow-up
    2
    ·
    15 hours ago

    I’m actually using a ps5 controller and have mapped the dpad left and right to use keyboard input for a mod. If I don’t use those buttons for 15 minutes or so I get kicked out of game with this garbage popup, every time! At his point I’m fed up and ready to leave KDE. Been using KDE for 6 years and have seen so many poor design decisions but you could always go into the settings and fix it. This I guess has no fix.

    • LiveLM@lemmy.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      6 hours ago

      Before Wayland was a thing, Steam used a X11 extension to send Mouse and Keyboard presses, which means that for a while, if you used Wayland you couldn’t emulate KB+M with your controller at all.
      A while so long, that someone created a work around. Extest is a “adapter” that simulates the old X11 extension Steam was using and sends the keypresses using its own virtual input device, therefore completely bypassing the pop-ups.
      While that wasn’t its intended function, and it is technically unnecessary now that Steam has added support for the proper ‘Wayland way of doing things’, I can confirm it still works just fine. I use Steam input all the time with no annoying pop-ups.

      It can be a bit annoying to install however. If you’re using Arch, grab it from the AUR. Bazzite ships with it OOTB, I believe.

      • Maiq@lemy.lolOP
        link
        fedilink
        arrow-up
        2
        ·
        2 hours ago

        Interesting Extest sound promising. I’ll have to give it a shot, could be a temporary workaround for the next few years till kde fixes this lol.

    • ScrambledLogic
      link
      fedilink
      English
      arrow-up
      3
      ·
      12 hours ago

      Are you using Steam Input Settings to map those dpad buttons? If so, try setting that back to default, then use AntiMicroX to map keyboard input to your dpad instead.

      • Maiq@lemy.lolOP
        link
        fedilink
        arrow-up
        1
        ·
        2 hours ago

        The problem with that is steam lets you configure per game. I have different keybindings depending on what game I’m playing. Not a bad suggestion to try though, would really help nail down whats partially causing the issue, steam input or the PS5 controller. Although as sp3tr4l pointed out there is probably an issue with how windowManagers are handling wayland security protocol’s, penquin said he is getting this on gnome too.