Hide Forgot
Description of problem: When run by a user authorized against external LDAP server, Thunderbird segfaults, the following is found in /var/log/messages: thunderbird-bin[3135]: segfault at 7f6597fa20de ip 00007f65a5dea89b sp 00007fff8f267ba8 error 7 in libc-2.14.90.so[7f65a5d62000+1aa000] Version-Release number of selected component (if applicable): Thunderbird 7.0.1 x86_64 from standard Fedora 16 repository How reproducible: If run by the mentioned type of user, Thunderbird 7.0.1 64-bit always crashes in the same manner, regardless of whether it's from repository, or downloaded as tarballed binary distribution. If the mentioned version of Thunderbird is run by local (shadow) user, it works fine. 32-bit versions work fine with any user (when all the required 32-bit packages are installed) Steps to Reproduce: 1. Setup LDAPS (ldasps://) authentication in Fedora 16 and make whatever configuration changes required that sssd started to authenticate users correctly (it doesn't by default) 2. Install Thunderbird 7.0.1 64-bit 3. Log in as LDAP-authenticated user and run Thunderbird. Actual results: Thunderbird segfaults. By default, the only message is the one posted to /var/log/messages Expected results: Thunderbird should run normally.
Note: running nscd daemon seems to handle the above segfault event. Please verify that as well. Thank you.
Thunderbird 9 behaves in the same manner. 64-bit crashes, 32-bit works. Am I right supposing no one is about to handle this bug or even consider it a bug at all? If any input from me is expected, please tell me how to generate it. I am only installing Thunderbird as it is, eitehr from RPM or from binary Linux distributions by Mozilla. Thanks.
I have the same problem Name : thunderbird Version : 9.0 Release : 4.fc16 Architecture: x86_64 User connected with LDAP (not LDAPS) Cheers
Thunderbird 10.0 x86_64, from default Fedora 16 repository, starts and works fine up to an attempt to open add-on manager. After that, it crashes. Will developers try a bit more and fix the add-on manager-related crash? What data shall I provide for that?
Please provide bactrace - https://fedoraproject.org/wiki/StackTraces#Firefox (it's the same as for Firefox).
Created attachment 566055 [details] backtrace for thunderbird crash Here is the backtrace for the thunderbird crash. First, you have thunderbird launched in the debugger and the resulting segfault, then the trace given by gdb Hope it could help. Cheers
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.