Red Hat Bugzilla – Bug 606979
[abrt] crash in thunderbird-3.0.4-3.fc13: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
Last modified: 2010-08-20 14:24:12 EDT
abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/thunderbird-3.0/thunderbird-bin component: thunderbird crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib64/thunderbird-3.0/thunderbird-bin global_uuid: 108db506fc67de4bf51a384d3ca9eaef5364e533 kernel: 2.6.33.5-124.fc13.x86_64 package: thunderbird-3.0.4-3.fc13 rating: 4 reason: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open email message 2. press control-p to print 3. crashy crashy
Created attachment 426082 [details] File: backtrace
Thank you for taking the time to report this bug. Updates to this package have been released since it was first reported. If you have time to update the package and re-test, please do so and report the results here. You can obtain the updated package by typing 'yum update' or using the graphical updater, Software Update. Disable any extensions, plugins and non-default themes. Exit cleanly and restart thunderbird. Are you able to replicate the crash? #2 <signal handler called> No symbol table info available. #3 __pthread_mutex_lock (mutex=0x28) at pthread_mutex_lock.c:50 type = <value optimized out> id = <value optimized out> #4 0x00000032c48b734b in int_err_get (create=1) at err.c:354 ret = 0x0 #5 0x00000032c48b709b in int_err_set_item (d=0x32c4b8c1e0) at err.c:402 p = <value optimized out> hash = <value optimized out> #6 0x00000032c48b6a4c in err_load_strings (lib=0, str=0x32c4b8c1e0) at err.c:676 No locals. #7 0x00000032c48b7fb1 in ERR_load_ERR_strings () at err.c:662 No locals. #8 0x00000032c48b8199 in ERR_load_crypto_strings () at err_all.c:113 No locals. #9 0x00000032c4c39769 in SSL_load_error_strings () at ssl_err2.c:66 -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
No, I can no longer reproduce the issue.
Excellent! Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers