Mailspring doesn't quit gracefully on Gnome logout

Bug Reports
, , ,
#1

Description

If mailspring is open and I log out of Gnome, instead of closing normally like all other apps, it crashes instead of quitting.

To Reproduce…

Steps to reproduce the behavior:

  1. Have mailspring open
  2. Click on menu bar → power menu → log out
  3. Mailspring will freeze and the system will issue an error message that it can’t quit the app (the famous ‘Close’ of ‘Wait for app’ message. If I don’t click ‘Close’ soon enough, the system becomes increasingly unresponsive and the only way to get out of it is to press ctrl + alt + F1/F2 etc. (in which case gdm pops up) and restart from there (logging back doesn’t solve the issue).

Expected Behavior

Mailspring quits and the system logs out.

Screenshots

(sorry for the poor quality of the video, I’m in a dark room and screen recorders are no use because they stop recording the moment I click on log out).

Setup

  • OS and Version: Ubuntu 20.04
  • Mailspring Version: 1.7.6-e94bb759

More system specs:
OS: Ubuntu 20.04 LTS x86_64
Host: X570 AORUS PRO -CF
Kernel: 5.4.0-26-generic
Packages: 1824 (dpkg), 5 (flatpak), 9 (snap)
Shell: bash 5.0.16
Resolution: 3440x1440
DE: GNOME
WM: Mutter
WM Theme: Adwaita
Theme: Ant-master [GTK2/3]
Icons: Flat-Remix-Blue-Light [GTK2/3]
Terminal: gnome-terminal
CPU: AMD Ryzen 5 3600 (12) @ 3.600GHz
GPU: AMD ATI Radeon 5700 XT
Memory: 2837MiB / 32126MiB

Additional Context

Mailspring is the only app that does this. Tested both snap and .deb versions, same problem.

(Originally posted by gitbobbed on GitHub.)

Quitting mailspring doesn't end all processes
#2

Same issue here. It only happens when logging out. It doesn’t happen when shutting down directly.

  • OS: Ubuntu 20.4.1 LTS
  • Mailspring version: 1.7.8-13635bcf (snap)

(Originally posted by GGimenez96 on GitHub.)

#3

Havig same configuration, confirming issue.

(Originally posted by senorLobito on GitHub.)

#4

As of feb. 2021 this issue still exists.

OS: Ubuntu 20.04
Mailspring: v1.8.0-8983dca2

(Originally posted by ualich on GitHub.)

#5

I’m on Ubuntu 20.04 too with Mailspring version 1.8.0 having the exact same issue.

(Originally posted by arg1998 on GitHub.)

#6

Thank you for migrating the issue =).

I’ve since moved to Arch, but was no longer using Mailspring.
Will reinstall tonight and try again to see if this bug also happens in it.

Best,

Daniel

1 Like
#7

Welcome! A couple of things you’ll find relevant:

#8

@gitbobbed Are you able to provide some logs about this issue? This does not happen on my machine:

  • Ubuntu 20.10
  • Mailspring 1.8.0
#9

I am having same issue. ubuntu 20.04.2 Gnome
have this issue with log out, shutdown and restart.
I manually quit mailspring before shutting down my system in order to avoid this issue.

1 Like
#10

Can confirm this issue - I’m running Pop!_OS 20.04LTS and mailspring is causing the system an annoyingly long time to log out, restart or shutdown. My current workaround is to manually close the mailspring app before shutting down my PC, which obviously is not an ideal solution… If we can get some attention on this one that’d be very much appreciated!

#11

Description

On Linux, when quitting mailspring, then checking in the process manager, processes called main are not closed, the ones started with the following command line /usr/share/mailspring/resources/app.asar.unpacked/mailsync.bin--modesync--info mail@provider.xyz

Restarting Mailspring creates new such processes and the old ones stay there, apparently indefinitely.

To Reproduce…

Steps to reproduce the behavior:

  1. Open Mailspring
  2. Quit Mailspring.
  3. Check for alive processes ones still associated with mailspring

Expected Behavior

After quitting mailspring, no process should be left open.

Setup

  • OS and Version: Archlinux and Ubuntu 20.10
    • Installation Method: AUR on archlinux (using the deb package), deb package on Ubuntu
  • Mailspring Version: 1.8.0-8983dca2