Cannot run on Wayland (1.15.1)

Bug Reports
1

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:

  1. Run Mailspring with any combination of Wayland switches
  2. Click on Open Inbox in 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-bin package with electron33-bin dependency
  • 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
2

I am also curious, I tried similar settings, and it was not working. I already had to hack myself into using kwalletā€¦

I suspect this issue is also related to the fact that Mailspring (its Flatpak version in particular) does not allow shifting the focus on new (browser) window when clicking on any link in KDE

3

Hey folks, good news! Weā€™re about to release an update to Mailspring (1.17.0) which moves it to Electron 39. Electron 39 supports Wayland and actually defaults to it. So I expect that this will not be an issue any more.

1 Like
4

Is there an ETA on this? This is the one thing stopping me from using this otherwise great email client!

5

Still getting the same error on 1.17, i.e. 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).

Checked and Mailspring is running on Wayland, but the problem persists.

Works normally if I start it with mailspring --ozone-platform=x11.

I also get an error regarding libtidy in 1.17:



[0115/000905.948840:ERROR:third_party/crashpad/crashpad/util/file/file_io_posix.cc:153] open /home/drakkar/.config/Mailspring/Crashpad/pending/43f98123-3795-4e7d-a053-ccaabbda310a.lock: File exists (17)
Running database migrations
App load time: 269ms
Error: Could not load libtidy. Tried: libtidy.so.5, libtidy.so.58, libtidy.so.5deb1, libtidy.so.60, libtidy.so.6, libtidy.so. Last error: libtidy.so: cannot open shared object file: No such file or directory
Install libtidy on your system (e.g., ā€˜apt install libtidy-devā€™ or ā€˜dnf install libtidy-develā€™)

{ā€œerrorā€:null}
Manual update check (updates.getmailspring.com/check/linux/x64/1.17.0-5e478521/anonymous/stable) returned 204
(node:45685) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use electron --trace-deprecation ... to show where the warning was created)

Fixed the error by installing the tidy package (on Arch Linux)

6

Same issue here. I opened a separate bug report. Installing Tidy fixed the issues with ā€œError: Could not load libtidyā€œ, but I still have Wayland errors and cannot open it under Wayland.

7

Still not working on Wayland with 1.17.1

8

Same. Well, it works on a machine with intel onboard graphics but not on another one with NVIDIA graphics.

Hereā€™s the output with wayland (X11 also works):slight_smile:

$ mailspring --ozone-platform=wayland
Running database migrations
App load time: 262ms

{"error":null}
[7348:0121/102242.862432:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:273] Unable to set image t
ransfer function.
[7348:0121/102242.862447:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:191] Failed to populate im
age description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
[7348:0121/102242.864050:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:273] Unable to set image t
ransfer function.
[7348:0121/102242.864063:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:191] Failed to populate im
age description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
Manual update check (``updates.getmailspring.com/check/linux/x64/1.17.1-dd5b3e56/3c19f457-d2a3-4bb7-9589-d788c9b3c9b9/
stable) returned 204
[7348:0121/102243.358693:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:273] Unable to set image t
ransfer function.
[7348:0121/102243.358710:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:191] Failed to populate im
age description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
(node:7348) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.

1 Like