GNOME Bugzilla – Bug 109917
Crash moving files from local folder to folder on NFS
Last modified: 2009-08-15 18:40:50 UTC
Package: nautilus Severity: normal Version: GNOME2.2.1 2.2.3.1 os_details: Gnome.Org Synopsis: Crash moving files from local folder to folder on NFS Bugzilla-Product: nautilus Bugzilla-Component: File and Folder Operations BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Nautilus crashed middle-click and dragging three files from a local folder to an NFS mounted folder. Steps to reproduce the problem: 1. Select multiple files from a local folder. 2. Press middle botton and hold, drag files to NFS mounted folder. 3. Crash. Sometimes this crashes nautilus, sometimes it doesn't. Debugging Information: Backtrace was generated from '/home/rodd/gnome/bin/nautilus' [New Thread 1024 (LWP 16867)] [New Thread 2049 (LWP 16868)] [New Thread 1026 (LWP 16869)] [New Thread 2051 (LWP 16870)] [New Thread 3076 (LWP 16871)] [New Thread 4101 (LWP 16872)] [New Thread 5126 (LWP 16873)] [New Thread 6151 (LWP 16874)] [New Thread 7176 (LWP 16875)] [New Thread 8201 (LWP 16876)] [New Thread 9226 (LWP 16877)] [New Thread 10251 (LWP 16878)] 0x420b48b9 in wait4 () from /lib/i686/libc.so.6
+ Trace 35555
Thread 1 (Thread 1024 (LWP 16867))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-03 20:18 ------- Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Okay, a few extra thoughts. I don't think it's ever crashed moving a single file (from a local folder to an NFS folder). Also, it seems to happen more when the files being moved already exist on the NFS folder (so they are being replaced). It always crashed before asking whether to replace the files.
The stack trace looks similar to the one in bug 113328 (which happens to be a gnome-panel crash). This also looks similar to bug 108205. Interestingly, in bug 108205, it was found that the bug was due to "a patched version of GTK+ to add pretty (albeit buggy) drop shadow eyecandy and the like" and it was found that installing a clean version of gtk+ fixed the problem.
So, do you have a patched gtk+, and does using a clean one fix this?
Please respond to the question above.
Sorry, been on holidays and just got back ;-] I'm not sure whether I had gtk+ patched (I don't think I did) but I've since cleaned my hard-drive and installed fedora-core so I'm not sure I'm going to be a lot of help with regard to testing. If you can't make anything from the backtrace then close the bug out and someone can refile it if it happens again.
Ok, as the reporter suggested I'm closing this.