GNOME Bugzilla – Bug 306634
Nautilus Crash at session opening
Last modified: 2010-07-06 21:13:08 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: nautilus Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Nautilus Crash at session opening Bugzilla-Product: nautilus Bugzilla-Component: Accessibility Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Nautilus does'nt open Steps to reproduce the crash: 1. Just at the session opening 2. 3. Expected Results: Nautilus is crashed How often does this happen? Additional Information: 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 -151144768 (LWP 2217)] [New Thread -165143632 (LWP 2221)] [Thread debugging using libthread_db enabled] [New Thread -151144768 (LWP 2217)] [New Thread -165143632 (LWP 2221)] [New Thread -164877392 (LWP 2220)] [New Thread -164611152 (LWP 2219)] [New Thread -154109008 (LWP 2218)] (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 -151144768 (LWP 2217)] [New Thread -165143632 (LWP 2221)] (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)...0x00a297a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 60607
Thread 5 (Thread -154109008 (LWP 2218))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-06 09:40 UTC ------- 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 jy.lhermitte@axrindustries.net.
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 ***
Changing component as a part of ongoing reorganisation work.