compass icon indicating copy to clipboard operation
compass copied to clipboard

How to run Compass under native Wayland?

Open sepehr opened this issue 2 years ago • 7 comments

Since Electron 12.x, there is support for native Wayland through the use of these feature flags:

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

or using --ozone-platform-hint=auto. This is the way to avoid a badly-stretched blurry, and hardly-usable UI on HiDPI displays. HiDPI Wayland users usually run VSCode, Chromium itself, and other popular Electron apps like so.

Passing those arguments to Compass on a Fedora 37, Gnome 4.32 desktop using:

flatpak run com.mongodb.Compass --enable-features=UseOzonePlatform --ozone-platform=wayland

Compass crashes with:

[3:0105/181354.163494:ERROR:wayland_connection.cc(180)] Failed to connect to Wayland display
[3:0105/181354.163517:FATAL:ozone_platform_wayland.cc(211)] Failed to initialize Wayland platform
/app/bin/run.sh: line 2:     3 Trace/breakpoint trap   (core dumped) zypak-wrapper '/app/main/MongoDB Compass' "$@"

I wonder how we could safely pass native wayland feature flags down to Electron and Chromium? It's definitely not a pleasure to use Compass in XWayland. Passing --ignore-additional-command-line-flags did not help.


blurry compass under XWayland

sepehr avatar Jan 05 '23 17:01 sepehr