Identical (except Installed ‘Yes’ (.i.e. not ‘automatically’))
Orphaned packages include, (that I cannot judge for relevance here)
i | @System | libx265-199 | 3.5-150600.2.pm.7 | x86_64
i+ | @System | snapd | 2.68-lp156.1.1 | x86_64
~> 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 | Main Repository (OSS)
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 | Main Repository (OSS)
i+ | libtracker-sparql-3_0-0 | package | 3.8.2-1.4 | x86_64 | repo-oss
i+ | typelib-1_0-Tracker-3_0 | package | 3.8.2-1.4 | x86_64 | Main Repository (OSS)
i+ | typelib-1_0-Tracker-3_0 | package | 3.8.2-1.4 | x86_64 | repo-oss
I suppose the duplicate repos have arisen after my offline migration
to Tumbleweed from dvd which set up the Main Repos, followed
by later `zypper dup` updates that added the repo-oss additionally.Nothing relevant to the problem at hand; you may cleanup something when you have time.
Let’s look at the service definition:
systemctl --user cat localsearch-3.service
and, just to be sure, check what version of localsearch you have:
zypper se -si localsearch
# /usr/lib/systemd/user/localsearch-3.service
[Unit]
Description=Tracker file system data miner
ConditionUser=!root
ConditionUser=!gnome-initial-setup
After=gnome-session.target
[Service]
Type=dbus
BusName=org.freedesktop.LocalSearch3
ExecStart=/usr/libexec/localsearch-3
Restart=on-failure
# Don't restart after tracker daemon -k (aka tracker-control -k)
RestartPreventExitStatus=SIGKILL
Slice=background.slice
[Install]
WantedBy=gnome-session.target
localsearch package version is 3.8.2-1.3
I fired up a test Leap 15.6 install and guess what? Text search doesn’t work and the symptoms are similar to those reported here.
Since it is a system I seldom use I cannot guarantee that all is well with it and certainly I didn’t check Tracker there until today, but there is something to think about.
BTW, everything apparently good in your last post, I’m running out of ideas…
I got Full Text Search to work under Leat 15.6. by installing Tracker first (it wasn’t there by default) and letting it index all my files.
There is a reset function in case the data base got corrupted
localsearch reset --filesystem
WARNING that will wipe any previous indexing and indexing again will take a while if you have many files, so think twice.
But since it is not working now, I think you have little to lose…
I did it.
Found 0 PIDs…
What now? Restart?
So there is no indexing process running, if you try to start one it fails (see post #34).
There might be something wrong in the systemd chain that should start local indexing as soon as a user logs in a Gnome session, but that is apparently above my pay grade 
Just to rule out the obvious, are you running a Gnome Wayland session?
Gnome on Xorg
No error messages after
systemctl --user start localsearch-3
localsearch-3 has started!
…but taking 0% CPU?
Full Text Search seems to be working now!!
Indexing obviously didn’t take long, presumably because I had set the file list short for test purposes.
Great stuff! Many thanks.
But now I have to ask, is the tracker supposed to get started automatically? If so, how can I make it do so?
and…how do I know when the indexing is done?
bruno@LT-B:~> localsearch status
Currently indexed: 1595 files, 158 folders
Remaining space on database partition: 3,5 GB (1,89%)
All data miners are idle, indexing complete
bruno@LT-B:~>
So the database reset did the trick apparently?
Yes.
All data miners are idle, indexing complete
291 recorded failures
I had to start the indexing by hand after power on. Shouldn’t that be automatic?
Yes, started after a Gnome session is established for a user on login to Gnome (unless the default configuration was changed one way or the other). Check:
systemctl --user status localsearch-3.service
Loaded: loaded (/usr/lib/systemd/user/localsearch-3.service; disabled; preset: disabled)
Active: active (running) since Thu 2025-03-13 09:01:56 CET; 1h 31min ago
Active (running) because I started it by hand?
Logout, login and try again to see what changes?
You may also look at dconf, /org/freedesktop/tracker/… and see if there is something odd.
Or backup ~/.config/dconf/user and then delete it and see if a default one is created on next login (or copy one from a fresh user…) and see what happens.
dconf confuses me a bit. Both ‘index-on-battery’ and index-on-batterry-first-time’ are set on. But there is no equivalent switch for power-up, unless those are supposed to be the ones. But my configuration is a(n old) desktop, not a mobile device.