GNOME Bugzilla – Bug 135063
Crash after home dir window opened
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Red Hat Linux release 9 (Shrike) Package: nautilus Severity: normal Version: GNOME2.5.4 2.5.7 Gnome-Distributor: GNOME.Org Synopsis: Crash after home dir window opened Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.5.7 BugBuddy-GnomeVersion: 2.0 (2.5.3) Description: I clicked on a launcher that opens my home dir, and the window opened, then Nautilus crashed. I've never seen this problem before. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (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)...[New Thread 1090352736 (LWP 5660)] [New Thread 1102101424 (LWP 5661)] (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)... 0x40000c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 44440
Thread 1 (Thread 1090352736 (LWP 5660))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-02-21 14:43 ------- Unknown version 2.5.7 in product nautilus. Setting version to the default, "unspecified". Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Reproducibility: Every time.
simple dup finder says this is a unique stack trace. adding keywords GNOMEVER2.5, STACKTRACE, bugsquad. Priority->High, Severity->Critical. Maybe an ORBit bug?
The funny thing is that Nautilus doesn't actually close down and restart after the crash, the home dir window just stays there and is actually still usable. Closing it and reopening the home dir causes the crash again.
Maybe a fork:ed process from nautilus is whats really crashing.
This is a dup of bug 133808.
*** This bug has been marked as a duplicate of 133808 ***