Nautilus move to trash very slow if mountpoints inaccessible

Bug #113072 reported by Philip Aston
2
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
Medium
nautilus (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

I have a number of smbfs mount points to a local server. When I start my VPN, these are not available, and all "move to trash" operations in Nautilus become unbearably slow. (The files I'm trashing are unrelated to the smbfs mounts). Other Nautilus operations are fine.

Example back trace showing "move to trash" trying to access mount points.

#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb737dad3 in __lxstat64 () from /lib/tls/i686/cmov/libc.so.6
#2 0xb65b22e7 in get_stat_info (file_info=0x88c3d58,
    full_name=0x88b7fc8 "/mnt/myserver/music",
    options=GNOME_VFS_FILE_INFO_DEFAULT, statptr=0xbf8f69cc)
    at /usr/include/sys/stat.h:443
#3 0xb65b2649 in do_get_file_info (method=0xb65b8840, uri=0x88361f0,
    file_info=0x88c3d58, options=GNOME_VFS_FILE_INFO_DEFAULT, context=0x0)
    at file-method.c:1174
#4 0xb76e232a in gnome_vfs_get_file_info_uri_cancellable (uri=0x88361f0,
    info=0x88c3d58, options=GNOME_VFS_FILE_INFO_DEFAULT, context=0x0)
    at gnome-vfs-cancellable-ops.c:202
#5 0xb76f5a43 in gnome_vfs_get_file_info_uri (uri=0x88361f0, info=0x88c3d58,
    options=GNOME_VFS_FILE_INFO_DEFAULT) at gnome-vfs-ops.c:332
#6 0xb76fc273 in _gnome_vfs_uri_resolve_all_symlinks_uri (uri=0x88b4158,
    result_uri=0xbf8f6b08) at gnome-vfs-utils.c:1972
#7 0xb76e2813 in gnome_vfs_find_directory_cancellable (near_uri=0x88b4158,
    kind=GNOME_VFS_DIRECTORY_KIND_TRASH, result_uri=0xbf8f6b70,
    create_if_needed=0, find_if_needed=0, permissions=63, context=0x0)
    at gnome-vfs-cancellable-ops.c:326
#8 0xb76e7bb8 in gnome_vfs_find_directory (near_uri=0x88b4158,
    kind=GNOME_VFS_DIRECTORY_KIND_TRASH, result=0xbf8f6b70,
    create_if_needed=0, find_if_needed=0, permissions=63)
    at gnome-vfs-find-directory.c:63
#9 0x0813ba12 in check_trash_directory_added_callback (monitor=0x83f04c8,
    volume=0x889c7d0, trash=0x81f5120) at nautilus-trash-directory.c:186
#10 0xb7606f99 in IA__g_cclosure_marshal_VOID__POINTER (closure=0x83e0890,
    return_value=0x0, n_param_values=2, param_values=0xbf8f6dcc,
    invocation_hint=0xbf8f6cdc, marshal_data=0x813b9a0) at gmarshal.c:601
#11 0xb75fa62b in IA__g_closure_invoke (closure=0x83e0890, return_value=0x0,
    n_param_values=2, param_values=0xbf8f6dcc, invocation_hint=0xbf8f6cdc)
    at gclosure.c:490
#12 0xb760b103 in signal_emit_unlocked_R (node=0x83e0728, detail=0,
    instance=0x83f04c8, emission_return=0x0, instance_and_params=0xbf8f6dcc)
    at gsignal.c:2440
#13 0xb760c627 in IA__g_signal_emit_valist (instance=0x83f04c8, signal_id=288,
    detail=0, var_args=0xbf8f7010 "") at gsignal.c:2199
#14 0xb760c7e9 in IA__g_signal_emit (instance=0x83f04c8, signal_id=288,
    detail=0) at gsignal.c:2243
#15 0x0813db95 in nautilus_trash_monitor_add_new_trash_directories ()
    at nautilus-trash-monitor.c:268
#16 0x0810d134 in nautilus_file_operations_copy_move (item_uris=0x8871860,
    relative_item_points=0x0, target_dir=0x815bbd7 "trash:",
    copy_action=GDK_ACTION_MOVE, parent_view=0x844a018,
    done_callback=0x80bb220 <copy_move_done_callback>,
    done_callback_data=0x88e0950) at nautilus-file-operations.c:2064
#17 0x080be24d in trash_or_delete_files_common (view=0x844a018,
    file_uris=<value optimized out>, relative_item_points=0x0,
    delete_if_all_already_in_trash=1) at fm-directory-view.c:3956
#18 0x080bf56c in trash_or_delete_files (view=0x844a018,
    files=<value optimized out>) at fm-directory-view.c:3990
#19 0x080bfbfc in trash_or_delete_selected_files (view=0x844a018)
    at fm-directory-view.c:938
#20 0x080bfc6e in real_trash (view=0x844a018) at fm-directory-view.c:947
#21 0xb7f15486 in eel_marshal_BOOLEAN__VOID () from /usr/lib/libeel-2.so.2
#22 0xb75f8e49 in g_type_class_meta_marshal (closure=0x844a018,
    return_value=0xbf8f7320, n_param_values=1, param_values=0x80bfc60,
    invocation_hint=0xbf8f730c, marshal_data=0x274) at gclosure.c:567
#23 0xb75fa62b in IA__g_closure_invoke (closure=0x83f4300,
...

Revision history for this message
Philip Aston (philipa) wrote :

Potentially a duplicate of bug #81348.

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

Thank you for your bug. Looks like an upstream bug. We don't have the ressources to work on it since that's not a current setup situation and we have lot of other bugs to work on already, maybe you could open it on bugzilla.gnome.org?

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Low
Revision history for this message
Philip Aston (philipa) wrote :

Reported to bugzilla.gnome.org as Bug 440701

Revision history for this message
Philip Aston (philipa) wrote :

Hmmm.. ignore the automatic linking in the previous comment. This is right: http://bugzilla.gnome.org/show_bug.cgi?id=440701

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

thank you for sending it upstream

Changed in nautilus:
status: Unconfirmed → Unknown
Changed in nautilus:
status: Unknown → Unconfirmed
Changed in nautilus:
status: New → Triaged
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's still an issue in hardy or intrepid?

Revision history for this message
Philip Aston (philipa) wrote :

I'd stopped using smbfs mounts, but just given this test and all seems fine in hardy.

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

closing the bug since that works correctly now

Changed in nautilus:
status: Triaged → Fix Released
Changed in nautilus:
status: New → Fix Released
Changed in nautilus:
importance: Unknown → Medium
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.