GNOME Bugzilla – Bug 96099
Nautilus crashed on Gnome2 login
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: major Version: 2.0.6 Synopsis: Nautilus crashed on Gnome2 login Bugzilla-Product: nautilus Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.0.4) Description: Description of Problem: As I logged in to Gnome2 I got a nautilus crash which didn't load the DKTop icons and gave me the message that asked me if I wanted to notify a bug report. Steps to reproduce the problem: 1. Changed the the localizations to IT_euro in .bash_profile 2. logged out and back in to gnome 2 3. Actual Results: Everything loads besides nautilus Expected Results: How often does this happen? Once for now. Additional Information: If it keeps doing it I will send another bug report. 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)...[New Thread 1024 (LWP 1573)] [New Thread 2049 (LWP 1580)] [New Thread 1026 (LWP 1581)] [New Thread 2051 (LWP 1582)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40b04609 in wait4 () from /lib/libc.so.6
+ Trace 28981
Thread 4 (Thread 2051 (LWP 1582))
Thread 3 (Thread 1026 (LWP 1581))
Thread 1 (Thread 1024 (LWP 1573))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-17 15:29 ------- The original reporter (nightnavigator@libero.it) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Bugs #96915, #97031, #97050, #97075 have different stack-traces, but all about a crash when launching nautilus. Their versions are also close to each-other.
The traceback seems to be very similar to the one in 96025.
Still seeing this, nightnavigator?
Reopening 'cause we have a dupe(s).
*** Bug 102019 has been marked as a duplicate of this bug. ***
*** Bug 102020 has been marked as a duplicate of this bug. ***
*** Bug 102195 has been marked as a duplicate of this bug. ***
*** Bug 103413 has been marked as a duplicate of this bug. ***
Since this has only reported for the 2.0.x series, I consider it fixed in later versions and marking it as such.