GNOME Bugzilla – Bug 325028
Crash on copy from remote source. (Nautilus)
Last modified: 2006-01-03 14:27:15 UTC
Distribution: Ubuntu 5.10 (breezy) Package: nautilus Severity: Normal Version: GNOME2.12.1 2.12.1 Gnome-Distributor: Ubuntu Synopsis: Crash on copy from remote source. Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.12.1 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Nautilus crashes a third of the way through the transfer of a folder from a remote source. Steps to reproduce the crash: 1. Download john from http://www.openwall.com/john/c/john-1.6.tar.gz and unpack the folder. 2. Copy the "src" folder of the unpacked directory john-1.6/ from a remote location to your Desktop. Expected Results: Nautilus should crash when attempting to copy "Makefile.dep". Removing this file from the folder does not fix the problem. How often does this happen? Always. Additional Information: None. 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 -1226332480 (LWP 8386)] [New Thread -1235670096 (LWP 8420)] [New Thread -1235403856 (LWP 8419)] [New Thread -1234744400 (LWP 8418)] [New Thread -1227908176 (LWP 8399)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 64815
Thread 2 (Thread -1235670096 (LWP 8420))
------- Bug created by bug-buddy at 2005-12-27 00:08 ------- Unknown version 2.12.1 in product nautilus. Setting version to "2.12.x".
Thanks for your bug. That works fine on my dapper box with sftp. What protocol do you use? Could you get a backtrace with libglib2.0-0-dbg and a debug package of libgnomevfs2-common (https://wiki.ubuntu.com/DebuggingProgramCrash) installed?
I downloaded and installed the two packages you mentioned, but I have been having trouble setting this LD_LIBRARY_PATH variable and using it correctly. Google and UbuntuForums.org searches have yielded little help. Could you explain in a bit of detail how this should be done? Also, the protocol I have been using for the transfer is SSH. The remote source from which I am attempting the download also runs Linux, but I do not know what version.
no need to use LD_LIBRARY_PATH, gdb has some magic to get that alone. Just click on the bug-buddy dialog to send the bug upstream and copy the backtrace from it
Created attachment 56476 [details] New backtrace for Nautilus crash. Here is a new backtrace for the crash. Is this what you expected? The two packages you mentioned are installed, but apart from that I have done nothing other than run Nautilus again and copy the backtrace upon its crash. Please forgive me if I have still not provided useful information.
Thank you for the comment but the backtrace is pretty short, could you try with gdb instead of bug-buddy as described by https://wiki.ubuntu.com/DebuggingProgramCrash (no need to build debug packages, just read the gdb explanations for it)
Created attachment 56607 [details] Proper gdb backtrace. So I started the preconfigured Nautilus "connect to server" session that has been causing all this trouble, and then attached gdb to it. The program crashed as expected, and gdb then produced this backtrace. I hope this one is more useful than the other two!
According to the backtrace duplicate of #153679 *** This bug has been marked as a duplicate of 153679 ***