GNOME Bugzilla – Bug 302402
Crash when remotely copying directory containing symlink
Last modified: 2005-09-01 21:22:43 UTC
Distribution: Debian 3.1 Package: nautilus Severity: normal Version: GNOME2.10.0 2.10.0 Gnome-Distributor: Ubuntu Synopsis: Crash when remotely copying directory containing symlink Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.10.0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: When I access a remote server in Nautilus, and try to copy a directory from that server to local filesystem, and this directory happens to contain a symlink to some other file/directory on the remote server (outside the directory to be copied) nautilus crashes. Steps to reproduce the crash: 1. on remote system create a dir with a symlink to a file outside that dir 2. from local system start nautilus and connect to remote server 3. copy dir from step 1 by drag-and-drop to the local filesystem Expected Results: dir should be copied, symlinks should be copied as is, possibly being broken links on the local filesystem How often does this happen? every time steps 1,2,3 are performed 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) `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) [Thread debugging using libthread_db enabled] [New Thread -1223928576 (LWP 17256)] [New Thread -1237587024 (LWP 17283)] [New Thread -1237320784 (LWP 17282)] [New Thread -1235731536 (LWP 17268)] [New Thread -1235465296 (LWP 17267)] [New Thread -1224389712 (LWP 17257)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 58886
Thread 6 (Thread -1224389712 (LWP 17257))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-29 08:57 ------- Unknown version 2.10.0 in product nautilus. Setting version to "2.10.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' 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.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Sure, here's what I get now: Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] [New Thread -1223928576 (LWP 17593)] [New Thread -1224389712 (LWP 17598)] [New Thread -1234801744 (LWP 17606)] [New Thread -1235850320 (LWP 17620)] [New Thread -1236116560 (LWP 17621)] (nautilus:17593): Gtk-CRITICAL **: gtk_window_realize_icon: assertion `info->icon_pixmap == NULL' failed gnome-vfs-modules-ERROR **: file file-method.c: line 1924 (do_create_symbolic_link): assertion failed: (target_reference != NULL) aborting... Program received signal SIGABRT, Aborted. [Switching to Thread -1235850320 (LWP 17620)] 0xffffe410 in __kernel_vsyscall ()
I see this too. The directory I'm copying over a ssh connection contains a lot of dangling symlinks. Backtrace: gnome-vfs-modules-ERROR **: file file-method.c: line 2108 (do_create_symbolic_link): assertion failed: (target_reference != NULL) aborting... Program received signal SIGABRT, Aborted.
+ Trace 62598
Thread NaN (LWP 9961)
the sftp issue is gnome-vfs bug #153679
see last comment - this is a known problem :( *** This bug has been marked as a duplicate of 153679 ***