Mailspring 1.10.5 crashes at start on Debian 11

Bug Reports Resolved
,
#1

Description

When I tried to open Mailspring in MX Linux 21 (based on Debian 11) it crashed with the following message in the console:

[72962:0817/092035.906188:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
Running database migrations
App load time: 238ms
Error: “@electron/remote” cannot be required in the browser process. Instead require("@electron/remote/main").
at Object. (/usr/share/mailspring/resources/app.asar/node_modules/@electron/remote/dist/src/renderer/index.js:14:11)
at Module._compile (node:internal/modules/cjs/loader:1116:14)
at Object.Module._extensions…js (node:internal/modules/cjs/loader:1169:10)
at Module.load (node:internal/modules/cjs/loader:988:32)
at Module._load (node:internal/modules/cjs/loader:829:12)
at Function.c._load (node:electron/js2c/asar_bundle:5:13343)
at Module.require (node:internal/modules/cjs/loader:1012:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (/usr/share/mailspring/resources/app.asar/node_modules/@electron/remote/renderer/index.js:1:-44)
at Module._compile (node:internal/modules/cjs/loader:1116:14)
at Object.Module._extensions…js (node:internal/modules/cjs/loader:1169:10)
at Module.load (node:internal/modules/cjs/loader:988:32)
at Module._load (node:internal/modules/cjs/loader:829:12)
at Function.c._load (node:electron/js2c/asar_bundle:5:13343)
at Module.require (node:internal/modules/cjs/loader:1012:19)
at require (node:internal/modules/cjs/helpers:102:18)
at MailsyncProcess._showStatusWindow (file:///tmp/nylas-build/electron-packager/linux-x64/mailspring-linux-x64/resources/app/src/mailsync-process.ts:108:31)
at onData (file:///tmp/nylas-build/electron-packager/linux-x64/mailspring-linux-x64/resources/app/src/mailsync-process.ts:357:52)
at Socket. (file:///tmp/nylas-build/electron-packager/linux-x64/mailspring-linux-x64/resources/app/src/mailsync-process.ts:197:23)
at Socket.emit (node:events:390:28)
at Socket.emit (node:domain:475:12)
at addChunk (node:internal/streams/readable:315:12)
at readableAddChunk (node:internal/streams/readable:289:9)
at Socket.Readable.push (node:internal/streams/readable:228:10)
at Pipe.onStreamRead (node:internal/stream_base_commons:199:23) uncaughtException
(node:72926) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
(Use mailspring --trace-deprecation ... to show where the warning was created)
Raven: 429 - undefined
Raven: 429 - undefined
Error: “@electron/remote” cannot be required in the browser process. Instead require("@electron/remote/main").
at Object. (/usr/share/mailspring/resources/app.asar/node_modules/@electron/remote/dist/src/renderer/index.js:14:11)
at Module._compile (node:internal/modules/cjs/loader:1116:14)
at Object.Module._extensions…js (node:internal/modules/cjs/loader:1169:10)
at Module.load (node:internal/modules/cjs/loader:988:32)
at Module._load (node:internal/modules/cjs/loader:829:12)
at Function.c._load (node:electron/js2c/asar_bundle:5:13343)
at Module.require (node:internal/modules/cjs/loader:1012:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (/usr/share/mailspring/resources/app.asar/node_modules/@electron/remote/renderer/index.js:1:-44)
at Module._compile (node:internal/modules/cjs/loader:1116:14)
at Object.Module._extensions…js (node:internal/modules/cjs/loader:1169:10)
at Module.load (node:internal/modules/cjs/loader:988:32)
at Module._load (node:internal/modules/cjs/loader:829:12)
at Function.c._load (node:electron/js2c/asar_bundle:5:13343)
at Module.require (node:internal/modules/cjs/loader:1012:19)
at require (node:internal/modules/cjs/helpers:102:18)
at MailsyncProcess._showStatusWindow (file:///tmp/nylas-build/electron-packager/linux-x64/mailspring-linux-x64/resources/app/src/mailsync-process.ts:108:31)
at onData (file:///tmp/nylas-build/electron-packager/linux-x64/mailspring-linux-x64/resources/app/src/mailsync-process.ts:357:52)
at Socket. (file:///tmp/nylas-build/electron-packager/linux-x64/mailspring-linux-x64/resources/app/src/mailsync-process.ts:197:23)
at Socket.emit (node:events:390:28)
at Socket.emit (node:domain:475:12)
at addChunk (node:internal/streams/readable:315:12)
at readableAddChunk (node:internal/streams/readable:289:9)
at Socket.Readable.push (node:internal/streams/readable:228:10)
at Pipe.onStreamRead (node:internal/stream_base_commons:199:23)

To Reproduce…

Steps to reproduce the behavior:

  1. Open Mailspring 1.10.5 on Debian 11 based distro in the console
  2. See the error

Expected Behavior

It should open Mailspring

Setup

  • OS and Version: MX Linux 21
  • Installation Method: .deb
  • Mailspring Version: 1.10.5
#2

I see this error on Arch Linux and Mailspring v1.10.6-ba7e89bb (mailspring@1.10.6-1), however, it does not happen all the time. I attached the latest logs.
mailspring_20221121_064829.log (4.9 KB)

On the subsequent run, I get the following logs:

Running database migrations
App load time: 170ms

{"error":null}
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Manual update check (updates.getmailspring.com/check/linux/x64/1.10.6-ba7e89bb/f0347ffe-641d-420f-99ab-80b7c712d6a7/stable) returned 204
[55400:1121/070120.322713:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.portal.Desktop': timed out (service_start_timeout=120000ms)
[55400:1121/070120.322832:ERROR:select_file_dialog_impl_portal.cc(243)] Failed to read portal version property

Note that I use NVIDIA T1000 GPU if that might be an issue.

See also this comment in issue electron/remote#66.

#3

Submitted PR for original issue

Fix for start crash - Community#5324 by glenn2223 · Pull Request #2437 · Foundry376/Mailspring (github.com)

@tukusejssirs, your issue seems separate. You should probably open a separate issue for someone familiar with your OS to investigate

#4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

#5

Will be resolved with the next version.

Thanks a lot for the bugfix @glenn2223