GNOME Bugzilla – Bug 108800
File browser crashed
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: normal Version: 1.4.0.5 Synopsis: File browser crashed Bugzilla-Product: nautilus Bugzilla-Component: File and Folder Operations Description: File browser crashed while looking through mounted network drive. Debugging Information: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x420b4769 in wait4 () from /lib/i686/libc.so.6
+ Trace 35084
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-03-19 20:30 ------- The original reporter (james_howey@hotmail.com) 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.
This does not look like the file browser (nautilus). I don't think there was ever a 1.4.0.5 version of nautilus. Regardless, the stack trace matches the one in bug 100366, which has been marked as a duplicate of 60406. *** This bug has been marked as a duplicate of 60406 ***