Created attachment 706092 [details] emerge info with package settings ==== The issue ==== $ google-chrome-stable [2969:2969:0505/061605.403992:ERROR:browser_main_loop.cc(1386)] Unable to open X display. There is known a workaround -> $ google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland <- worth mentioning, but shouldn't be as simple as typing "google-chrome-..." out of the box? In this case is it an real issue that should be fixed, or wont-fix (cos foobar can do an alias)?
aliases don't work with application launchers (dmenu, bemenu) which functionality depends on pkg-config
At this point wayland support is still unstable in chrome, so it's not a bug :)
We just install the desktop file provided by upstream. If you want to change it, you can copy the desktop file (e.g. /usr/share/applications/google-chrome.desktop) to ~/.local/share/applications or /usr/local/share/applications and add your flags to it.