GNOME Bugzilla – Bug 108854
unknown nautilus crash
Last modified: 2009-08-15 18:40:50 UTC
Package: nautilus Severity: major Version: 2.2.2 Synopsis: unknown nautilus crash Bugzilla-Product: nautilus Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? Additional Information: 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)...[New Thread 16384 (LWP 608)] [New Thread 32769 (LWP 623)] [New Thread 16386 (LWP 624)] [New Thread 32771 (LWP 625)] [New Thread 49156 (LWP 626)] [New Thread 65541 (LWP 627)] [New Thread 81926 (LWP 635)] [New Thread 98311 (LWP 636)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40b4ab89 in wait4 () from /lib/libc.so.6
+ Trace 35101
Thread 8 (Thread 98311 (LWP 636))
Thread 7 (Thread 81926 (LWP 635))
Thread 6 (Thread 65541 (LWP 627))
Thread 5 (Thread 49156 (LWP 626))
Thread 4 (Thread 32771 (LWP 625))
Thread 3 (Thread 16386 (LWP 624))
Thread 1 (Thread 16384 (LWP 608))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-03-20 11:32 ------- The original reporter (grick@tiscalinet.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.
Looks like the stack trace in bug 107007, which is a bug filed against the most recent gnome-panel. If this is a duplicate, then this would have to be a gtk+ bug. Setting version->2.2.x, marking priority->high & severity->critical (it's a crasher), adding GNOMEVER2.2 and bugsquad keywords, and marking as new.
This stace trace looks completely useless for tracking down the crash. Is there any way you can figure out the steps to reproduce the crash?
I have a suspicion that this is related to bug 105745, but in any event, we need a better stack trace. [If you're using RedHat 9, you can do so with the following easy method; otherwise this will require recompiling from source: Install http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm and if the problem occurs again, submit the backtrace you get. Installing the debuginfo package will make the backtrace much more useful.] I am adding myself to the cc and marking as needinfo for now.
Oops, forgot to mark as needinfo. Doing so now.
No news in 2 months. Close?
Yeah, I think so. Owen has now marked bug 107007 as a duplicate of bug 105745 (as well as most other bugs that looked similar to 105745 that were open), so I'm pretty sure this is a dup. I'll just close it instead of reopening and duping to save on the spam, though.