3 ms·
Not using Arch anymore, but I did have this issue recently on OpenSUSE Tumbleweed. I switched KDE to Wayland (defaulted to X11 for some reason) and the issue we
by gh02t 2y ago
Not using Arch anymore, but I did have this issue recently on OpenSUSE Tumbleweed. I switched KDE to Wayland (defaulted to X11 for some reason) and the issue went away. Worth a try if you haven't already.
- bigstrat2003 2y agoThank you for the tip! Unfortunately I can't use Wayland because it breaks the AFK detection in Discord. I would actually prefer to use Wayland, but Discord Linux support is real bad. That said I'll have to take a look because maybe there's a solution that didn't exist last time I tried. And worst case scenario, I can at least decide which bug is less bad.
- MrDrMcCoy 2y agoWhile I can't personally understand why you'd want to give Discord and its advertisers free information about your application usage habits, issues like these are endemic to rather a large number of Electron apps whose developers refuse to keep the framework up-to-date. Supposedly the issues will go away when they upgrade to modern Electron, and then I'll know for sure just how good the Flatpak jails are at blocking that nonsense.
- gh02t 2y agoAn off the wall solution might be to bridge Discord to Matrix with https://docs.mau.fi/bridges/go/discord/index.html https://docs.mau.fi/bridges/go/discord/index.html and then use a Matrix client, but no idea how well the bridge supports AFK detection as I haven't used the Discord one. Generally the other bridges to Matrix I have used support status and presence pretty seamlessly, though. Don't think any of the bridges support voice chat, however, so depends on what you use Discord for. Also perhaps try Discord in the browser instead of the desktop app? Just some random thoughts to try.