1545489 - Thunderbird segmentation fault at startup after adding email account

Status: RESOLVED DUPLICATE of bug 1514605

(Thunderbird :: Account Manager, defect)

Description

[Gianluca]

Attachment: thunderbird.log

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

1. Create a new profile using the Profile Manager by launching Thunderbird with the -P flag
2. Add a new IMAP account

Actual results:

After setting up the IMAP account, Thunderbird immediately shuts down with the following message:
"[1] 8075 segmentation fault (core dumped) thunderbird"

This happens every time I launch Thunderbird after setting up the new profile.

I get the same results with the packaged version by the Manjaro maintainers, with the Snap package (https://snapcraft.io/thunderbird) and with the version downloaded from the official website.

Everything works well when repeating the steps above using a separate Linux user, suggesting that maybe there are some user-specific files or folders interfering with Thunderbird. Deleting the .thunderbird folder from my home directory does solve the issue.

Attached is the terminal output the following command and following the steps indicated above:

gianluca@t480 [18:44:31] [~]
-> LD_DEBUG=files thunderbird -P &> thunderbird.log
[1] 10206 segmentation fault (core dumped) LD_DEBUG=files thunderbird -P &> thunderbird.log

Expected results:

Thunderbird should just download existing mails from the IMAP server and not crash.

Comment 1

[Gianluca]

Sorry for the type, I meant to say that "deleting the .thunderbird folder from my home directory does NOT solve the issue".

Comment 2

[Gianluca]

Attachment: tb-strace.log

strace output for the linux user where the segfault happens

Comment 3

[Gianluca]

Attachment: tb-strace-test.log

strace output for the 'test' user, i.e. the linux user for which Thunderbird DOES NOT segfault.

Comment 4

[Nate Graham]

I was experiencing this bug but found that it was because I had GTK_USE_PORTAL=1 set in my environment; unsetting that envar that fixed the issue. So this may be a duplicate of Bug 1514605.