Created attachment 1924953 [details] Zip file containing all attachments Description of problem: I'm experiencing a bug with nautilus file manager and GNOME activity in Fedora Workstation after upgrading from 36 to 37. In particular, the moment I type something in the nautilus search it suddenly hangs and never responds anymore. In addition, GNOME activity stops looking for files (entries that are to be opened with nautilus) after approximately 15 seconds after logging in. At every shutdown, systemd hangs on, waiting for user job tracker-extract-3.service and user job tracker-miners-fs-3.service Launching nautilus from shell and running a search yields message ** Message: 08:15:39.744: Connecting to org.freedesktop.Tracker3.Miner.Files and then hangs forever. This prevents me to run any search on nautilus. The bug is not always reproducible, as sometimes when I boot my machine the search works as expected for a long time. This is different from the activity bug, where the bug occurred in all cases and after the first search or around 15s after login. Issuing command tracker3 status yields no output and the command never returns. After describing the problem to the IRC and telegram chat, a temporary solution has been found: running tracker3 reset --filesystem solves the issue temporarily for both nautilus and Activity, but then the issue appears again at the next boot. The above command, however, does not solve the delay in the shutdown process. I will attach 4 files in a single .zip: 1. smartphone photo of the systemd shutdown process in which tracker is causing a delay 2. system information from fpaste --printonly --sysinfo 3. Results of command journalctl -x -b 0 > log-before.txt taken before I issued command tracker3 reset --filesystem 4. Results of command journalctl -x -b 0 > log-after.txt taken after I issued command tracker3 reset --filesystem Version-Release number of selected component (if applicable): Tracker 3.4.1 How reproducible: nautilus freeze: rarely reproducible, currently unknown procedure for reproduce it activity bug: always reproducible shutdown issue: always reproducible Steps to Reproduce: 1. log in 2. wait some time, perform some file search in activity (at this point activity will stop providing entries for files) 3. shutdown (this will cause a delay of 1m30s during shutdown process) Actual results: tracker3 does not index files correctly on nautilus and GNOME activity, hangs on shutdown Expected results: tracker3 works as expected, shutdown is quick and systemd does not wait for 1m30s Additional info: If required, I will post additional system information or desired logs.
Created attachment 1925696 [details] Log containing some errors possibly related to tracker3
Hello, I have a similar issue, nautilus isn't starting since I upgraded to Fedora 37. Currently running Kernel 6.0.8-300.fc37.x86_64 First attempt to launch nautilus from the teminal gave me this before crashing: ❯ G_MESSAGES_DEBUG=all nautilus (org.gnome.Nautilus:9265): GLib-GIO-DEBUG: 13:29:19.805: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) (org.gnome.Nautilus:9265): GLib-GIO-DEBUG: 13:29:19.807: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs? (org.gnome.Nautilus:9265): Tracker-DEBUG: 13:29:19.810: Loading ontologies from database. (org.gnome.Nautilus:9265): Tracker-DEBUG: 13:29:19.811: Applying ontologies from /usr/share/nautilus/ontology to existing database (org.gnome.Nautilus:9265): Tracker-DEBUG: 13:29:19.811: Current and DB locales match: 'C' ** (org.gnome.Nautilus:9265): DEBUG: 13:29:19.812: *** Cancel Results Meta requests Failed to register: Timeout was reached Then I deleted ~/.cache/tracker3 and try again, nautilus would hang indefinitely, at a different step: ❯ G_MESSAGES_DEBUG=all nautilus (org.gnome.Nautilus:10423): GLib-GIO-DEBUG: 13:35:26.481: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) (org.gnome.Nautilus:10423): GLib-GIO-DEBUG: 13:35:26.483: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs? (org.gnome.Nautilus:10423): Tracker-DEBUG: 13:35:26.487: Loading ontologies from database. (org.gnome.Nautilus:10423): Tracker-DEBUG: 13:35:26.488: Applying ontologies from /usr/share/nautilus/ontology to existing database (org.gnome.Nautilus:10423): Tracker-DEBUG: 13:35:26.488: Current and DB locales match: 'C' (org.gnome.Nautilus:10423): GLib-GIO-DEBUG: 13:35:26.504: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.504: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.504: watch_fast: "/org/gnome/desktop/peripherals/mouse/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.504: watch_fast: "/org/gnome/desktop/sound/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.504: watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.504: watch_fast: "/org/gnome/desktop/wm/preferences/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.504: watch_fast: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.504: watch_fast: "/org/gnome/desktop/a11y/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.504: watch_fast: "/org/gnome/desktop/a11y/interface/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): GLib-GIO-DEBUG: 13:35:26.505: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.506: watch_established: "/org/gnome/desktop/interface/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.506: watch_established: "/org/gnome/desktop/peripherals/mouse/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.506: watch_established: "/org/gnome/desktop/sound/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.506: watch_established: "/org/gnome/desktop/privacy/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.506: watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.506: watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.506: watch_established: "/org/gnome/desktop/a11y/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.506: watch_established: "/org/gnome/desktop/a11y/interface/" (establishing: 1) (org.gnome.Nautilus:10423): Gtk-DEBUG: 13:35:26.507: Connecting to session manager (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.548: watch_fast: "/org/gnome/nautilus/preferences/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.548: watch_fast: "/org/gnome/nautilus/compression/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.548: watch_fast: "/org/gnome/nautilus/window-state/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.548: watch_fast: "/org/gnome/nautilus/icon-view/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.548: watch_fast: "/org/gnome/nautilus/list-view/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.548: watch_fast: "/org/gtk/settings/file-chooser/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.548: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 0) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.548: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.548: watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.549: watch_established: "/org/gnome/nautilus/preferences/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.549: watch_established: "/org/gnome/nautilus/compression/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.549: watch_established: "/org/gnome/nautilus/window-state/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.549: watch_established: "/org/gnome/nautilus/icon-view/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.549: watch_established: "/org/gnome/nautilus/list-view/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.549: watch_established: "/org/gtk/settings/file-chooser/" (establishing: 1) (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.549: watch_established: "/org/gnome/desktop/lockdown/" (establishing: 1) (org.gnome.Nautilus:10423): seahorse-nautilus-DEBUG: 13:35:26.550: seahorse nautilus module initialized (org.gnome.Nautilus:10423): dconf-DEBUG: 13:35:26.550: watch_fast: "/org/gnome/desktop/lockdown/" (establishing: 0, active: 1) (org.gnome.Nautilus:10423): GLib-DEBUG: 13:35:26.573: setenv()/putenv() are not thread-safe and should not be used after threads are created /usr/lib64/python3.11/site-packages/gi/module.py:168: Warning: g_boxed_type_register_static: assertion 'g_type_from_name (name) == 0' failed g_type = info.get_g_type() /usr/lib64/python3.11/site-packages/gi/module.py:168: Warning: g_once_init_leave: assertion 'result != 0' failed g_type = info.get_g_type() /usr/lib64/python3.11/site-packages/gi/module.py:203: Warning: g_type_get_qdata: assertion 'node != NULL' failed type_ = g_type.pytype Running as nautilus as root does not help, same result after a reboot. I also trying to run "tracker3 reset --filesystem" and attempt to start nautilus again, this didn't work either. The application wouldn't show at all, but is present in the task monitor. Hope this helps.
Running tracker3 status on a Sway didn't result on tracker3 freezing: instead, it reported some errors, all relative to cue files: Già indicizzato: 4598 file, 332 cartelle Spazio residuo sulla partizione del database: 75,1 GB (14,98%) Tutti gli estrattori sono inattivi, indicizzazione completata 5 errori registrati URI: file:///home/sirduke/Musica/italian/Fabrizio%20De%20Andre/Fabrizio%20De%20Andr%C3%A9%20-%20Fabrizio%20De%20Andr%C3%A9%20in%20concerto%20(DVD)%20(1998)%20(AC3%202.0,%205.1,%20Cue)/2.0/01.cue Messaggio: Not a CUE sheet URI: file:///home/sirduke/Musica/italian/Fabrizio%20De%20Andre/Fabrizio%20De%20Andr%C3%A9%20-%20Fabrizio%20De%20Andr%C3%A9%20in%20concerto%20(DVD)%20(1998)%20(AC3%202.0,%205.1,%20Cue)/5.1/01.cue Messaggio: Not a CUE sheet URI: file:///home/sirduke/Musica/italian/Fabrizio%20De%20Andre/Fabrizio%20De%20Andr%C3%A9%20-%20Fabrizio%20De%20Andr%C3%A9%20in%20concerto%20(DVD)%20(1998)%20(AC3%202.0,%205.1,%20Cue)/2.0/02.cue Messaggio: Not a CUE sheet URI: file:///home/sirduke/Musica/italian/Fabrizio%20De%20Andre/Fabrizio%20De%20Andr%C3%A9%20-%20Fabrizio%20De%20Andr%C3%A9%20in%20concerto%20(DVD)%20(1998)%20(AC3%202.0,%205.1,%20Cue)/5.1/02.cue Messaggio: Not a CUE sheet URI: file:///home/sirduke/Musica/patterns/Wilco%20-%20Yankee%20Hotel%20Foxtrot%20(2002)/Yankee%20Hotel%20Foxtrot.cue Messaggio: Not a CUE sheet Moving the error-causing files to an external disk resulted in nautilus, GNOME activity and definitely tracker to work well again. Today I tried to reproduce it by inserting those files again, but tracker3 does not manifest the bug behavior again. This means that the bug is somehow solved for my machine. Still, I will attach the error-causing files as well as the above message in hope this helps to solve the bug for other people too.
Created attachment 1925983 [details] Archive containing error message and error-causing files
Created attachment 1926293 [details] journalctl -x -b -e right after nautilus and tracker3 stopped working
Created attachment 1926295 [details] File errors that were fixed one by one using a script These were the file errors listed when I used tracker3 status when it worked for a brief amount of time. These errors are fixed by a script one by one as the OP's solution tracker3 reset --filesystem did not work. After a system reboot the errors were shown again but not all files. Some errors were very weird. Thought these could help.
I have the same error
Hello, I have a very similar issue, with tracker3 status also returning some errors with JPEG and PNG files. I deleted the files in question but this did not help. Finally I found this post on reddit suggesting to remove nautilus-python package: https://www.reddit.com/r/ManjaroLinux/comments/ywg8k6/cannot_open_nautilus_after_gnome_43_update/ After I uninstalled nautilus-python and rebooted, it start working again normally. I don't know if this is the correct bug tracker to report this. Let me know if I should open another one, or report to another existing tracker. Thanks.
antoine+redhat ... The nautilus-python package couldn't be the issue. I don't have it installed on my system but still have the issue on and off
Yes same for me @antoine+redhat . `nautilus-python` is not installed. tracker3 doesn't stop normally on Fedora 37 shutdown. It stopped after 1min30. File indexing is broken and prevent Nautilus and Boxes to be launched most of the time. File searching doesn't show any files. The command `tracker3 status` displays a blinking cursor and nothing else, even after waiting many hours. I tried `tracker3 reset --filesystem`. It works for some minutes with a large CPU consumption (fan gets noisy), but the issue comes again.
Hello, @mail I did not encounter the issue since I removed `nautilus-python`. I guess I had a different issue not related to this bug.
I didn't met this bug for around 3 weeks. It seems fixed.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.