Bug 345441 – Copy-paste from SSH connection did a nautilus crash

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 345441 - Copy-paste from SSH connection did a nautilus crash


Summary:	Copy-paste from SSH connection did a nautilus crash


Status:	RESOLVED DUPLICATE of bug 338970

Product:	nautilus
Classification:	Core
Component:	Navigation
Version:	2.14.x
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-06-20 15:58 UTC by Mario Gonzalez
Modified:	2006-06-20 16:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Mario Gonzalez 2006-06-20 15:59:18 UTC

Distribution: Ubuntu 6.06 (dapper)
Package: nautilus
Severity: critical
Version: GNOME2.14.2 2.14.x
Gnome-Distributor: Ubuntu
Synopsis: Copy-paste from SSH connection did a nautilus crash
Bugzilla-Product: nautilus
Bugzilla-Component: Navigation
Bugzilla-Version: 2.14.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
I added a SSH place and I tried to do a copy-paste from SSH to my
machine and Oops! nautilus crashed.

Steps to reproduce the crash:
1. Add a Server Connection "Places -> Connect to server"
2. Find the directory I want to copy
3. Right Click on it -> Copy
4. Click in machine's windows -> Paste

Expected Results:
 The same directory in both places

How often does this happen?
First time I did that

Additional Information:
  Ubuntu Dapper


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)
[Thread debugging using libthread_db enabled]
[New Thread -1225905792 (LWP 22615)]
[New Thread -1273922640 (LWP 22668)]
[New Thread -1227396176 (LWP 22619)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 68955

Thread 2 (Thread -1273922640 (LWP 22668))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 ??
from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#11 ??
from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#12 ??
from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#13 ??
#14 ??
from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#15 ??
from /usr/lib/gnome-vfs-2.0/modules/libfile.so
#16 ??
from /usr/lib/libgnomevfs-2.so.0
#17 ??
#18 _dl_rtld_di_serinfo
from /lib/ld-linux.so.2
#19 gnome_vfs_create_symbolic_link_cancellable
from /usr/lib/libgnomevfs-2.so.0
#20 gnome_vfs_create_symbolic_link
from /usr/lib/libgnomevfs-2.so.0
#21 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#22 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#23 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#24 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#25 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#26 gnome_vfs_volume_to_corba
from /usr/lib/libgnomevfs-2.so.0
#27 gnome_vfs_job_get_count
from /usr/lib/libgnomevfs-2.so.0
#28 gnome_vfs_is_primary_thread
from /usr/lib/libgnomevfs-2.so.0
#29 g_thread_pool_free
from /usr/lib/libglib-2.0.so.0
#30 g_static_private_free
from /usr/lib/libglib-2.0.so.0
#31 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#32 clone
from /lib/tls/i686/cmov/libc.so.6





------- Bug created by bug-buddy at 2006-06-20 15:59 -------

Comment 1 Elijah Newren 2006-06-20 16:40:57 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 338970 ***