GNOME Bugzilla – Bug 126755
crash when try to delete
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: normal Version: 2.2.4 Synopsis: crash when try to delete Bugzilla-Product: nautilus Bugzilla-Component: File and Folder Operations BugBuddy-GnomeVersion: 2.0 (2.2.2) Description: Description of Problem: crash appears when try to delete a file or directory with a same named file in the trash Steps to reproduce the problem: 1. create a file toto 2. delete toto (now it is in trash) 3. re-create a file toto 4. try to delete the new toto => crash 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)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 2325)] [New Thread 32769 (LWP 2326)] [New Thread 16386 (LWP 2327)] [New Thread 32771 (LWP 2328)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40a06ab6 in waitpid () from /lib/libpthread.so.0
+ Trace 41660
Thread 4 (Thread 32771 (LWP 2328))
Thread 3 (Thread 16386 (LWP 2327))
Thread 1 (Thread 16384 (LWP 2325))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-11 15:46 ------- Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
unnable to reproduce bug under Fedora Core 1 (nautilus 2.4.0)
*** Bug 126754 has been marked as a duplicate of this bug. ***
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 126042 ***