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 746184 - Nautilus stuck due to tracker-store
Nautilus stuck due to tracker-store
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: general
3.15.x
Other Linux
: Normal critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 746176 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-03-13 21:39 UTC by Mikhail
Modified: 2021-06-18 15:29 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mikhail 2015-03-13 21:39:30 UTC
[mikhail@localhost ~]$ gdb nautilus
GNU gdb (GDB) Fedora 7.9-10.fc22
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from nautilus...Reading symbols from /usr/lib/debug/usr/bin/nautilus.debug...done.
done.
(gdb) r
Starting program: /usr/bin/nautilus 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libstdc++.so.6.0.21-gdb.py", line 58, in <module>
    import libstdcxx.v6
  File "/lib64/../share/gcc-5.0.0/python/libstdcxx/v6/__init__.py", line 19, in <module>
    from printers import register_libstdcxx_printers
ImportError: No module named 'printers'
[New Thread 0x7fffe2425700 (LWP 3833)]
[New Thread 0x7fffe2c26700 (LWP 3832)]
** Message: Init Stock Icons
[Thread 0x7fffe2425700 (LWP 3833) exited]

(nautilus:3823): Gtk-CRITICAL **: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed

(nautilus:3823): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(nautilus:3823): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(nautilus:3823): Gtk-CRITICAL **: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed
^C[New Thread 0x7fffd0774700 (LWP 3835)]
[New Thread 0x7fffe0b07700 (LWP 3834)]

Program received signal SIGINT, Interrupt.
0x00007ffff382f66d in poll () at ../sysdeps/unix/syscall-template.S:81
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
(gdb) thread apply all bt

Thread 1 (Thread 0x7ffff7fb2a00 (LWP 3823))

  • #0 poll
    at ../sysdeps/unix/syscall-template.S line 81
  • #1 g_main_context_poll
    at gmain.c line 4103
  • #2 g_main_context_iterate
    at gmain.c line 3803
  • #3 g_main_loop_run
    at gmain.c line 4002
  • #4 g_dbus_connection_send_message_with_reply_sync
    at gdbusconnection.c line 2255
  • #5 tracker_sparql_backend_construct
    at /home/carlos/Source/gnome/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 43
  • #6 tracker_sparql_backend_new
    at /home/carlos/Source/gnome/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 31
  • #7 tracker_sparql_backend_get
    at /home/carlos/Source/gnome/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 244
  • #8 tracker_sparql_backend_get_internal
    at /home/carlos/Source/gnome/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 262
  • #9 tracker_sparql_connection_get
    at /home/carlos/Source/gnome/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 402
  • #10 nautilus_search_engine_tracker_init
    at nautilus-search-engine-tracker.c line 362
  • #11 g_type_create_instance
    at gtype.c line 1870
  • #12 g_object_new_internal
    at gobject.c line 1774
  • #13 g_object_newv
    at gobject.c line 1922
  • #14 g_object_new
    at gobject.c line 1614
  • #15 nautilus_search_engine_tracker_new
    at nautilus-search-engine-tracker.c line 374
  • #16 nautilus_search_engine_init
    at nautilus-search-engine.c line 290
  • #17 g_type_create_instance
    at gtype.c line 1870
  • #18 g_object_new_internal
    at gobject.c line 1774
  • #19 g_object_newv
    at gobject.c line 1922
  • #20 g_object_new
    at gobject.c line 1614
  • #21 nautilus_search_engine_new
    at nautilus-search-engine.c line 305
  • #22 execute_search
    at nautilus-shell-search-provider.c line 412
  • #23 handle_get_initial_result_set
    at nautilus-shell-search-provider.c line 447
  • #24 ffi_call_unix64
    at ../src/x86/unix64.S line 76
  • #25 ffi_call
    at ../src/x86/ffi64.c line 525
  • #26 g_cclosure_marshal_generic
    at gclosure.c line 1448
  • #27 g_closure_invoke
    at gclosure.c line 768
  • #28 signal_emit_unlocked_R
    at gsignal.c line 3549
  • #29 g_signal_emitv
    at gsignal.c line 3044
  • #30 _nautilus_shell_search_provider2_skeleton_handle_method_call
    at nautilus-shell-search-provider-generated.c line 1669
  • #31 g_dbus_interface_method_dispatch_helper
    at gdbusinterfaceskeleton.c line 609
  • #32 skeleton_intercept_handle_method_call
    at gdbusinterfaceskeleton.c line 650
  • #33 call_in_idle_cb
    at gdbusconnection.c line 4884
  • #34 g_main_dispatch
    at gmain.c line 3122
  • #35 g_main_context_dispatch
    at gmain.c line 3737
  • #36 g_main_context_iterate
    at gmain.c line 3808
  • #37 g_main_context_iteration
    at gmain.c line 3869
  • #38 g_application_run
    at gapplication.c line 2308
  • #39 main
    at nautilus-main.c line 103
(gdb) 
(gdb) q
A debugging session is active.

	Inferior 1 [process 3823] will be killed.

Quit anyway? (y or n) y
[mikhail@localhost ~]$ 


$ nautilus --version
GNOME nautilus 3.15.91
Comment 1 Matthias Clasen 2015-03-13 21:49:46 UTC
without any more details, we won't be able to do much with this report. What were you doing when this happened ?
Comment 2 Matthias Clasen 2015-03-13 21:50:09 UTC
*** Bug 746176 has been marked as a duplicate of this bug. ***
Comment 3 Mikhail 2015-03-13 21:52:01 UTC
nothing, just run nautilus into gdb and see how it stuck again and again
Comment 4 André Klapper 2015-03-14 12:38:37 UTC
Mikhail: So you start nautilus and do absolutely nothing and this just happens?
Comment 5 Mikhail 2015-03-15 11:50:25 UTC
(In reply to André Klapper from comment #4)
> Mikhail: So you start nautilus and do absolutely nothing and this just
> happens?

Yes, just run it immediately after system start and not see gui.


Same issue happens with gnome-boxes:
https://bugzilla.gnome.org/show_bug.cgi?id=746241

maybe this is same problem
Comment 6 Mikhail 2015-06-15 21:28:01 UTC
again stuck nautilus gui, when I try search use filter in folder with a lot of files:


(gdb) thread apply all bt

Thread 1 (Thread 0x7f251651ba00 (LWP 2731))

  • #0 poll
    at ../sysdeps/unix/syscall-template.S line 81
  • #1 g_main_context_poll
    at gmain.c line 4103
  • #2 g_main_context_iterate
    at gmain.c line 3803
  • #3 g_main_loop_run
    at gmain.c line 4002
  • #4 g_dbus_connection_send_message_with_reply_sync
    at gdbusconnection.c line 2255
  • #5 tracker_sparql_backend_construct
    at /home/carlos/Source/gnome/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 43
  • #6 tracker_sparql_backend_new
    at /home/carlos/Source/gnome/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 31
  • #7 tracker_sparql_backend_get
    at /home/carlos/Source/gnome/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 244
  • #8 tracker_sparql_backend_get_internal
    at /home/carlos/Source/gnome/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 262
  • #9 tracker_sparql_connection_get
    at /home/carlos/Source/gnome/tracker/src/libtracker-sparql-backend/tracker-backend.vala line 402
  • #10 nautilus_search_engine_tracker_init
    at nautilus-search-engine-tracker.c line 362
  • #11 g_type_create_instance
    at gtype.c line 1870
  • #12 g_object_new_internal
    at gobject.c line 1774
  • #13 g_object_newv
    at gobject.c line 1921
  • #14 g_object_new
    at gobject.c line 1614
  • #15 nautilus_search_engine_tracker_new
    at nautilus-search-engine-tracker.c line 374
  • #16 nautilus_search_engine_init
    at nautilus-search-engine.c line 290
  • #17 g_type_create_instance
    at gtype.c line 1870
  • #18 g_object_new_internal
    at gobject.c line 1774
  • #19 g_object_newv
    at gobject.c line 1921
  • #20 g_object_new
    at gobject.c line 1614
  • #21 nautilus_search_engine_new
    at nautilus-search-engine.c line 305
  • #22 nautilus_search_directory_init
    at nautilus-search-directory.c line 767
  • #23 g_type_create_instance
    at gtype.c line 1870
  • #24 g_object_new_internal
    at gobject.c line 1774
  • #25 g_object_new_valist
    at gobject.c line 2033
  • #26 g_object_new
    at gobject.c line 1617
  • #27 nautilus_directory_new
    at nautilus-directory.c line 562
  • #28 nautilus_directory_get_internal
    at nautilus-directory.c line 385
  • #29 create_new_search
    at nautilus-window-slot.c line 237
  • #30 query_editor_changed_callback
    at nautilus-window-slot.c line 283
  • #31 ffi_call_unix64
    at ../src/x86/unix64.S line 76
  • #32 ffi_call
    at ../src/x86/ffi64.c line 525
  • #33 g_cclosure_marshal_generic
    at gclosure.c line 1448
  • #34 g_closure_invoke
    at gclosure.c line 768
  • #35 signal_emit_unlocked_R
    at gsignal.c line 3549
  • #36 g_signal_emit_valist
    at gsignal.c line 3305
  • #37 g_signal_emit
    at gsignal.c line 3361
  • #38 nautilus_query_editor_changed_force
    at nautilus-query-editor.c line 995
  • #39 _g_closure_invoke_va
    at gclosure.c line 831
  • #40 g_signal_emit_valist
    at gsignal.c line 3214
  • #41 g_signal_emit
    at gsignal.c line 3361
  • #42 gtk_search_entry_changed_timeout_cb
    at gtksearchentry.c line 293
  • #43 g_timeout_dispatch
    at gmain.c line 4545
  • #44 g_main_dispatch
    at gmain.c line 3122
  • #45 g_main_context_dispatch
    at gmain.c line 3737
  • #46 g_main_context_iterate
    at gmain.c line 3808
  • #47 g_main_context_iteration
    at gmain.c line 3869
  • #48 g_application_run
    at gapplication.c line 2308
  • #49 main
    at nautilus-main.c line 103
(gdb) 
(gdb) 
(gdb)
Comment 7 Mikhail 2015-06-15 21:32:06 UTC
below trace of /usr/libexec/tracker-store process which begins in same time consume 100% CPU



(gdb) thread apply all bt

Thread 7 (Thread 0x7efbf9323700 (LWP 2209))

  • #0 syscall
    at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
  • #1 g_mutex_lock_slowpath
    at gthread-posix.c line 1313
  • #2 g_mutex_lock
    at gthread-posix.c line 1337
  • #3 g_object_notify_queue_freeze
    at gobject.c line 225
  • #4 g_object_init
    at gobject.c line 968
  • #5 g_type_create_instance
    at gtype.c line 1864
  • #6 g_object_new_internal
    at gobject.c line 1774
  • #7 g_object_newv
    at gobject.c line 1921
  • #8 g_object_new
    at gobject.c line 1614
  • #9 g_dbus_message_new
    at gdbusmessage.c line 578
  • #10 g_dbus_message_new_from_blob
    at gdbusmessage.c line 2030
  • #11 _g_dbus_worker_do_read_cb
    at gdbusprivate.c line 751
  • #12 g_simple_async_result_complete
    at gsimpleasyncresult.c line 763
  • #13 complete_in_idle_cb
    at gsimpleasyncresult.c line 775
  • #14 g_main_dispatch
    at gmain.c line 3122
  • #15 g_main_context_dispatch
    at gmain.c line 3737
  • #16 g_main_context_iterate
    at gmain.c line 3808
  • #17 g_main_loop_run
    at gmain.c line 4002
  • #18 gdbus_shared_thread_func
    at gdbusprivate.c line 274
  • #19 g_thread_proxy
    at gthread.c line 764
  • #20 start_thread
    at pthread_create.c line 333
  • #21 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 109

Thread 6 (Thread 0x7efbf8b22700 (LWP 2213))

  • #0 syscall
    at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
  • #1 g_cond_wait
    at gthread-posix.c line 1395
  • #2 g_async_queue_pop_intern_unlocked
    at gasyncqueue.c line 419
  • #3 g_async_queue_pop_unlocked
    at gasyncqueue.c line 475
  • #4 g_thread_pool_wait_for_new_task
    at gthreadpool.c line 245
  • #5 g_thread_pool_thread_proxy
    at gthreadpool.c line 296
  • #6 g_thread_proxy
    at gthread.c line 764
  • #7 start_thread
    at pthread_create.c line 333
  • #8 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 109

Thread 5 (Thread 0x7efbf3fff700 (LWP 2214))

  • #0 syscall
    at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
  • #1 g_cond_wait
    at gthread-posix.c line 1395
  • #2 g_async_queue_pop_intern_unlocked
    at gasyncqueue.c line 419
  • #3 g_async_queue_pop_unlocked
    at gasyncqueue.c line 475
  • #4 g_thread_pool_wait_for_new_task
    at gthreadpool.c line 245
  • #5 g_thread_pool_thread_proxy
    at gthreadpool.c line 296
  • #6 g_thread_proxy
    at gthread.c line 764
  • #7 start_thread
    at pthread_create.c line 333
  • #8 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 109

Thread 4 (Thread 0x7efbf37fe700 (LWP 2215))

  • #0 syscall
    at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
  • #1 g_cond_wait
    at gthread-posix.c line 1395
  • #2 g_async_queue_pop_intern_unlocked
    at gasyncqueue.c line 419
  • #3 g_async_queue_pop_unlocked
    at gasyncqueue.c line 475
  • #4 g_thread_pool_wait_for_new_task
    at gthreadpool.c line 245
  • #5 g_thread_pool_thread_proxy
    at gthreadpool.c line 296
  • #6 g_thread_proxy
    at gthread.c line 764
  • #7 start_thread
    at pthread_create.c line 333
  • #8 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 109

Thread 3 (Thread 0x7efbf2ffd700 (LWP 2216))

  • #0 syscall
    at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
  • #1 g_cond_wait
    at gthread-posix.c line 1395
  • #2 g_async_queue_pop_intern_unlocked
    at gasyncqueue.c line 419
  • #3 g_async_queue_pop_unlocked
    at gasyncqueue.c line 475
  • #4 g_thread_pool_wait_for_new_task
    at gthreadpool.c line 245
  • #5 g_thread_pool_thread_proxy
    at gthreadpool.c line 296
  • #6 g_thread_proxy
    at gthread.c line 764
  • #7 start_thread
    at pthread_create.c line 333
  • #8 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 109

Thread 1 (Thread 0x7efc059d3880 (LWP 2196))

  • #0 g_slist_find
    at gslist.c line 712
  • #1 g_object_notify_queue_add
    at gobject.c line 303
  • #2 g_object_notify_by_spec_internal
    at gobject.c line 1144
  • #3 g_object_notify
    at gobject.c line 1197
  • #4 object_set_property
    at gobject.c line 1415
  • #5 g_object_new_internal
    at gobject.c line 1808
  • #6 g_object_new_valist
    at gobject.c line 2033
  • #7 g_object_new
    at gobject.c line 1617
  • #8 g_data_input_stream_new
    at gdatainputstream.c line 188
  • #9 tracker_steroids_update_array_co
    at /home/carlos/Source/gnome/tracker/src/tracker-store/tracker-steroids.vala line 162
  • #10 tracker_steroids_update_array
  • #11 _dbus_tracker_steroids_update_array
    at tracker-steroids.c line 3922
  • #12 tracker_steroids_dbus_interface_method_call
    at tracker-steroids.c line 3972
  • #13 call_in_idle_cb
    at gdbusconnection.c line 4884
  • #14 g_main_dispatch
    at gmain.c line 3122
  • #15 g_main_context_dispatch
    at gmain.c line 3737
  • #16 g_main_context_iterate
    at gmain.c line 3808
  • #17 g_main_loop_run
    at gmain.c line 4002
  • #18 tracker_main_main
    at /home/carlos/Source/gnome/tracker/src/tracker-store/tracker-main.vala line 298
  • #19 main
    at /home/carlos/Source/gnome/tracker/src/tracker-store/tracker-main.vala line 150
(gdb) 
(gdb) 
(gdb) 
(gdb) q
Comment 8 Mikhail 2015-06-15 21:42:00 UTC
Yes, tracker-store is culprit here. After killing tracker-store process, nautilus begins respond again.
Comment 9 André Klapper 2021-06-18 15:29:46 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.