Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm
Đã lưu trữ

Continuous Thunderbird SIGSEGV crashes on Linux (libxul.so)

paull2 đã trả lời
paull2

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!

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!

Được chỉnh sửa bởi paull2 vào

Tất cả các câu trả lời (3)

Thanks for the reply, @Wayne. Unfortunately, after *many* attempts to get about:config to actually load (the app just keeps crashing within seconds of loading), I found that devtools.toolbox.host was already set to 'bottom'. That is, the proposed solution unfortunately does not solve this issue.

Được chỉnh sửa bởi paull2 vào

Unfortunately this solution did not work for me. It took many tries to get to about:config (a rather challenging feat when Thunderbird dies within seconds of opening it) only to find that the suggested variable already was set to 'bottom'. That is, the proposed solution did not work in this case.

Thank you for the reply @Wayne. I appreciate your help. Not sure where to go from here :(