GNOME Bugzilla – Bug 166799
nautilus crash while copying amounts of files from sftp mount
Last modified: 2005-03-01 00:44:23 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.8.1 2.8.1 Gnome-Distributor: Ubuntu Synopsis: nautilus crashes when copying large amount of files from sftp server Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Nautilus freezes when copying several carpets (for example a jdk1.5 + tomcat 1.4 folder) from a remote host to a local drive. Steps to reproduce the crash: 1. Connect to sftp server by typing address in url entry. 2. Select the two folders 3. Drag and drop to a local foldes 4. Eventually, nautilus crashes Expected Results: Correct copy How often does this happen? Several times on a stock ubuntu + updates system (installed today on brand new pc) Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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)...[Thread debugging using libthread_db enabled] [New Thread 1089446208 (LWP 19763)] [New Thread 1102318512 (LWP 20651)] [Thread debugging using libthread_db enabled] [New Thread 1089446208 (LWP 19763)] [New Thread 1102318512 (LWP 20651)] (no debugging symbols found)...[New Thread 1095850928 (LWP 19778)] (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1089446208 (LWP 19763)] [New Thread 1102318512 (LWP 20651)] [New Thread 1095584688 (LWP 19777)] (no debugging symbols found)...[New Thread 1095318448 (LWP 19776)] (no debugging symbols found)...[New Thread 1095052208 (LWP 19775)] (no debugging symbols found)...[New Thread 1094785968 (LWP 19774)] (no debugging symbols found)...[New Thread 1094478768 (LWP 19771)] (no debugging symbols found)...[New Thread 1094212528 (LWP 19770)] (no debugging symbols found)...[New Thread 1093802928 (LWP 19764)] (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)...(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)...0xffffe410 in __kernel_vsyscall ()
+ Trace 55505
Thread 10 (Thread 1093802928 (LWP 19764))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-09 10:10 ------- Unknown version 2.8.1 in product nautilus. Setting version to "2.8.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was rapto@arrakis.es. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.8.2 2.8.2 Gnome-Distributor: Debian I can confirm this behaviour and it does not seem to depend on the number of files transfered. I have to move entire directory trees to trigger the fault. Copy the platform, mono or Desktop folders of garnome 2.9.91.1 to your local machine. It is 100% reproducable for me. The error message is "The application nautilus has terminated unexpectedly. You can inform the developers..." so this exception is obviously not caught. I have not been able to quickly produce a nautilus stack trace as I do not know how to do that :)
I have also observed this bug with the version of GNOME 2.8 shipped with Fedora 3. In my case it transferred around 1200 files before crashing, and would do it repeatedly each time I tried to transfer the files.
Supplemental: nautilus 2.8.2-2 nautilus-data 2.8.2-2 libgnome-vfsmm-2 2.8.0-2 libgnomevfs2-0 2.8.3-11 libgnomevfs2-common 2.8.3-11 Dave what are your versions?
Christian, These are the versions of nautilus and gnome-vfs packages. They are obtained from "rpm -qa" on an up-to-date Fedora 3 system: nautilus-2.8.1-4 nautilus-media-0.8.1-3 gnome-vfs2-smb-2.8.2-8 gnome-vfs2-2.8.2-8 gnome-vfs2-devel-2.8.2-8 Looks like my Nautilus and Gnome VFS versions are a point release behind yours. I don't have nautilus-data, it must be packaged differently by Fedora. Dave
Last thread's stack trace is equal to the last one in Bug 166309 but the other one is not; duplicate? Anyway reproducable in Gnome 2.8 series
*** Bug 166309 has been marked as a duplicate of this bug. ***
Thanks Christian - I had a look into it and it turned out to be a dup of bug 153679. *** This bug has been marked as a duplicate of 153679 ***