Discord on Linux Wayland: Fixing Away Detection (Auto-Idle)
If Discord never switches to Idle on Linux Wayland, you are likely running it on Wayland. This post explains the issue and shows a practical fix by adding Wayland flags to the Discord desktop entry.
If you use Discord on Linux with a Wayland session, you may have noticed a weird behavior: your status never switches to Idle when you walk away from the keyboard.
This is not just a random one-off bug. Multiple users have reported it, especially when Discord is running on Wayland.
In this post, I will show a practical fix that worked for me and others: start Discord with native Wayland flags.
The Problem
Normally, Discord should switch your status from Online to Idle after inactivity.
On Linux Wayland, this often does not happen with the default Discord launch setup. A common reason is that Discord still starts through XWayland unless you explicitly force Wayland mode.
The Fix
Add these startup parameters:
1
--enable-features=UseOzonePlatform --ozone-platform=wayland
A working launch command looks like this:
1
/usr/bin/discord --enable-features=UseOzonePlatform --ozone-platform=wayland
Apply It via a Local .desktop Override
Do not edit system files in /usr/share/applications directly. Create a local override instead.
1) Copy the desktop file to your local applications folder
1
2
mkdir -p ~/.local/share/applications
cp /usr/share/applications/discord.desktop ~/.local/share/applications/
2) Edit the Exec= line
Open:
1
nano ~/.local/share/applications/discord.desktop
Find the line that starts with Exec= and append the flags. Example:
1
Exec=/usr/bin/discord --enable-features=UseOzonePlatform --ozone-platform=wayland %U
3) Restart Discord
Completely close Discord and launch it again from your app menu.
Notes
- This fix is for the native Linux Discord app (for example
.debpackage). - Depending on packaging (Snap/Flatpak), launch behavior can differ.
- If your desktop entry gets overwritten by updates, your local
~/.local/share/applications/discord.desktopoverride usually remains the safer approach.
Why This Helps
Discord is an Electron app. Electron apps can run on Wayland natively, but many still start in XWayland compatibility mode by default unless flags are supplied.
For Discord specifically, users reported that auto-idle works once native Wayland mode is enabled with these flags.
Sources and Research
- Reddit discussion and workaround comment:
- https://old.reddit.com/r/discordapp/comments/1mluhdu/does_discord_not_idle_when_being_run_in_wayland/
- https://old.reddit.com/r/discordapp/comments/1mluhdu/does_discord_not_idle_when_being_run_in_wayland/ntgzd9g/
- Blog post documenting the same behavior and workaround:
- https://avery.is-a.dev/blog/2025-05-20-half-baked-discord-linux-client/
- ArchWiki notes for Discord and Electron/Wayland flags:
- https://wiki.archlinux.org/title/Discord
- https://wiki.archlinux.org/title/Wayland#Electron
- Electron power monitor API reference (context for idle state behavior):
- https://www.electronjs.org/docs/latest/api/power-monitor
If you are affected by this, the two flags above are the first thing I would try.
