** Changed in: mlocate (Debian)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/281471
Title:
Unable to use 'locate' to locate files mlocate.db permission den
Not sure what happened over time but I don't see the problem anymore,
Ubuntu 20.10, mlocate 0.26-3ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/281471
Title:
Unable to use 'locate' to locate
** Changed in: mlocate (Debian)
Status: Unknown => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/281471
Title:
Unable to use 'locate' to locate files mlocate.db permission denied
May be some some system groups change gid during system upgrade. In this
case mlocate created before upgrade retains old gid and loses ability to
read mlocate.db. I have access to several hosts and mlocate group have
different gid there. Of course it does not explain what removes sgid.
Possible wo
** Bug watch added: Debian Bug tracker #664206
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664206
** Also affects: mlocate (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664206
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
Same issue on a 15.10 upgraded to 16.04:
e0101450@bhaskark:/Distrib/Ubuntu$ locate abc.def
locate: can not open `/var/lib/mlocate/mlocate.db': Permission denied
e0101450@bhaskark:/Distrib/Ubuntu$ ls -l /var/lib/mlocate/mlocate.db
-rw-r- 1 root mlocate 25974609 May 16 09:21 /var/lib/mlocate/mlo
On a new Xubuntu 16.04 installation, I saw the following permissions:
ls -l /usr/bin/mlocate
-rwxr-xr-x 1 root saned 39520 Nov 18 2014 /usr/bin/mlocate
1) mlocate didn't have setuid (which might be ok for some use cases)
2) the group is saned which is completely wrong. I assume the group is assi
Still there in Ubuntu 12.04, is this going to be fixed eventually?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/281471
Title:
Unable to use 'locate' to locate files mlocate.db permission denied
To
Still there in Ubuntu 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/281471
Title:
Unable to use 'locate' to locate files mlocate.db permission denied
To manage notifications about this bug go
Still there in Ubuntu 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/281471
Title:
Unable to use 'locate' to locate files mlocate.db permission denied
To manage notifications about this bug go
This bug is still present in Ubuntu 10.11!
Ian's fix in comment #5 fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/281471
Title:
Unable to use 'locate' to locate files mlocate.db permission
** Changed in: mlocate (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/281471
Title:
Unable to use 'locate' to locate files mlocate.db permission denied
--
u
[Sorry for the spam - I didn't notice that my posts were working despite a
popup saying "The following errors were encountered:
Object: , name: u'ubuntu-eee'"]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
I still see this problem, running maverick. In my case the executable's
group was avahi:
-rwxr-sr-x 1 root avahi 35432 2010-03-24 06:35 /usr/bin/mlocate
Ian's fix worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
I still see this problem, running maverick. In my case the executable's
group was avahi:
-rwxr-sr-x 1 root avahi 35432 2010-03-24 06:35 /usr/bin/mlocate
Ian's fix worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
I still see this problem, running maverick. In my case the executable's
group was avahi:
-rwxr-sr-x 1 root avahi 35432 2010-03-24 06:35 /usr/bin/mlocate
Ian's fix in comment 5 fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I still see this problem, running maverick. In my case the executable's
group was avahi:
-rwxr-sr-x 1 root avahi 35432 2010-03-24 06:35 /usr/bin/mlocate
Ian's fix in comment #5 fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I still see this problem, running maverick. In my case the executable's
group was avahi:
-rwxr-sr-x 1 root avahi 35432 2010-03-24 06:35 /usr/bin/mlocate
Ian's fix in comment #5 fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I still see this problem, running maverick. In my case the executable's
group was avahi:
-rwxr-sr-x 1 root avahi 35432 2010-03-24 06:35 /usr/bin/mlocate
Ian's fix in comment #5 fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I still see this problem, running maverick. In my case the executable's
group was avahi:
-rwxr-sr-x 1 root avahi 35432 2010-03-24 06:35 /usr/bin/mlocate
Ian's fix in comment #5 fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Jordan,
I had the same problem. After a Jaunty install, I found that
/usr/bin/mlocate belonged to the ssl-cert group, clearly incorrect!
Reading the man page for locate, I found that locate (which is symlinked
to mlocate by default) must run as a set-gid mlocate (which means the
process automatic
Better workaround (only have to apply it once):
sudo usermod -a -G mlocate $USER
Logout, log back in and locate works again.
--
Unable to use 'locate' to locate files mlocate.db permission denied
https://bugs.launchpad.net/bugs/281471
You received this bug notification because you are a member
** Changed in: mlocate (Ubuntu)
Sourcepackagename: None => mlocate
--
Unable to use 'locate' to locate files mlocate.db permission denied
https://bugs.launchpad.net/bugs/281471
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Workaround:
sudo chgrp mlocate /usr/bin/mlocate
sudo chmod g+s /usr/bin/mlocate
--
Unable to use 'locate' to locate files mlocate.db permission denied
https://bugs.launchpad.net/bugs/281471
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have this problem with locate but not with ping or crontab.
I don't want to set set the s bit because locate is supposed to only show users
the location of files they have permission to see.
The problem on my system seems to be that /var/lib/mlocate/mlocate.db is
unreadable by others. If I chm
25 matches
Mail list logo
