Bug 752536 – nautilus hanged when accessing an SMB share

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 752536 - nautilus hanged when accessing an SMB share


Summary:	nautilus hanged when accessing an SMB share


Status:	RESOLVED OBSOLETE

Product:	nautilus
Classification:	Core
Component:	general
Version:	3.20.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2015-07-17 15:38 UTC by Bastien Nocera
Modified:	2021-06-18 15:33 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Bastien Nocera 2015-07-17 15:38:23 UTC

I couldn't get a more accurate trace, and have since upgraded nautilus to the next minor version with mtime sorting...

+ Trace 235279

#0 syscall
at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
#1 g_mutex_lock_slowpath
#2 g_dbus_connection_signal_subscribe
#3 async_initable_init_first
#4 async_initable_init_async
#5 g_async_initable_new_valist_async
#6 g_async_initable_new_async
#7 gvfs_dbus_daemon_proxy_new
#8 async_call_cancelled_cb
#9 g_closure_invoke
#10 signal_emit_unlocked_R
#11 g_signal_emit_valist
#12 g_signal_emit
#13 g_cancellable_cancel
#14 file_info_cancel
#15 nautilus_directory_async_state_changed
#16 dequeue_pending_idle_callback
#17 directory_load_done
#18 more_files_callback
#19 next_async_callback_wrapper
#20 g_simple_async_result_complete
#21 complete_in_idle_cb
#22 g_main_context_dispatch
#23 g_main_context_iterate.isra
#24 g_main_context_iteration
#25 g_application_run
#26 main

Comment 1 Bastien Nocera 2015-07-18 13:43:21 UTC

I was loading a directory (full of files) in the only tab, pressed "Ctrl+T" to start a new tab (which would have been loading the same directory from the SMB share) and then clicked on "Downloads". Looks like it hung try to start a gvfs daemon while it was cancelling the loading of the SMB share in that second tab.

Comment 2 Bastien Nocera 2016-04-09 13:38:02 UTC

I regularly see this in 3.20 as well:

+ Trace 236170

Thread 1 (Thread 0x7f0457e55a80 (LWP 6813))

#0 syscall
#1 g_mutex_lock_slowpath
#2 g_dbus_connection_signal_subscribe
#3 async_initable_init_first
#4 async_initable_init_async
#5 g_async_initable_new_valist_async
#6 g_async_initable_new_async
#7 gvfs_dbus_daemon_proxy_new
#8 async_call_cancelled_cb
#9 g_closure_invoke
#10 signal_emit_unlocked_R
#11 g_signal_emit_valist
#12 g_signal_emit
#13 g_cancellable_cancel
#14 update_places
#15 update_hostname
#16 hostname_proxy_new_cb
#17 g_task_return_now
#18 g_task_return
#19 init_second_async_cb
#20 g_task_return_now
#21 g_task_return
#22 async_init_get_all_cb
#23 g_task_return_now
#24 g_task_return
#25 g_dbus_connection_call_done
#26 g_task_return_now
#27 complete_in_idle_cb
#28 g_main_context_dispatch
#29 g_main_context_iterate.isra
#30 g_main_context_iteration
#31 g_application_run
#32 main

Comment 3 Bastien Nocera 2016-04-09 13:39:07 UTC

Might be bug 747419.

Comment 4 André Klapper 2021-06-18 15:33:33 UTC

GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version of Files (nautilus), then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/nautilus/-/issues/

Thank you for your understanding and your help.