Description
I cannot get Mailspring to run on Wayland. I have read all the various posts, and have tried launching with:
mailspring --enable-features=UseOzonePlatform --ozone-platform=wayland
Or even with (which should be supported on Electron 33):
mailspring --ozone-platform-hint=auto
I have tried with/without the --enable-features=WaylandWindowDecorations switch.
Whatever I do, Mailspring appears to start normally, and the tray icon appears. However, when I click on Open Inbox from the tray icon menu, nothing happens (no visible window).
Am I missing something???
To Reproduce…
Steps to reproduce the behavior:
- Run Mailspring with any combination of Wayland switches
- Click on
Open Inboxin the tray icon menu
Expected Behavior
Mailspring window should show normally.
Screenshots
N/A
Setup
- OS and Version: Arch Linux with GNOME
- Installation Method: from AUR,
mailspring-binpackage withelectron33-bindependency
- Installation Method: from AUR,
- Mailspring Version: 1.15.1-cb02bf10
Additional Context
Console output when launching from command line:
mailspring --enable-features=UseOzonePlatform --ozone-platform=wayland
[0629/094322.469630:ERROR:file_io_posix.cc(153)] open /home/drakkar/.config/Mailspring/Crashpad/pending/0de483ba-1755-4a66-ae16-ff2fc324e66f.lock: File exists (17)
[0629/094322.469813:ERROR:file_io_posix.cc(153)] open /home/drakkar/.config/Mailspring/Crashpad/pending/6c768e30-5900-41d7-9d06-38346c9285ae.lock: File exists (17)
[0629/094322.469835:ERROR:file_io_posix.cc(153)] open /home/drakkar/.config/Mailspring/Crashpad/pending/6c6ecd53-a079-4f42-9fcd-3a90d20b6e72.lock: File exists (17)
Fontconfig warning: using without calling FcInit()
Running database migrations
App load time: 279ms
{"error":null}
Manual update check (updates.getmailspring.com/check/linux/x64/1.15.1-cb02bf10/anonymous/stable) returned 204