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!

  • sp3ctr4l@lemmy.zipEnglish
    6·
    4 minutes ago

    Ok so I’ve run into this bug frequently with my Steam Deck for the past 2 years.

    The following is my possibly innacurate, but genuine attempt to best describe whats going:

    https://bugs.kde.org/show_bug.cgi?id=490666

    Its a KDE bug that is specific to how KDE handles GTK (2 and 3?) in Wayland.

    It is not a bug with Wayland. It is not a bug with GTK.

    GNOME doesn’t seem to have this problem.

    Its existed for about 3 years, the thread I linked above shows some of the explanation of how/why its occuring… even though this particular bug report is only a few months old, you can find it recurring further back in the past.

    Here’s some more bug threads:

    https://bugs.kde.org/show_bug.cgi?id=480412

    https://forums.opensuse.org/t/remote-control-requested-every-time-i-use-kde-connect-remote-control/175083

    https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/issues/6

    Basically, in an attempt to make remote access/control permissions for GTK to work properly in KDE Wayland, KDE implemented what multiple KDE developers have themselves described as a ‘hack’, a temporary, quick fix solution, in various comments on forums.

    EDIT// Here’s an example of a KDE dev outright stating this, from the first thread:

    Just to clarify that, we have two paths. One uses xtest one does not.

    The xtest path is more of a hack, at the time for just GTK3. If anyone can test commenting out:

    plasma-workspace/xembedsniproxy/sniproxy.cpp

        if (windowAttributes && !(windowAttributes->all_event_masks & XCB_EVENT_MASK_BUTTON_PRESS)) {
        m_injectMode = XTest;
    }

    and see if clicking their app still works that would be useful. We can try and make the xtest path less used.

    The rest of that thread is another KDE dev pushing hotfixes, interspersed with others saying that the problem persists.

    //

    Unsuprisingly, having a quick fix hack as an underlying, integral part of an entire DE, is not a good idea, as it doesn’t actually solve the problem except in very specific situations, and causes mass confusion downstream.

    The problem has persisted for years because… as far as I can tell, to fix it properly would require a significant rewrite of KDE’s entire permission model, and also as far as i can tell, this has yet to be done.

    The problem originally was pretty rare and thus I guess low priority, but as more and more people are trying to use KDE Wayland and a console controller or Steam Deck or gamescope or something like that, you can find more and more people complaining about it.

    The devs seem to keep thinking they’ve fixed it, over 2024, only to find… no, they have not.

    There is no functional ‘fix’, outside of switching back to X11, not until KDE gets its shit together.

    For me on a Steam Deck, wanting to be able to use it as a gaming device and a PC, I switched over to the GNOME flavor of Bazzite, all problems solved.