crash copying directory over ssh

Bug #8205 reported by Jason Toffaletti
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
Critical
nautilus (Ubuntu)
Fix Released
Medium
Sebastien Bacher

Bug Description

I try to copy a specific directory and nautilus crashes before the copy is
complete. This crash is reproducable every time I try to copy this directory.
Here is a back trace:

Program received signal SIGABRT, Aborted.
[Switching to Thread 1100143536 (LWP 9980)]
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x40b9b4b3 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0x40ca1edc in ?? () from /lib/tls/i686/cmov/libc.so.6
#3 0x00000000 in ?? ()
#4 0x40b9cc08 in abort () from /lib/tls/i686/cmov/libc.so.6
#5 0x4192d034 in ?? ()
#6 0x00000000 in ?? ()
#7 0x00000020 in ?? ()
#8 0x00000000 in ?? ()
#9 0x00000000 in ?? ()
#10 0x00000000 in ?? ()
#11 0x00000000 in ?? ()
#12 0x00000000 in ?? ()
#13 0x00000000 in ?? ()
#14 0x00000000 in ?? ()
#15 0x00000000 in ?? ()
#16 0x00000000 in ?? ()
#17 0x00000000 in ?? ()
#18 0x00000000 in ?? ()
#19 0x00000000 in ?? ()
#20 0x00000000 in ?? ()
#21 0x00000000 in ?? ()
#22 0x00000000 in ?? ()
---Type <return> to continue, or q <return> to quit---
#23 0x00000000 in ?? ()
#24 0x00000000 in ?? ()
#25 0x00000000 in ?? ()
#26 0x00000000 in ?? ()
#27 0x00000000 in ?? ()
#28 0x00000000 in ?? ()
#29 0x00000000 in ?? ()
#30 0x00000000 in ?? ()
#31 0x00000000 in ?? ()
#32 0x00000000 in ?? ()
#33 0x00000000 in ?? ()
#34 0x00000000 in ?? ()
#35 0x00000000 in ?? ()
#36 0x00000000 in ?? ()
#37 0x00000000 in ?? ()
#38 0x00000000 in ?? ()
#39 0x41b2d260 in ?? ()
#40 0x082bf82c in ?? ()
#41 0x40a32a21 in g_free () from /usr/lib/libglib-2.0.so.0
#42 0x40a34e10 in g_log () from /usr/lib/libglib-2.0.so.0
#43 0x40f33ea4 in ?? () from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#44 0x40f34d2d in ?? () from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#45 0x00000004 in ?? ()
---Type <return> to continue, or q <return> to quit---
#46 0x40f34fc0 in ?? () from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#47 0x40f34d1f in ?? () from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#48 0x00000769 in ?? ()
#49 0x40f34eb8 in ?? () from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#50 0x40f34ed0 in ?? () from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#51 0x4000b50f in _dl_map_object_deps () from /lib/ld-linux.so.2
#52 0x40933ede in gnome_vfs_create_symbolic_link_cancellable ()
   from /usr/lib/libgnomevfs-2.so.0
#53 0x4094cb0f in gnome_vfs_create_symbolic_link ()
   from /usr/lib/libgnomevfs-2.so.0
#54 0x4095b5ce in _gnome_vfs_volume_from_corba ()
   from /usr/lib/libgnomevfs-2.so.0
#55 0x4095bb82 in _gnome_vfs_volume_from_corba ()
   from /usr/lib/libgnomevfs-2.so.0
#56 0x4095bbc2 in _gnome_vfs_volume_from_corba ()
   from /usr/lib/libgnomevfs-2.so.0
#57 0x4095bbc2 in _gnome_vfs_volume_from_corba ()
   from /usr/lib/libgnomevfs-2.so.0
#58 0x4095bf56 in _gnome_vfs_volume_from_corba ()
   from /usr/lib/libgnomevfs-2.so.0
#59 0x4095cd4f in _gnome_vfs_volume_from_corba ()
   from /usr/lib/libgnomevfs-2.so.0
#60 0x4095d492 in _gnome_vfs_xfer_private () from /usr/lib/libgnomevfs-2.so.0
---Type <return> to continue, or q <return> to quit---
#61 0x409411e7 in _gnome_vfs_job_go () from /usr/lib/libgnomevfs-2.so.0
#62 0x40941439 in _gnome_vfs_job_execute () from /usr/lib/libgnomevfs-2.so.0
#63 0x4093f008 in _gnome_vfs_job_queue_shutdown ()
   from /usr/lib/libgnomevfs-2.so.0
#64 0x409512ca in _gnome_vfs_thread_pool_init ()
   from /usr/lib/libgnomevfs-2.so.0
#65 0x40a4582f in g_static_private_free () from /usr/lib/libglib-2.0.so.0
#66 0x40415a2b in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#67 0x00000000 in ?? ()

If you need me to provide a directory listing so you can see what is actually
being copied, let me know.

http://bugzilla.gnome.org/show_bug.cgi?id=153066: http://bugzilla.gnome.org/show_bug.cgi?id=153066

Revision history for this message
Sebastien Bacher (seb128) wrote :

Ok, thanks for the bug report. I've some crashes here too with the ssh://
method, I'll bug report upstream.
BTW you can try to use sftp:// instead of ssh://, it works just fine most of the
time.

Revision history for this message
Jason Toffaletti (jason) wrote :

Oh, well sftp makes a lot more sense to me, I'll try that. I just figured ssh
was an alias for sftp because when I go to File->Connect to Server... SSH shows
up in Service Type but SFTP does not. I'd be nice if SFTP showed up there.

Revision history for this message
Jason Toffaletti (jason) wrote :

Ok, I posted too soon. Service Type SSH _is_ an alias for sftp:// when I go to
Properties for the volume it creates in Network, it shows Location:
sftp://user@domain/home

Revision history for this message
Sebastien Bacher (seb128) wrote :

I've reported the problem upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=153066

Revision history for this message
Jason Toffaletti (jason) wrote :

I haven't seen this happen in a while, can we poke upstream to find out if this
should be closed?

Revision history for this message
Sebastien Bacher (seb128) wrote :

thanks for the comment. There is some known issue upstream and the code has not
changed so the upstream bug is probably useful

Revision history for this message
Lakin Wecker (lakin) wrote :

Changing status to confirmed, as this problem exists in Ubuntu and has yet to be fixed upstream.

Changed in nautilus:
status: Unconfirmed → Confirmed
Revision history for this message
Daniel Robitaille (robitaille) wrote :

Changing the upstream link since the previous one was a duplicate

Revision history for this message
DarkMageZ (darkmagez) wrote :

this is marked as fixed upstream, has the fix been applied to dapper? i ran across this bug today.

Changed in nautilus:
status: Confirmed → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

no, that's probably not a trivial change so not something for dapper. It's fixed to edgy

Changed in nautilus:
status: Confirmed → Fix Released
Changed in nautilus:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.