arxim-lab
(Cpt. Huntsman)
March 14, 2021, 3:28pm
#1
Description
Failed to start MailSpring App.
To Reproduce…
Steps to reproduce the behavior:
Just start Mailspring
Expected Behavior
A window jumped out and told me “Mailspring has crashed.”
~ $ mailspring
Running database migrations
App load time: 226ms
{"error":null}
mailspring --type=renderer --no-sandbox --enable-features=SharedArrayBuffer --service-pipe-token=7037354014446856978 --lang=zh-CN --app-path=/usr/share/mailspring/resources/app.asar --user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Mailspring/1.8.0 Chrome/69.0.3497.128 Electron/4.2.12 Safari/537.36 --node-integration=true --webview-tag=true --no-sandbox --background-color=#fff --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=7037354014446856978 --renderer-client-id=4 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101: ../src/workers/open.cc:28:virtual void OpenWorker::Execute(): 假设 ‘sqlite3_db_mutex(db->db_handle) == __null’ 失败。
mailspring --type=renderer --no-sandbox --autoplay-policy=no-user-gesture-required --js-flags=--harmony --enable-features=SharedArrayBuffer --service-pipe-token=17215680302105642622 --lang=zh-CN --app-path=/usr/share/mailspring/resources/app.asar --user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Mailspring/1.8.0 Chrome/69.0.3497.128 Electron/4.2.12 Safari/537.36 --node-integration=true --webview-tag=true--no-sandbox --background-color=#fff --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=17215680302105642622 --renderer-client-id=6 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101: ../src/workers/open.cc:28:virtual void OpenWorker::Execute(): 假设 ‘sqlite3_db_mutex(db->db_handle) == __null’ 失败。
Manual update check (updates.getmailspring.com/check/linux/x64/1.8.0-8983dca2/anonymous/stable) returned 204
Failed to get crash dump id.
Report Id: {"success":true}
Failed to get crash dump id.
Report Id: {"success":true}
Screenshots
Setup
OS and Version: Archlinux (Linux-zen Kernel, all packages are up-to-date)
Installation Method: pacman installation from Archlinuxcn Source
Mailspring Version: 1.8.0-8983dca2
Additional Context
It was working before. And maybe after one system update, it fails.
Same error here, also using Archlinux. Seems after last kernel upgrade (yesterday, march-13-2021) this error appeared. Removed profile folder and uninstalled, installed again but no way.
Bookingyo
(Bookingyo)
March 14, 2021, 6:56pm
#3
I am getting the same thing in Arch after the latest updates.
Uninstalled Mailspring and installed it again did not fix the issue.
Also attempted to reinstall sqlite-3.34.1-1, since the error seems to be related to sqlite3.
The issue is with the update to gtk3, downgrading to 1:3.24.26-2 fixes it, though it’s only a temporary fix.
Jpfonseca
(João Fonseca)
March 14, 2021, 11:42pm
#5
Hey everyone,
The issue seems to be related with the latest GTK3 Archlinux build ,
This means tracker3 is the reason of the problem if I am not wrong.
This issue has been reported/solved before in a different distro :
NixOS
The update to gtk3 1:3.24.27-4 has fixed this for me.
Here I confirmed this, today gtk update has been applied and Mailspring now works again. Thank you very much all.
Bookingyo
(Bookingyo)
March 15, 2021, 7:26pm
#8
Works for me as well with the latest version of gtk3 1:3.24.27-4
Description
I get the error:
App load time: 313ms
{"error":null}
Manual update check (updates.getmailspring.com/check/linux/x64/1.8.0-8983dca2/8e4976bc-310c-4725-93e2-6dfdf11afad0/stable) returned 204
mailspring --type=renderer --no-sandbox --enable-features=SharedArrayBuffer --service-pipe-token=9686115835118150961 --lang=en-GB --app-path=/usr/share/mailspring/resources/app.asar --user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Mailspring/1.8.0 Chrome/69.0.3497.128 Electron/4.2.12 Safari/537.36 --node-integration=true --webview-tag=true --no-sandbox --background-color=#fff --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=9686115835118150961 --renderer-client-id=4 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101: ../src/workers/open.cc:28: virtual void OpenWorker::Execute(): Assertion sqlite3_db_mutex(db->db_handle) == __null' failed.
mailspring --type=renderer --no-sandbox --autoplay-policy=no-user-gesture-required --js-flags=--harmony --enable-features=SharedArrayBuffer --service-pipe-token=15070587304291527218 --lang=en-GB --app-path=/usr/share/mailspring/resources/app.asar --user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Mailspring/1.8.0 Chrome/69.0.3497.128 Electron/4.2.12 Safari/537.36 --node-integration=true --webview-tag=true --no-sandbox --background-color=#fff --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=15070587304291527218 --renderer-client-id=6 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101: ../src/workers/open.cc:28: virtual void OpenWorker::Execute(): Assertion `sqlite3_db_mutex(db->db_handle) == __null' failed.
Failed to get crash dump id.
To Reproduce…
Steps to reproduce the behavior:
Run mailspring from .desktop or terminal
Expected Behavior
For the app to launch
Setup
2 gmail accounts
OS and Version:
Arch Linux 5.11.6-arch1-1
Mailspring Version:
1.8.0-8983dca2
Additional Context
Slaviusz
(Slaviusz)
March 15, 2021, 8:21am
#10
I am seeing exactly the same issue. 4 Accounts (1x Outlook, 3x custom IMAP/SMTP). After recent system upgrade Mailspring does not start.
Tried moving ~/.config/Mailspring away but the same error appears even with no data.
$ mailspring
Running database migrations
App load time: 103ms
{"error":null}
mailspring --type=renderer --no-sandbox --enable-features=SharedArrayBuffer --service-pipe- token=13204721428936932628 --lang=en-US --app-path=/usr/share/mailspring/resources/app.asar --user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Mailspring/1.8.0 Chrome/69.0.3497.128 Electron/4.2.12 Safari/537.36 --node-integration=true --webview-tag=true --no-sandbox --background-color=#fff --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=13204721428936932628 --renderer-client-id=4 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101: ../src/workers/open.cc:28: virtual void OpenWorker::Execute(): Assertion `sqlite3_db_mutex(db->db_handle) == __null' failed.
mailspring --type=renderer --no-sandbox --autoplay-policy=no-user-gesture-required --js-flags=--harmony --enable-features=SharedArrayBuffer --service-pipe-token=3487667978737560133 --lang=en-US --app-path=/usr/share/mailspring/resources/app.asar --user-agent=Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Mailspring/1.8.0 Chrome/69.0.3497.128 Electron/4.2.12 Safari/537.36 --node-integration=true --webview-tag=true --no-sandbox --background-color=#fff --num-raster-threads=4 --enable-main-frame-before-activation --service-request-channel-token=3487667978737560133 --renderer-client-id=6 --shared-files=v8_context_snapshot_data:100,v8_natives_data:101: ../src/workers/open.cc:28: virtual void OpenWorker::Execute(): Assertion `sqlite3_db_mutex(db->db_handle) == __null' failed.
Manual update check (updates.getmailspring.com/check/linux/x64/1.8.0-8983dca2/76cb0153-1e9f-4f35-ba93-8b2e0049e435/stable) returned 204
Failed to get crash dump id.
Report Id: {"success":true}
Can confirm behavior. According to the AUR seems to be related to a recent GTK update.
Install gtk3-no_deadkeys_underline until there is a permanent fix.
As soon as tracker support is enabled in gtk mailspring does not start anymore.
See here for more info:
opened 10:47AM - 12 Dec 20 UTC
closed 09:27PM - 29 Dec 20 UTC
Describe the bug
At some point after a40d653 mailspring got broke, and now it fails to start with:
mailspring: ../src/workers/open.cc:28: virtual void OpenWorker::Execute():...
0.kind: bug
committed 01:32PM - 13 Mar 21 UTC
git-svn-id: file:///srv/repos/svn-packages/svn@409810 eb2447ed-0c53-47e4-bac8-5bc4a241df78
GTK3 has been updated to 1:3.24.27-4 on Arch and resolves the issue for me.
1 Like
Same here
mailspring
Running database migrations
App load time: 147ms
{“error”:null}
Manual update check (updates.getmailspring.com/check/linux/x64/1.8.0-8983dca2/125b3b83-0e75-4201-bc9b-aa99f21306c3/stable ) returned 204
mailspring --type=renderer --no-sandbox --autoplay-policy=no-user-gesture-required --js-flags=–harmony --enable-features=SharedArrayBuffer --s
like Gecko) Mailspring/1.8.0 Chrome/69.0.3497.128 Electron/4.2.12 Safari/537.36 --node-integration=true --webview-tag=true --no-sandbox --backg
ext_snapshot_data:100,v8_natives_data:101: …/src/workers/open.cc:28: virtual void OpenWorker::Execute(): Assertion sqlite3_db_mutex(db->db_ha mailspring --type=renderer --no-sandbox --enable-features=SharedArrayBuffer --service-pipe-token=15694025554640579459 --lang=en-US --app-path=/ 2 Safari/537.36 --node-integration=true --webview-tag=true --no-sandbox --background-color=#fff --num-raster-threads=4 --enable-main-frame-befo c:28: virtual void OpenWorker::Execute(): Assertion
sqlite3_db_mutex(db->db_handle) == __null’ failed.
Failed to get crash dump id.
Report Id: {“success”:true}
Failed to get crash dump id.
Report Id: {“success”:true}
<
CodeMouse92
(Jason C. McDonald)
March 15, 2021, 9:35pm
#14
Hey @rodude123 , I think this might be in your ballpark as our semi-official Arch maintainer.
Jpfonseca
(João Fonseca)
March 15, 2021, 11:31pm
#15
Works for me as well with the latest version of gtk3 1:3.24.27-4
Can confirm the issue is solved with the latest version of GTK3 1:3.24.27-4
.
@CodeMouse92 the issue is related to tracker3 which seems have been used as a parameter in the GTK3 build 1:3.24.27-3
. This might mean that in future GTK3 versions arch and other distros start to use this tracker3 feature and there’s a potencial for problems. I hope this is not the case.
2 Likes
mailsync-3ec92864.log (2.4 MB)
I was just logging in to my laptop that day and opened Mailspring to check email. It crashed four times.
A few hours later I was able to successfully log in without problems. This never happened before.
My OS is Archlinux.
Thank you,
Mark Ring