I get no output at all (and therefore I cannot figure out what is wrong), mailspring just does not start anymore.
$ snap run mailspring
$ echo $?
1
Hmm that's odd - we do the snap testing on Ubuntu 18 so it should work... can you try running with ELECTRON_ENABLE_LOGGING=true mailspring and see if that prints anything useful?
Hello, after uninstalling Mailspring, removing the local files, rebooting and reinstalling it worked again.
I am still not sure what was wrong before, too bad I didn't know how to enable logging.
Here is the output with logging enabled:
$ ELECTRON_ENABLE_LOGGING=true mailspring
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
[26495:1114/142623.796085:ERROR:gconf_listener.cc(116)] Error with gconf key '/apps/metacity/general': Configuration server couldn't be contacted: D-BUS error: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.83" (uid=1001 pid=26495 comm="/snap/mailspring/277/usr/share/mailspring/mailspri" label="snap.mailspring.mailspring (enforce)") interface="org.gnome.GConf.Server" member="GetDefaultDatabase" error name="(unset)" requested_reply="0" destination="org.gnome.GConf" (uid=1001 pid=26616 comm="/usr/lib/x86_64-linux-gnu/gconf/gconfd-2 " label="unconfined")
[26639:1114/142624.578882:ERROR:gl_implementation.cc(245)] Failed to load libGL.so.1: libGL.so.1: cannot open shared object file: No such file or directory
[26639:1114/142624.630828:ERROR:gpu_child_thread.cc(252)] Exiting GPU process due to errors during initialization
Running database migrations
App load time: 1208ms
[26495:1114/142624.774663:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process.
{"error":null}
[26495:1114/142627.225667:INFO:CONSOLE(16)] "Window load time: 1146ms", source: file:///snap/mailspring/277/usr/share/mailspring/resources/app.asar/static/index.js (16)
[26495:1114/142627.226936:INFO:CONSOLE(16)] "Window load time: 1147ms", source: file:///snap/mailspring/277/usr/share/mailspring/resources/app.asar/static/index.js (16)
Thanks for the support :)
Looks like you could close this for now and reopen if it comes up again...
I'm having the same symptoms. Running the snap with debug:
$ ELECTRON_ENABLE_LOGGING=true mailspring
[12089:1118/225548.673881:WARNING:browser_main_loop.cc(275)] Gtk: cannot open display: :0
This happens on both Wayland and X11. Like @tyrion, I've removed the snap and rm -rf ~/snap/mailspring, then restarted, but that did not change the behaviour.
I'm running this on a laptop with Nvidia Optimus. After I've switched to Nvidia GPU with prime-select nvidia, Mailspring starts up. After switching back with prime-select intel I still get the same error.
Non-snap installation does not have this problem.
Same issue here on Arch Linux. Getting the same error as above on the snap package, but the deb-package is working just fine.
For me it does not work in the Wayland session, it did work in the X11 session
❯ ELECTRON_ENABLE_LOGGING=true mailspring
[5559:1128/154618.153851:WARNING:browser_main_loop.cc(275)] Gtk: cannot open display: :0
The deb package does work
Same problem, mailspring snap cannot work with wayland, but works fine when installed from deb. Looks like the snap package needs to be updated with wayland support.
Same issue. Mailspring doesn't start when installed from snap on Ubuntu 18.04.01 LTS. Neither launching from desktop icon nor from terminal works. I'm using Nvidia graphics card. Please let me know if you need more info about configuration.
Below is output when launching with logging enabled:
$ ELECTRON_ENABLE_LOGGING=true mailspring
[22202:0105/144958.741954:WARNING:browser_main_loop.cc(269)] Gtk: cannot open display: :0
Same issue for me. I tried snapd beta version for kicks.
ELECTRON_ENABLE_LOGGING=true mailspring
2580:0108/182950.504018:WARNING:browser_main_loop.cc(269)] Gtk: cannot open display: :0
> snap list mailspring
Name Version Rev Tracking Publisher Notes
mailspring 1.5.5 309 stable foundry376✓ -
> snap list core
Name Version Rev Tracking Publisher Notes
core 16-2.36.3 6130 beta canonical✓ core
Given that the original poster's issue is solved, but this has some helpful information about issues running the snap version of Mailspring on Wayland, should we change the bug title to be:
"Cannot run Mailspring snap version with Wayland"?
No, same issue here regardless of wayland or X11.
I get the very same on Fedora 29.
Any updates on this?
Same on Ubuntu 18.04. Similar to @asdzxcasd I am running on an Nvidia graphics card with Gnome X11. Getting the following when running with logging:
Running database migrations
App load time: 124ms
{"error":null}
[11026:0323/131030.480972:INFO:CONSOLE(16)] "Window load time: 516ms", source: file:///snap/mailspring/338/usr/share/mailspring/resources/app.asar/static/index.js (16)
[11026:0323/131030.481013:INFO:CONSOLE(16)] "Window load time: 525ms", source: file:///snap/mailspring/338/usr/share/mailspring/resources/app.asar/static/index.js (16)
^C[11156:0323/131119.632618:WARNING:x11_util.cc(1391)] X error received: serial 449, error_code 3 (BadWindow), request_code 4, minor_code 0 (Unknown)
Joining the club on Ubuntu/Pop_OS! 19.04 with mailspring (1.6.1-aceed8e5) installed from the amd64 deb package:
$ ELECTRON_ENABLE_LOGGING=true mailspring
Running database migrations
App load time: 179ms
{"error":null}
[26455:0421/230518.783277:INFO:CONSOLE(16)] "Window load time: 369ms", source: file:///usr/share/mailspring/resources/app.asar/static/index.js (16)
[26455:0421/230518.792031:INFO:CONSOLE(16)] "Window load time: 377ms", source: file:///usr/share/mailspring/resources/app.asar/static/index.js (16)
Manual update check (updates.getmailspring.com/check/linux/x64/1.6.1-aceed8e5/anonymous/stable) returned 204
^C%
I also have NVIDIA GPU on Gnome X11.
I tried to unpack the app.asar to add some logging, but unfortunately couldn't find where the {"error":null} line would've been written. :/
Just to clarify - my problem is that Mailspring launches, but no window is opened. The Mailspring icon shows up on the dock, but that's the extent of visible graphical elements I'm getting.
I checked and the issue seems present on all versions after and including 1.5.4. Maybe the Electron 4 update is to blame?
On 1.5.3 that shipped with Electron 2.x I still get the {"error":null} output, but all the windows seem to be open and the software functions normally.
Same here on Ubuntu 19.04 on Wayland. Deb installation works, Snap doesn't - at launch no window is opened, it just does nothing.
Same problem, Ubuntu 19.04 Wayland. Will try installing the deb package.
I do have the same problem. In Wayland not a window open. And in Xorg, only the greeting window, but wont let me go further. Im working in Fedora 30. Thanks for the support!
Same issue on Fedora 30
ELECTRON_ENABLE_LOGGING=true mailspring
[9017:0522/111746.622988:WARNING:browser_main_loop.cc(269)] Gtk: cannot open display: :0
Most helpful comment
For me it does not work in the Wayland session, it did work in the X11 session
The deb package does work