Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: crashes on startup Version-Release number of selected component: thunderbird-146.0-1.fc43 Additional info: reporter: libreport-2.17.15 type: CCpp reason: thunderbird killed by SIGSEGV journald_cursor: s=83f97f853db245b5807991f2914f8c67;i=a936f8;b=3ff73e1cb2cc40989fb6168633456e13;m=25ede592a;t=6465785b05765;x=a824e29683e159c1 executable: /usr/lib64/thunderbird/thunderbird cmdline: /usr/lib64/thunderbird/thunderbird cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-net.thunderbird.Thunderbird rootdir: / uid: 1000 kernel: 6.17.12-400.asahi.fc43.aarch64+16k package: thunderbird-146.0-1.fc43 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: __pthread_kill_implementation comment: crashes on startup Truncated backtrace: Thread no. 0 (1 frames) #0 __pthread_kill_implementation at pthread_kill.c:44 Potential duplicate: bug 2193201
Created attachment 2119310 [details] File: proc_pid_status
Created attachment 2119311 [details] File: maps
Created attachment 2119312 [details] File: limits
Created attachment 2119313 [details] File: environ
Created attachment 2119314 [details] File: open_fds
Created attachment 2119315 [details] File: mountinfo
Created attachment 2119316 [details] File: os_info
Created attachment 2119317 [details] File: cpuinfo
Created attachment 2119318 [details] File: core_backtrace
Created attachment 2119319 [details] File: dso_list
Created attachment 2119320 [details] File: var_log_messages
Created attachment 2119321 [details] File: backtrace
Can you see if https://bodhi.fedoraproject.org/updates/FEDORA-2025-35fc92cfa9 fixes this? I'm not 100% sure it's the same as the other crash. Thanks!
It does seem to be the same problem as Bug 2423824. The fix they rolled out with thunderbird-146.0.0.1-1.fc43.aarch64.rpm doesn't work to fix it. (confirmed doesn't fix it on my machine) I will mark this as duplicate. If 2423824 gets fixed but I'm still having issues, I will open a new bug report *** This bug has been marked as a duplicate of bug 2423824 ***