Hide Forgot
Description of problem: Thunderbird 8 fails in certain situations, such as clicking on Tools->Add-Ons with disgnostics: Inconsistency detected by ld.so: dl-open.c: 603: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed! Version-Release number of selected component (if applicable): thunderbird-8.0-2.fc16.x86_64 Binary 64-bit build of Thunderbird 8 (from ftp.mozilla.org) fails in the same manner. Binary 32-bit builds of Thunderbird 8 are not affected. How reproducible: Always (when trying to run Add-On manager); sporadically in other unidentified cases (an attempt to click on a folder with significant number could trigger the same failure) When run with -safe-mode switch, launching Add-On manager crashes Thunderbird in the same manner. When run with .thunderbird directory removed (empty profile) Thunderbird fails in the same manner. Steps to Reproduce: 1. Setup Fedora 16 with LDAP authentication (via sssd) 2. Logon as LDAP-authenticated user (non-local) 2. Run nscd (otherwise, Thunderbird segfaults on startup) 3. Install Thunderbird 8 64-bit and run it 4. Click on Tools->Add-Ons Actual results: Fails with diagnostics like Inconsistency detected by ld.so: dl-open.c: 603: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed! Expected results: Add-On manager should work normally. Additional info: 32-bit versions of Thunderbird 8 seem not affected by this bug.
This is most likely problem with mixing system ldap library and Thunderbird's own library. It would be nice to have a backtrace of crash. To get one please install debuginfo package for Thunderbird by: debuginfo-install thunderbird Then run 'thunderbird -g -d gdb' and start thunderbird by 'run' command. After crash occurs use 't a a bt' to get backtrace of all threads. Please attach this output to this bug. Thanks.
Created attachment 535803 [details] GDB thunderbird crash backtrace The GDB backtrace output requested
Hello jan, Before is entire gdb output you asked. gdb.txt is also attached. Methinks, it contains little information - have I done something wrong? $ thunderbird -g -d gdb /usr/lib64/thunderbird/run-mozilla.sh -g -d gdb /usr/lib64/thunderbird/thunderbird-bin MOZILLA_FIVE_HOME=/usr/lib64/thunderbird LD_LIBRARY_PATH=/usr/lib64/thunderbird:/usr/lib64/thunderbird/plugins:/usr/lib64/thunderbird DISPLAY=:0 DYLD_LIBRARY_PATH=/usr/lib64/thunderbird:/usr/lib64/thunderbird LIBRARY_PATH= SHLIB_PATH=/usr/lib64/thunderbird:/usr/lib64/thunderbird LIBPATH=/usr/lib64/thunderbird:/usr/lib64/thunderbird ADDON_PATH= MOZ_PROGRAM=/usr/lib64/thunderbird/thunderbird-bin MOZ_TOOLKIT= moz_debug=1 moz_debugger=gdb moz_debugger_args= /usr/bin/gdb --args /usr/lib64/thunderbird/thunderbird-bin GNU gdb (GDB) Fedora (7.3.50.20110722-10.fc16) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/lib64/thunderbird/thunderbird-bin...Reading symbols from /usr/lib/debug/usr/lib64/thunderbird/thunderbird-bin.debug...done. done. (gdb) set logging on Copying output to gdb.txt. (gdb) run Starting program: /usr/lib64/thunderbird/thunderbird-bin [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Detaching after fork from child process 2746. [New Thread 0x7fffecbfb700 (LWP 2747)] [New Thread 0x7fffebe3f700 (LWP 2748)] [New Thread 0x7fffeb63e700 (LWP 2749)] [New Thread 0x7fffeabff700 (LWP 2750)] [New Thread 0x7fffe9bff700 (LWP 2751)] [New Thread 0x7fffe93fe700 (LWP 2752)] [New Thread 0x7fffe7cc1700 (LWP 2753)] enigmail.js: Registered components [New Thread 0x7fffe71ff700 (LWP 2754)] [New Thread 0x7fffe67ff700 (LWP 2755)] [New Thread 0x7fffe5ffe700 (LWP 2756)] [Thread 0x7fffe7cc1700 (LWP 2753) exited] [New Thread 0x7fffe55ff700 (LWP 2757)] [Thread 0x7fffe5ffe700 (LWP 2756) exited] [Thread 0x7fffe67ff700 (LWP 2755) exited] [New Thread 0x7fffe7cc1700 (LWP 2758)] [New Thread 0x7fffe67ff700 (LWP 2759)] [Thread 0x7fffe55ff700 (LWP 2757) exited] [New Thread 0x7fffe55ff700 (LWP 2760)] [Thread 0x7fffe55ff700 (LWP 2760) exited] [New Thread 0x7fffe55ff700 (LWP 2761)] [New Thread 0x7fffe5ffe700 (LWP 2762)] [New Thread 0x7fffdcdff700 (LWP 2763)] [Thread 0x7fffdcdff700 (LWP 2763) exited] [New Thread 0x7fffdcdff700 (LWP 2764)] [New Thread 0x7fffdaf72700 (LWP 2765)] [New Thread 0x7fffda771700 (LWP 2766)] [New Thread 0x7fffd9f70700 (LWP 2767)] [New Thread 0x7fffd92ff700 (LWP 2768)] [New Thread 0x7fffd8afe700 (LWP 2769)] [New Thread 0x7fffd82fd700 (LWP 2770)] [Thread 0x7fffe67ff700 (LWP 2759) exited] [New Thread 0x7fffe67ff700 (LWP 2771)] [New Thread 0x7fffd2aff700 (LWP 2772)] [Thread 0x7fffd9f70700 (LWP 2767) exited] [New Thread 0x7fffd22fe700 (LWP 2773)] [New Thread 0x7fffd9f70700 (LWP 2774)] [New Thread 0x7fffd16ff700 (LWP 2775)] [Thread 0x7fffd16ff700 (LWP 2775) exited] Missing separate debuginfo for /home/mbo/.mozilla/plugins/libjavaplugin.so Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/47/c42393aabb5845d0873806484c05b059a50714.debug Missing separate debuginfo for /home/mbo/.mozilla/plugins/libnpgoogletalk64.so Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/2f/c0650d6bb2e1507e1ee653f293661ec3777284.debug Inconsistency detected by ld.so: dl-open.c: 603: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed! [Thread 0x7fffd22fe700 (LWP 2773) exited] [Thread 0x7fffd82fd700 (LWP 2770) exited] [Thread 0x7fffda771700 (LWP 2766) exited] [Thread 0x7fffd9f70700 (LWP 2774) exited] [Thread 0x7fffd92ff700 (LWP 2768) exited] [Thread 0x7fffdaf72700 (LWP 2765) exited] [Thread 0x7fffd2aff700 (LWP 2772) exited] [Thread 0x7fffe67ff700 (LWP 2771) exited] [Thread 0x7fffd8afe700 (LWP 2769) exited] [Thread 0x7fffdcdff700 (LWP 2764) exited] [Thread 0x7fffe5ffe700 (LWP 2762) exited] [Thread 0x7fffe7cc1700 (LWP 2758) exited] [Thread 0x7fffe71ff700 (LWP 2754) exited] [Thread 0x7fffe93fe700 (LWP 2752) exited] [Thread 0x7fffe9bff700 (LWP 2751) exited] [Thread 0x7fffeabff700 (LWP 2750) exited] [Thread 0x7fffeb63e700 (LWP 2749) exited] [Thread 0x7fffebe3f700 (LWP 2748) exited] [Thread 0x7fffecbfb700 (LWP 2747) exited] [Thread 0x7fffe55ff700 (LWP 2761) exited] [Inferior 1 (process 2743) exited with code 0177] (gdb) t a a bt (gdb) set logging off Done logging to gdb.txt. (gdb) quit
Is something else expected from me at this moment?
For me this bug happens after 5-10 mins of uptime of thunderbird. I can manually trigger it by going to Add-on manager but it happens by itself after 5-10 mins as well. This is a blocker because it kills thunderbird. Anybody has any ideas about a possible workaround?
Uninstalling google talk plugin makes the crash go away for me. I can't reproduce the crash by doing either of the things I mentioned above. Can the original reporter mention if he is using the google talk plugin as well?
2devsk: no, I am not using Google Talk plugin. The only solution that worked for me was to install manually 16-bit version of Thunderbird, which isn't plagued by this bug.
(In reply to comment #7) > 2devsk: no, I am not using Google Talk plugin. According to backtrace it seems you have it installed, see: /home/mbo/.mozilla/plugins/libnpgoogletalk64.so What kind of plugin is it? Where can I get it? > The only solution that worked for me was to install manually 16-bit version of > Thunderbird, which isn't plagued by this bug. You probably mean 32-bit version of thunderbird, in that case 64 bit plugin (libnpgoogletalk64.so) can't be loaded, so that's why no crash occurs. Try to remove Google Talk plugin for workaround.
Jan, You can get it at: http://www.google.com/talk/ I think its important for most users that this plugin works with thunderbird because its part of the standard install and not in user's hands i.e. its in /usr/lib somewhere and I as a user can't unload it because I can't write to /usr/lib. Moreover, firefox seems to be ok with it. Thunderbird should be ok with it too.
2Jan Horak : I haven't installed the plugin explicitly. All I have done was installing g Thunderbird from Fedora's repository. As told in the original bug desciption, Thunderbird fails even when run with empty profile, where no plugins could ever be specified.
Plugins are dlopen'ed whether they are used or not. So, a standard install with google talk plugin WILL make thunderbird fail.
Sorry, I can't reproduce with: rpm -q thunderbird google-talkplugin thunderbird-8.0-2.fc16.x86_64 google-talkplugin-2.5.6.0-1.x86_64 Unfortunately Konstantin's backtrace is not much usable. It actually miss any backtrace (it seems that Thunderbird just finished the executin, I see no crash here, you need to do the 't a a bt' after crash occurs). Also notice that thunderbird profiles stays in .thunderbird, while google talk is loaded from .mozilla/plugins. Please try to check this directory.
Confirming that Seamonkey 64-bit fails in exactly the same way. Once more: what data do you need from me to help you to find the bug? The problem is reproduced on every computer in our intranet where LDAP authentication is used.
I have removed the Google talk plugin from ~/.mozilla/plugins Nothing changed, Thunderbird fails in the same manner.
(In reply to comment #13) > Confirming that Seamonkey 64-bit fails in exactly the same way. > > Once more: what data do you need from me to help you to find the bug? The > problem is reproduced on every computer in our intranet where LDAP > authentication is used. Same instructions as described on my first comment. Please check if thunderbird debuginfo is installed(rpm -q thunderbird-debuginfo). > Nothing changed, Thunderbird fails in the same manner. In your case there's maybe more reasons. Without correct backtrace we're unable to resolve this issue (something like https://bugzilla.redhat.com/attachment.cgi?id=317776 ).
2Jan Horak: Thunderbird 10 x86_64 bit crashes in exactly the same manner. I updated the thunderbird-debuginfo and tried to generate the debug information as in the previous case. However, after thunderbird -g -d gdb gdb> run gdb> t a a bt gdb> set logging off nothing ahs been generated. Could you provide me *exact* command to generate data you require? Thanks.
(In reply to comment #16) > 2Jan Horak: > > Thunderbird 10 x86_64 bit crashes in exactly the same manner. > I updated the thunderbird-debuginfo and tried to generate the debug information > as in the previous case. However, after > > thunderbird -g -d gdb > gdb> run > gdb> t a a bt > gdb> set logging off > > nothing ahs been generated. Could you provide me *exact* command to generate > data you require? > > Thanks. I usually don't use logging. What does 'bt' command show after crash? For exact instructions look here: http://fedoraproject.org/wiki/StackTraces#gdb
We've written some debugging guidelines. How to install debuginfo package see: https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Installing_debug_info_packages and continue in 'Running application in debugger' and 'Obtain crash stack trace' sections. Thanks.
Hm, the LDAPS crashes. Reported, do you still see it, in the new Thunderbird 12?
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.