Feature to block specific processes from showing discord RPC

Comments

5 comments

  • Blastyr

    Actually Lutris doesn't do Discord presence by default; you literally have to manually install a separate package to even enable support for it. I opened an issue on their GitHub last week for exactly this, and it was closed with a note saying it's Discord detecting a process running out of /usr/games/ and automatically updating the presence.

    Which makes it DEFINITELY Discord's responsibility to fix this.

    Could the Lutris package maintainer move the executable to /usr/bin/ and mitigate what Discord is doing wrong? Probably, but the correct solution is that Discord shouldn't just assume something is a game based on where its executable is located.

    Steam could just as easily have been packaged to be run from /usr/games/ and I'd bet this wouldn't be an issue because (1) Steam's install base is much larger, meaning more users would be annoyed by the behavior, and/or (2) someone at Valve would have raised a stink.

    1
  • Shigutso

    I'm having the same issue with Lutris.

    I believe this issue could be fixed if Discord had an option to blacklist "auto detected" games, the same way we can whitelist games not detected automatically.

    1
  • Reesz

    Having the same issue with lowkey.gg and other tools running in the background.

    Would really help out to be able to specifiy which RPC I want to show.

    0
  • Shigutso

    Quick solution for Linux and Lutris:

    cd /usr/bin
    sudo ln -s /usr/games/lutris

    Reboot your system (not really necessary but just to make things easier to understand)

    Done, Lutris will not show in Discord game activity anymore.

    0
  • Blastyr

    That's essentially what I've done to mitigate the problem, although a more "proper" place for that symlink is in /usr/local/bin/ rather than /usr/bin/.

    It's also a mitigation specific to Lutris, not a solution to the problem, which is that Discord will sometimes assume a program is a game based on the location of its executable.

    You're also correct that there is no reason to reboot. Get that "reboot to apply changes" Windows mentality out of here.

    0

Please sign in to leave a comment.