systemctl --user status localsearch-3
× localsearch-3.service - Tracker file system data miner
Loaded: loaded (/usr/lib/systemd/user/localsearch-3.service; disabled; preset: disabled)
Active: failed (Result: exit-code) since Tue 2025-03-11 17:20:24 CET; 1h 7min ago
Invocation: 559165d1fae4476982a6ae415d180246
Process: 20430 ExecStart=/usr/libexec/localsearch-3 (code=exited, status=1/FAILURE)
Main PID: 20430 (code=exited, status=1/FAILURE)
OK, at least we have found the problem (if not yet the culprit).
Try:
systemctl --user start localsearch-3
then again check the status.
~> systemctl --user status localsearch-3
× localsearch-3.service - Tracker file system data miner
Loaded: loaded (/usr/lib/systemd/user/localsearch-3.service; disabled; preset: disabled)
Active: failed (Result: exit-code) since Tue 2025-03-11 17:20:24 CET; 1h 7min ago
Invocation: 559165d1fae4476982a6ae415d180246
Process: 20430 ExecStart=/usr/libexec/localsearch-3 (code=exited, status=1/FAILURE)
Main PID: 20430 (code=exited, status=1/FAILURE)
harvey@localhost:~> systemctl --user start localsearch-3
Job for localsearch-3.service failed because the control process exited with error code.
See "systemctl --user status localsearch-3.service" and "journalctl --user -xeu localsearch-3.service" for details.
~> systemctl --user status localsearch-3.service
× localsearch-3.service - Tracker file system data miner
Loaded: loaded (/usr/lib/systemd/user/localsearch-3.service; disabled; preset: disabled)
Active: failed (Result: exit-code) since Tue 2025-03-11 18:41:34 CET; 2min 49s ago
Invocation: 85c42aa26d294d3b9b047efb1d2bca90
Process: 58239 ExecStart=/usr/libexec/localsearch-3 (code=exited, status=1/FAILURE)
Main PID: 58239 (code=exited, status=1/FAILURE)
~> journalctl --user -xeu localsearch-3.service
Hint: You are currently not seeing messages from the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
Add your current user to the systemd-journal group, logout/login and try again, there should be something interesting in the journal…
~> systemctl --user status localsearch-3
× localsearch-3.service - Tracker file system data miner
Loaded: loaded (/usr/lib/systemd/user/localsearch-3.service; disabled; preset: disabled)
Active: failed (Result: exit-code) since Tue 2025-03-11 19:38:38 CET; 2min 43s ago
Invocation: 10c0f2242b1a4430965e18abe0ba9375
Process: 19779 ExecStart=/usr/libexec/localsearch-3 (code=exited, status=1/FAILURE)
Main PID: 19779 (code=exited, status=1/FAILURE)
Mär 11 19:38:38 localhost systemd[17673]: localsearch-3.service: Scheduled restart job, restart counter is at 9.
Mär 11 19:38:38 localhost systemd[17673]: localsearch-3.service: Start request repeated too quickly.
Mär 11 19:38:38 localhost systemd[17673]: localsearch-3.service: Failed with result 'exit-code'.
Mär 11 19:38:38 localhost systemd[17673]: Failed to start Tracker file system data miner.
Did I do an update in the meantime?
Maybe a logout / login?
Same again essentially…
○ localsearch-3.service - Tracker file system data miner
Loaded: loaded (/usr/lib/systemd/user/localsearch-3.service; disabled; preset: disabled)
Active: inactive (dead)
Mär 11 20:43:40 localhost systemd[2490]: localsearch-3.service: Scheduled restart job, restart counter is at 7.
Mär 11 20:43:40 localhost systemd[2490]: Starting Tracker file system data miner...
Mär 11 20:43:41 localhost localsearch-3[26073]: Could not create store: ambiguous column name: ROWID
Mär 11 20:43:41 localhost systemd[2490]: localsearch-3.service: Main process exited, code=exited, status=1/FAILURE
Mär 11 20:43:41 localhost systemd[2490]: localsearch-3.service: Failed with result 'exit-code'.
Mär 11 20:43:41 localhost systemd[2490]: Failed to start Tracker file system data miner.
Mär 11 20:43:41 localhost systemd[2490]: localsearch-3.service: Scheduled restart job, restart counter is at 8.
Mär 11 20:43:41 localhost systemd[2490]: localsearch-3.service: Start request repeated too quickly.
Mär 11 20:43:41 localhost systemd[2490]: localsearch-3.service: Failed with result 'exit-code'.
Mär 11 20:43:41 localhost systemd[2490]: Failed to start Tracker file system data miner.
I don’t know the details (I don’t really use tracker myself) but maybe there is a timer that triggers every hour or so in case of error and looking at the journal seems the way to go now.
What I see here is that localsearch-3.service started with my login in the morning and remained active since, then I stopped and restarted it for testing and it has been running for 3:30 hours as of this writing.
So there is something broken in your system, maybe create a fresh user and test if the search works with a fresh configuration.
Just now, this morning
~> systemctl --user start localsearch-3
Job for localsearch-3.service failed because the control process exited with error code.
See "systemctl --user status localsearch-3.service" and "journalctl --user -xeu localsearch-3.service" for details.
and
~> journalctl --user -xeu localsearch-3.service
No journal files were found.
t[quote=“OrsoBruno, post:28, topic:183160, full:true”]
So there is something broken in your system, maybe create a fresh user and test if the search works with a fresh configuration.
[/quote]
Thanks very much for your help so far!
Would the fresh user idea, at best only confirm that my configuration is broken. If it works, would I then have to transfer all my data and apps across to the new user. Feels a bit like a sledge-hammer to crack a nut, remembering that I am only trying to correct the fault in one, albeit important, function.
We are still trying to understand what is wrong with your system. Localsearch is started on a per-user basis, so the fault might be at system level or at user level.
If you don’t add your user to the systemd-journal group you cannot see system messages in the journal. If you do not try a fresh user we don’t know if the fault might be at user level.
Sorry, but we cannot access your system or browse over your shoulder so if you don’t provide useful data we cannot help.
How far to go to fix your system is entirely up to you, personally I have Tracker disabled on my daily system.
I am just curious to know what a new user would reveal, except that ‘it works’, but will that also reveal the wrong settings in my existing account. If not, then I fear the implications of a migration from the old to the new account.
My own user memberships are currently systemd-journal and users (default).
So, does
journalctl --user -ru localsearch-3.service
show something interesting about why localsearch doesn’t start?
~> systemctl --user start localsearch-3
Job for localsearch-3.service failed because the control process exited with error code.
See "systemctl --user status localsearch-3.service" and "journalctl --user -xeu localsearch-3.service" for details.
~> journalctl --user -ru localsearch-3.service
No journal files were found.
-- No entries --
Try:
journalctl -b -r
localsearch status
Numerous (>20) identical repetitions of 23 lines followed by a final large repetitious block each covering the same 5 minute period.
So at least the system journal is there…
What about
localsearch status
~> localsearch status
Could not establish a connection to Tracker: Could not activate remote peer 'org.freedesktop.Tracker3.Miner.Files': startup job failed
Reference to Tracker puzzles me a little, because Tracker is not a loadable package from the TW repos whereas it was available under Leap 15. Am I right in thinking that the Tracker indexing function has somehow been taken over by tinysparql ?
Yes, but there are still remnants, at least in the naming of some packages:
LT-B:~ # zypper --no-refresh info --provides typelib-1_0-Tracker-3_0
Loading repository data...
Reading installed packages...
Information for package typelib-1_0-Tracker-3_0:
------------------------------------------------
Repository : repo-oss
Name : typelib-1_0-Tracker-3_0
Version : 3.8.2-1.4
Arch : x86_64
Vendor : openSUSE
Installed Size : 48.3 KiB
Installed : Yes (automatically)
Status : up-to-date
Source package : tinysparql-3.8.2-1.4.src
Upstream URL : https://gitlab.gnome.org/GNOME/tinysparql
Summary : Introspection bindings for the tinysparql Sparql library
Description :
tinysparql is a desktop-neutral object database, tag/metadata database,
search tool and indexer.
This package provides the GObject Introspection bindings for the
sparql library for tinysparql.
Provides : [4]
typelib(Tracker) = 3.0
typelib(Tsparql) = 3.0
typelib-1_0-Tracker-3_0 = 3.8.2-1.4
typelib-1_0-Tracker-3_0(x86-64) = 3.8.2-1.4
LT-B:~ #
Check
zypper packages --orphaned
and/or compare what you have with the following:
LT-B:~ # zypper se -si racker
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-------------------------+---------+-------------+--------+-----------
i | grilo-plugin-tracker | package | 0.3.16-1.10 | x86_64 | repo-oss
i | libtracker-sparql-3_0-0 | package | 3.8.2-1.4 | x86_64 | repo-oss
i | rygel-plugin-tracker | package | 0.44.1-1.4 | x86_64 | repo-oss
i | typelib-1_0-Tracker-3_0 | package | 3.8.2-1.4 | x86_64 | repo-oss
LT-B:~ #
I get the same if localsearch statusis invoked by superuser (root), because localsearch is not started for user ‘root’.
So apparently something tells the system not to start localsearch for your current user…
Please, again, create a new user and see how that goes.