Thunderbird crashes on Asahi and/or aarch64

Ask Fedora
, ,
1

I open this topic to move posts regarding an Asahi/aarch64 Thunderbird bug here, which were posted in bug topics regarding a solved x86_64 thunderbird bug (which we can assume at this time to be not related).

I elaborated the point in the discourse topic post #21 and the bugzilla ticket BZ#2423824 comment 32 of the x86_64 bug.

Below is the extract of the bugzilla ticket, including links that might contain further indication about this, and also indication that this aarch64/asahi bug in thunderbird might be the same as one in firefox (read through the bodhi links and the related posts about aarch64/asahi, including a further bug report). Keep in mind that I have not opened a bugzilla ticket (maybe someone else did already → check bugzilla for existing thunderbird tickets before opening a new one). Extract of comment 32 in the bugzilla ticket:

@<username> @<username> @<username> All your reports have in common the architecture: aarch64.

Since this bug ticket is linked to x86_64, which seems to be no longer affected by a segFault, I suggest you open a new one for this. In case of a doubt, that might be an issue related to aarch64, and might be best addressed in a bug ticket linked to aarch64.

Also, a quick search shows that Firefox currently has an issue related to crashes on aarch64: while firefox is not thunderbird, the two share a lot.

Maybe that is interesting for you (I still would create a separated bug ticket for Thunderbird against aarch64 but maybe link it to its Firefox aarch64 bug ticket > counterparts if there are further similarities):
Making sure you're not a bot!
Making sure you're not a bot!
Making sure you're not a bot!
→ more links to bug tickets etc contained

Please ping me with @py0xc3 here if I shall change the title of this topic.

I close the old topic, as it has been solved.

Thunderbird crashes on start since update to 146.0-1.fc43
2

Is this fix available in flatpak for fedora silverblue?
I am running fedora:fedora/43/aarch64/silverblue Version: 43.20260101.0 (2026-01-01T00:27:12Z)
and
lt@fsbmac:~$ flatpak info net.thunderbird.Thunderbird

Thunderbird - Thunderbird is a free and open source email, newsfeed, chat, and
calendaring client

      ID: net.thunderbird.Thunderbird
     Ref: app/net.thunderbird.Thunderbird/aarch64/stable
    Arch: aarch64
  Branch: stable
 Version: 146.0.1
 License: MPL-2.0
  Origin: fedora

Collection:
Installation: system
Installed: 315.5 MB
Runtime: org.fedoraproject.Platform/aarch64/f43
Sdk: org.fedoraproject.Sdk/aarch64/f43

  Commit: 40f1d01ddfad6ca03ea47084163d6f25da0945ffc6eb36439720595f4510c7c8
 Subject: Export net.thunderbird.Thunderbird
    Date: 2025-12-24 17:48:26 +0000
  Alt-id: 7f7a399e848cccb63dd4af0c3e635a88bfb1e287e74eca61b230f675832790fe

But this is not starting:
lt@fsbmac:~$ flatpak run net.thunderbird.Thunderbird
[2] Sandbox: CanCreateUserNamespace() clone() failure: EPERM

The odd thing is that it works just fine same on another VM identical wrt to versions but with x86_64 architecture

Thunderbird crashes on start since update to 146.0-1.fc43
Thunderbird crashes on start since update to 146.0-1.fc43
Thunderbird crashes on start since update to 146.0-1.fc43
3

Hi,

Same here on Fedora Asahi Remix 42 : since update to thunderbird-146.0.1-2.fc42 (aarch64) yesterday , Thunderbird crashes on start.

What I get in Konsole is (sorry for French) :

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: FireTestProcess failed: L’exécution du processus fils « /usr/lib64/thunderbird/v4l2test » a échoué (Aucun fichier ou dossier de ce nom)
(t=0.376193) [GFX1-]: FireTestProcess failed: L’exécution du processus fils « /usr/lib64/thunderbird/v4l2test » a échoué (Aucun fichier ou dossier de ce nom)

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: FireTestProcess failed: L’exécution du processus fils « /usr/lib64/thunderbird/v4l2test » a échoué (Aucun fichier ou dossier de ce nom)
(t=0.376193) |[1][GFX1-]: Failed to start v4l2test process
(t=0.376193) [GFX1-]: Failed to start v4l2test process

Erreur de segmentation (core dumped)

What I get in crash report :

reason thunderbird killed by SIGSEGV

crash_function __pthread_kill_implementation

4

Please try this build when it’s done. If anyone confirms it works I’ll submit it as an official update.

2 Likes
5

I can confirm that thunderbird-146.0.1-3.fc43.aarch64.rpm doesn’t crash on startup on my Asahi machine

1 Like
6

awesome, thank you very much. I’ll submit the builds as official updates when they’re done, then.

2 Likes
7

No, thank you! I really appreciate your work on getting this resolved

8

I just tried thunderbird-146.0.1-3.fc42 and I confirm that it doesn’t crash anymore on start (i’m running Fedora Asahi Remix 42).

Thank you very much

1 Like
9

The issue is also seen on Silverblue and so the fix for flatpak is also needed. Would you provide that pls

10

I’ll try to figure out/remember how tomorrow. Don’t do flatpak builds often.

1 Like
11

Is it known if/when the TB maintainer is back? I wasn’t wondering at the bug ticket of October, as it was quite eccentric & it seems I am the only one affected by that, so there was/is understandable reason to not emphasize it, but the last issue seems to have been quite critical (I think it’s not stransky but “Jan”, whom you set needinfo in the ticket without getting response?).

I was just out of curiosity checking the last 5 thunderbird tickets based on last update, but could not see that any of them had been received a response from the maintainer, going back longer than October (this is definitely not a representative search, and I did not check how legitimate the tickets are, so that is not an accusation or so, but just a question) (?)

12

The official maintainer is Jan Horak (@xhorak). He was away for the Red Hat shutdown last week, probably. He is active, he’s the one who backported the crash fix to Firefox in the first place. I just noticed it was missing from Thunderbird and that was a pretty good suspect for the problems people were hitting.

Jan’s made lots of changes to the Thunderbird package recently, he’s not inactive or anything. Bugs can go unanswered for a while for various reasons, probably none of us maintainers have a perfect record on answering bug reports…

1 Like