Hi all,
I'm experiencing persistent and reproducible segmentation fault crashes with both Thunderbird (versions 140.0.1, 141, and 142 tested) and Betterbird on Arch Linux… (read more)
Hi all,
I'm experiencing persistent and reproducible segmentation fault crashes with both Thunderbird (versions 140.0.1, 141, and 142 tested) and Betterbird on Arch Linux. The crashes occur consistently within 30 seconds to 2 minutes of operation, making the application unusable.
System Configuration:
- Arch Linux (fully updated)
- KDE Plasma 6 on Wayland
- Multi-monitor setup using DisplayLink/evdi drivers
- Firefox works perfectly fine (no crashes)
What I've Already Tried:
- Fresh profiles (completely clean - crashes persist)
- Safe mode with add-ons disabled
- Disabling hardware acceleration (MOZ_DISABLE_RDD_SANDBOX=1, --disable-gpu)
- Software rendering mode
- Multiple Thunderbird versions (140, 141, 142)
- Alternative client (Betterbird) - same crashes
- Full system upgrade
All crashes show the same signature in libxul.so during startup/operation. The stack traces consistently point to Mozilla's threading/compositor code. Notably, Firefox using the same libxul.so library works without any issues, which suggests this is Thunderbird-specific.
I believe the issue is related to KWin compositor interaction with my multi-monitor DisplayLink (evdi) setup on Wayland. The crashes are specific to Thunderbird/Betterbird and do not occur with Firefox, despite them sharing core libraries. Note that this problem happens on both x11 and Wayland.
I have extensive coredumpctl output available if that would be helpful for debugging. Has anyone else experienced similar crashes with multi-monitor setups or KWin/Wayland compositor issues?
Any assistance would be greatly appreciated!