GNOME Bugzilla – Bug 135986
Crashes when exiting after making update to "File types and programs" settings
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: nautilus Severity: blocker Version: GNOME2.4.0 unspecified Gnome-Distributor: GNOME.Org Synopsis: Crashes when exiting after making update to "File types and programs" settings Bugzilla-Product: nautilus Bugzilla-Component: Preferences Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: When selecting File->Close all windows, Nautilus crashes. This occurs when trying to add /usr/local/Acrobat5/bin/acroread as a handler for PDF files. Steps to reproduce the crash: 1. In Nautilus, right-click a PDF file and select 'open with...' 2. Select the 'go there' button to open the "File types and programs" application 3. Select /usr/local/Acrobat5/bin/acroread as a custom handler to open PDF file types. 4. Close the "File types and programs" application 5. In Nautilus, select File->close all windows Expected Results: acroread should have been added as a handler application for PDF files. Nautilus should have exited without crashing. How often does this happen? 100% Additional Information: I have 3 SMB mounts, 2 owned by root and 1 owned by the user I login as. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1085057152 (LWP 15972)] [New Thread -1088783440 (LWP 15979)] [New Thread -1088517200 (LWP 15978)] [New Thread -1088250960 (LWP 15977)] [New Thread -1087984720 (LWP 15976)] [New Thread -1087718480 (LWP 15975)] [New Thread -1087452240 (LWP 15974)] [New Thread -1087186000 (LWP 15973)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x00b65c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 44730
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-03-02 12:29 ------- Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
I tried reproducing this with nautilus-2.4.2, but couldn't. This is stacktrace is unfortunately, not useful. Could you install debug packages for nautilus, gnome-vfs2, and gtk from here: http://download.fedora.redhat.com/pub/fedora/linux/core/1/i386/debug/ and try to get a better stacktrace? And what versions of nautilus does this happen with? Thanks.
*Nautilus version I'm using(haven't tried other versions): Gnome nautilus 2.4.0 *Debug packages I now have installed: rpm -qa | grep debug mozilla-js-debugger-1.4.1-18 gtk-engines-debuginfo-0.12-1 glibc-debug-2.3.2-101.4 xmms-debuginfo-1.2.10-1 gtk2-debuginfo-2.2.4-5.1 gnome-vfs2-debuginfo-2.4.1-1 gtk+-debuginfo-1.2.10-28.1 gtk2-engines-debuginfo-2.2.0-3 nautilus-debuginfo-2.4.0-7 *New backtrace(hopefully more useful): Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1085319296 (LWP 3012)] [New Thread -1089045584 (LWP 3029)] [New Thread -1088779344 (LWP 3028)] [New Thread -1088513104 (LWP 3027)] [New Thread -1088246864 (LWP 3026)] [New Thread -1087980624 (LWP 3025)] [New Thread -1087714384 (LWP 3024)] [New Thread -1087448144 (LWP 3023)] 0x00b65c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 44917
Thread 1 (Thread -1085319296 (LWP 3012))
Thanks!
Thanks for the followup. This is a duplicate of bug 91588.
*** This bug has been marked as a duplicate of 91588 ***