You are not logged in.
Hey guys,
Had some spare time on a saturday and thought I'd find a solution for some warnings/errors I get when launching Nautilus, which presumably also make it load slow (2 seconds to pop up).
$ nautilus
** (nautilus:3749): WARNING **: 22:55:41.069: Error on getting connection: Failed to load SPARQL backend: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
(nautilus:3749): GLib-GIO-CRITICAL **: 22:55:43.083: g_dbus_connection_signal_unsubscribe: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(nautilus:3749): GLib-GObject-CRITICAL **: 22:55:43.083: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(nautilus:3749): GLib-GObject-CRITICAL **: 22:55:43.083: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
As far as I can see this is because the tracker is not running? However
systemctl status dbus
and
systemctl --user status dbus
both indicate that D-Bus is active and running.
Getting the tracker status indeed confirms the problem lies there:
$ tracker status
Could not establish a connection to Tracker: Failed to load SPARQL backend: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Is this because I'm running GNOME with Wayland? Is that related? Otherwise, can someone point me in the right direction? I see many other people posting logs with that warning, but nobody really pays attention to it? The criticals look severe though...
Thanks!
Last edited by tdewolff (2018-10-13 10:07:21)
Offline
I have the exact same issue with Gnome under X, so I don't think it's related to Wayland.
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
Tracker works on X11 and Wayland. Is the tracker daemon running? You can check that with
$ tracker daemon --list-processes
That should return multiple running processes like "tracker-store" and "tracker-miner-fs". In case there are no processes running, you can start tracker with
tracker daemon --start
Offline
Hmm, turns out it wasn't running. Why though? How is it normally started? Because I don't see e.g a systemd unit.
It is better to keep your mouth shut and be thought a fool than to open it and remove all doubt. (Mark Twain)
Offline
Yes, there were no tracker processes running, but issueing `--start` only started the tracker-store, and none of the miners.
However, I ran
tracker reset --hard
which seems to have fixed the error messages I used to get. Looking in the journalctl logs, tracker-store was running in circles with
tracker-store[10752]: Cannot initialize database: error in view fts_view: no such table: main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not necessarily related): No such file or directory)
which is also fixed now.
Last edited by tdewolff (2018-10-15 09:32:53)
Offline
@dcc24 Normally tracker is started automatically. There are some desktop files for tracker in /etc/xdg/autostart and there is a systemd user service that is enabled by default:
systemctl --user status tracker-store
Offline