On Mon, Apr 16, 2018 at 11:00:46AM +0200, Paride Legovini wrote:
> Thunderbird 60 (experimental) crashes when sending GPG encrypted mail
> usging enigmail. This was not happening with Thunderbird 58, again from
> experimental. I can always reproduce the issue and it doesn't happen
> with signed only messages.
due you use the enigmail package from experimental or installed locally?
I assume you use a local installed enigmail addon. Thunderbird uses
since version 59 a different addon interface, only webextension is now
Unfortunately I need to confirm this behavior on my local setup no
matter if I use the enigmail package from experimental or a local
> The backtrace is not very useful. The ‘vendor.js’ parse error appears as
> Thunderbird starts, and I don't think it's relevant for this issue. The
> rest appears as I (try to) send the encrypted message.
> $ RUST_BACKTRACE=1 thunderbird
> /usr/lib/thunderbird/defaults/pref/vendor.js:2: prefs parse error: unknown
> thread '<unnamed>' panicked at '`before_sheet` stylesheet not found',
> stack backtrace:
> 0: <unknown>
> 1: <unknown>
> 2: <unknown>
> 3: <unknown>
> 99: <unknown>
> Redirecting call to abort() to mozalloc_abort
> ExceptionHandler::GenerateDump cloned child 5841
> ExceptionHandler::SendContinueSignalToChild sent continue signal to child
> ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Yes, the debugging will be slightly different now. For this the starting
wrapper needs to be adjusted again and for now the calls need to be done
manually to get backtraces.
$ sudo apt install thunderbird-dbgsym
$ RUST_BACKTRACE=1 gdb /usr/lib/thinderbird/thunderbird
(gdb) thread applly all bt
I've done this yesterday quickly but didn't have seen a catch to get a
clued what's going wrong here. So I've no idea if thunderbird or
enigmail itself is causing this segfault. On the other hand thunderbird
isn't allowed to crash anyway.
If possible append a backtrace as file please.