Opening discord through walker causes it to run under xwayland. (IMP: Read description)

Bugs / FRs / Support
, , ,
1
Hyprland version 
Hyprland 0.51.0 built from branch  at commit 46174f78b374b6cea669c48880877a8bdcf7802f  (version: bump to 0.51.0).
Date: Wed Sep 10 12:41:05 2025
Tag: v0.51.0, commits: 6418
built against:
 aquamarine 0.9.4
 hyprlang 0.6.3
 hyprutils 0.8.4
 hyprcursor 0.1.13
 hyprgraphics 0.1.5


no flags were set

before you crash out at me saying this is an issue with walker (the application launcher), it is not. i’ve already discussed with the developer of walker.

I have discord installed through flatpak. opening discord using walker, for some reason causes it to run under xwayland. this does not happen when it’s ran from terminal with flatpak run com.discordapp.Discord and systemd-run --user --scope discord in case of discord from arch repo. this also does not happen when opening discord from another launcher like wofi or fuzzel.
Installing discord from official arch repository also has the same issue. running from any other launcher or terminal works just fine, except for walker.

i have the env = ELECTRON_OZONE_PLATFORM_HINT,auto in my hyprland.conf. i also have my ~/.config/electron-flags.conf as below

--enable-features=UseOzonePlatform
--ozone-platform=wayland

i am not saying that this is a hyprland issue. i am only posting this here to check if someone has faced this and can possibly help me here.

2

Discord will ignore your electron flags because it doesn’t use the Electron that is already installed. Try adding --ozone-platform=wayland to the .desktop file.

1 Like
3

so why does it run normally under wayland when launching from cmdline or any other launcher. why does this happen only with walker? which also just launches the same .desktop file and does nothing extra

4

turns out i walker launches apps with the prefix “systemd-run --user” and since i wasn’t using uwsm, systemd couldn’t inherit variable like WAYLAND_DISPLAY and DISPLAY. using hyprland with UWSM solved this

alternate way to solve this without having to use uwsm (not recommended) would be to add the following lines to your ~/.config/elephant/elepahant.toml

auto_detect_launch_prefix = false