System details
Omarchy HEAD (Oct 3 2025)
What's wrong?
Slack's Electron-based desktop application supports native Wayland rendering, but requires specific command-line flags to enable it. Without these flags, Slack runs through XWayland, which can cause blurry text on HiDPI displays and miss out on native Wayland benefits.
Proposed Change
We might want Omarchy to add Wayland support flags to the Slack desktop entry configuration by modifying the Exec line to include:
--enable-features=WaylandWindowDecorations - Enables native Wayland window decorations
--ozone-platform-hint=auto - Automatically selects Wayland when available, falls back to X11
Example Configuration
Create/modify ~/.local/share/applications/slack.desktop:
[Desktop Entry]
Name=Slack
StartupWMClass=Slack
Comment=Slack Desktop
GenericName=Slack Client for Linux
Exec=/usr/bin/slack --enable-features=WaylandWindowDecorations --ozone-platform-hint=auto --gtk-version=3 -s %U
Icon=slack
Type=Application
StartupNotify=true
Categories=GNOME;GTK;Network;InstantMessaging;
MimeType=x-scheme-handler/slack;
Benefits
- Native Wayland rendering (no XWayland translation layer)
- Crisp text rendering on HiDPI displays
- Better performance and lower latency
- Proper Wayland window management
System details
Omarchy HEAD (Oct 3 2025)
What's wrong?
Slack's Electron-based desktop application supports native Wayland rendering, but requires specific command-line flags to enable it. Without these flags, Slack runs through XWayland, which can cause blurry text on HiDPI displays and miss out on native Wayland benefits.
Proposed Change
We might want Omarchy to add Wayland support flags to the Slack desktop entry configuration by modifying the
Execline to include:--enable-features=WaylandWindowDecorations- Enables native Wayland window decorations--ozone-platform-hint=auto- Automatically selects Wayland when available, falls back to X11Example Configuration
Create/modify
~/.local/share/applications/slack.desktop: