GNOME Bugzilla – Bug 172107
Nautilus crash
Last modified: 2005-03-30 15:49:12 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: gnome-utils Severity: normal Version: GNOME2.8.0 2.8.1 Gnome-Distributor: Red Hat, Inc Synopsis: Nautilus crash Bugzilla-Product: gnome-utils Bugzilla-Component: gdict Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Upon the start of a user account, the dailog box appears telling me I have an error, and states that "Nautilus" has quit. It, of course, gives me three options, to restart the application, close it, or to inform someone. The bug buddy indicated that there was a problem with the gdict, or something having to do with the retrieval of words. Steps to reproduce the crash: 1. Restart the computer, and log in 2. Sometimes I can attempt to restart the application 3. Expected Results: Since I have not used gdict, it is not a critical error for me. How often does this happen? This occurrs upon startup. It has not always done this, however. It seems to be coupled to another issue (As follows in the additional information) Additional Information: My name is Kory A. Cox, a student at NC State University (kacox2@ncsu.edu). I recently decided to activate the Kerberos support within the Fedora Core 3 Release I have. Nautilus did not appear to have any trouble until that moment. Alongside the activation of the kerberos support, I also seemed to lose control of my user passwords. I was still able to use the root profile, but any attempts to change the other user passwords failed, as I checked the systems logs. I switched the user /bin/bash to /bin/ash, and was able to set a password there only by using the root to disable the kerberos support. From there I was able to go back to the /bin/bash user profile. I don't know if you really needed all of this information, but it appears to have all happened in unison, and maybe the switch to /bin/ash and back may have disrupted something with Nautilus. Thank you for all your support, and for wonderful programs and products. - a happy customer- 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)...[Thread debugging using libthread_db enabled] [New Thread -1208285504 (LWP 5941)] [New Thread -1221166160 (LWP 6001)] [Thread debugging using libthread_db enabled] [New Thread -1208285504 (LWP 5941)] [New Thread -1221166160 (LWP 6001)] [Thread debugging using libthread_db enabled] [New Thread -1208285504 (LWP 5941)] [New Thread -1221166160 (LWP 6001)] [New Thread -1220899920 (LWP 6000)] [New Thread -1210410064 (LWP 5948)] (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)...0x005cf7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 57507
Thread 4 (Thread -1210410064 (LWP 5948))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-30 09:51 ------- Unknown version 2.8.1 in product gnome-utils. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-utils". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was kacox2@ncsu.edu. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 153888 ***