Package mlocate installed yet, command mlocate not found - and more

Support
1

Hello,

Requirements:

I have Searched the forum for my issue and found nothing related or helpful
I have checked the Resources category (Resources Index)
I have reviewed the Wiki for relevant information
I have read the the Release Notes and Errata

**OpenMandriva Lx version:6

**Desktop environment (KDE, LXQT…):*irrelevant *

Package mlocate installed yet command mlocate not found

Description of the issue (screenshots if relevant):

LC_ALL=C sudo dnf install mlocate 
[sudo] password for kuba: 
Last metadata expiration check: 4:49:37 ago on Wed Apr 23 10:11:51 2025.
Dependencies resolved.
================================================================================
 Package          Architecture    Version            Repository            Size
================================================================================
Installing:
 mlocate          x86_64          0.26-26            rock-x86_64          100 k

Transaction Summary
================================================================================
Install  1 Package

Total download size: 100 k
Installed size: 339 k
Is this ok [y/N]: y
Downloading Packages:
mlocate-0.26-26-omv4050.x86_64.rpm              168 kB/s | 100 kB     00:00    
--------------------------------------------------------------------------------
Total                                           167 kB/s | 100 kB     00:00     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                        1/1 
  Running scriptlet: mlocate-0.26-26.x86_64                                 1/1 
  Installing       : mlocate-0.26-26.x86_64                                 1/1 
  Running scriptlet: mlocate-0.26-26.x86_64                                 1/1 
Created symlink '/etc/systemd/system/timers.target.wants/updatedb.timer' -> '/usr/lib/systemd/system/updatedb.timer'.
Warning: The unit file, source configuration file or drop-ins of updatedb.timer changed on disk. Run 'systemctl daemon-reload' to reload units.


Installed:
  mlocate-0.26-26.x86_64                                                        

Complete!
kuba@kuba:~$ LC_ALL=C sudo systemctl daemon-reload

Let’s try to use command

sudo updatedb
LC_ALL=C mlocate -b *cov
bash: mlocate: nie znaleziono polecenia <-- btw this should be translated to English.
It should be bash: mlocate: command not found

same goes with sudo  mlocate -b *cov

now

whereis mlocate
mlocate:       ?????

So maby

kuba@kuba:~$ sudo whereis mlocate
mlocate:            ?????!!!??? nope
kuba@kuba:~$

Oh, ok, package is installed, but it is in a fact not installed.
Lets check that

kuba@kuba:~$ LC_ALL=C sudo dnf install mlocate 
[sudo] password for kuba: 
Last metadata expiration check: 5:13:41 ago on Wed Apr 23 10:11:51 2025.
Package mlocate-0.26-26.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
kuba@kuba:

so i tried as last resort

sudo /usr/bin/mlocate -b *W-8 BEN*
[sudo] hasło użytkownika kuba: 
sudo: /usr/bin/mlocate: nie znaleziono polecenia

Nope

Now, either I’m a moron or my installation is broken.

I used this particular iso as mu installation source OpenMandrivaLx.6.0-snapshot.20250420.3876-plasma6x11.x86_64.iso

I had a weird issues with it from the very beginning

First om-welcome glich then super -p does not work on kde
Plasma 6.3.5 patch

Bero said

berocooker

We already have that patch

Those were issues I have reported in form of questions but I had more

I’m extremely confused at this point.
Option 1 I’m an idiot and all of this happened by my lack of skill and wrong doing. And that is quite probable cause

Option 2 OM was released a bit too early, and we have some errors that go unnoticed under the radar. Yup maby

Option 3 Black hole physics or black magic are all to blame

2

What if you manually mark the package as installed? Guessing here.

sudo dnf mark install mlocate
3

is there any plocate or llocate possible ?

4 
sudo dnf mark install mlocate
mlocate -b cov*
bash: mlocate: nie znaleziono polecenia <-- mlocate command not found
kuba@kuba:~$

plocate works

plocate -b cov.*
/home/kuba/Pulpit/z-pulpitu/cov.mp4

mlocate didn’t work on OM5 also and I forgot about that

Maybe it should be removed from the repos ?

Now i have strange issue with pulseaudio and sound in shotcut

I must read logs first, but not today.

I’m bugging you all with my strange issues for 3 days straight.
To be fair, I feel a little ashamed / bad with it.

I really should deep dive in logs before any next question
It may be pulseaudio issue, shotcut issue, OM6 issue or im an idiot issue
As I said before

Option 1 I’m an idiot and all of this happened by my lack of skill and wrong doing. And that is quite probable cause

Option 2 OM was released a bit too early, and we have some errors that go unnoticed under the radar. Yup maby

Option 3 Black hole physics or black magic are all to blame
:stuck_out_tongue: :wink:

5

Very easy solution: you can use the binary locate for both mlocate or plocate. You may check it looking at the package content

dnf repoquery --list mlocate
dnf repoquery --list plocate
6

mlocate plocate is “frontend” of locate I had no idea about, that thank-you.

7

Isn’t this solved. If so please mark this as solved.

1 Like
8

mlocate is very old coming from gnome Gtk2 and use also by Mate
this have review after with plocate to optimize db

9

I think there’s 2 different things called mlocate, which may well be causing the confusion.

We have THIS mlocate: Overview - mlocate - Pagure.io - it’s in the mlocate package, it’s an implementation of the “locate”/“updatedb” tools and is CLI only. The binary is just called “locate” because that’s what the standards expect us to have – so install mlocate and invoke it as “locate”.

And then there’s some obscure locate frontend (probably originating from Mate) that makes use of the locate tool. We don’t currently package this.

10

FWIW it is probably recommendable to use plocate over mlocate. That, too, is an implementation of the locate command, and it, too, is called locate in the filesystem because that’s where it’s expected.

Some other distros rename mlocate to mlocate and plocate to plocate, but IMO that doesn’t make much sense – it’s a system wide tool (and updatedb needs to run globally), so there’s no reason why someone would want to install multiple locate implementations at the same time.

11

true

12

@ben79 I would happily mark this as solved… but i have no freaking idea how. (I’m incapable to edit a title of original post)

13

Under each post, there is a box with a check mark in it. Pick the post that solved your issue and click that box.

2 Likes
14

oh shit :rofl: sorry
done