You are not logged in.
While checking the health of my system, I found recently a lot of files (>6000) with broken ownership
find /boot /etc /opt /root /srv /usr /home -nouser 2>/dev/null
...
/usr/share/man/nl/man1/faked.1.gz
/usr/share/man/nl/man1/fakeroot.1.gz
/usr/share/man/sv/man1/faked.1.gz
/usr/share/man/sv/man1/fakeroot.1.gz
/usr/share/man/pt/man1/faked.1.gz
/usr/share/man/pt/man1/fakeroot.1.gz
ls -lan /usr/share/man/pt/man1/fakeroot.1.gz
-rw-r--r-- 1 1004 1000 4509 May 25 11:44 /usr/share/man/pt/man1/fakeroot.1.gzThere is no user 1004 on my system. and why has it group 1000 ?
Removing the package and reinstalling does not help.
I think the fault is already in the provided package, I downloaded and extracted it fresh from the website:
$ tar --numeric-owner -tvf fakeroot-1.29-1.0-pentium4.pkg.tar
-rw-r--r-- 0/0 5832 2022-05-25 11:44 .BUILDINFO
-rw-r--r-- 0/0 140 2022-05-25 11:44 .INSTALL
-rw-r--r-- 0/0 1904 2022-05-25 11:44 .MTREE
-rw-r--r-- 0/0 493 2022-05-25 11:44 .PKGINFO
drwxr-xr-x 0/0 0 2022-05-25 11:44 etc/
drwxr-xr-x 0/0 0 2022-05-25 11:44 etc/ld.so.conf.d/
-rw-r--r-- 0/0 21 2022-05-25 11:44 etc/ld.so.conf.d/fakeroot.conf
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/bin/
-rwxr-xr-x 0/0 26020 2022-05-25 11:44 usr/bin/faked
-rwxr-xr-x 0/0 3968 2022-05-25 11:44 usr/bin/fakeroot
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/lib/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/lib/libfakeroot/
-rwxr-xr-x 0/0 59384 2022-05-25 11:44 usr/lib/libfakeroot/libfakeroot-0.so
lrwxrwxrwx 0/0 0 2022-05-25 11:44 usr/lib/libfakeroot/libfakeroot.so -> libfakeroot-0.so
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/doc/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/doc/fakeroot/
-rw-r--r-- 0/0 521 2022-05-25 11:44 usr/share/doc/fakeroot/README
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/de/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/de/man1/
-rw-r--r-- 1004/1000 1517 2022-05-25 11:44 usr/share/man/de/man1/faked.1.gz
-rw-r--r-- 1004/1000 4779 2022-05-25 11:44 usr/share/man/de/man1/fakeroot.1.gz
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/es/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/es/man1/
-rw-r--r-- 1004/1000 1454 2022-05-25 11:44 usr/share/man/es/man1/faked.1.gz
-rw-r--r-- 1004/1000 4494 2022-05-25 11:44 usr/share/man/es/man1/fakeroot.1.gz
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/fr/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/fr/man1/
-rw-r--r-- 1004/1000 1522 2022-05-25 11:44 usr/share/man/fr/man1/faked.1.gz
-rw-r--r-- 1004/1000 4701 2022-05-25 11:44 usr/share/man/fr/man1/fakeroot.1.gz
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/man1/
-rw-r--r-- 1004/1000 1190 2022-05-25 11:44 usr/share/man/man1/faked.1.gz
-rw-r--r-- 1004/1000 4006 2022-05-25 11:44 usr/share/man/man1/fakeroot.1.gz
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/nl/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/nl/man1/
-rw-r--r-- 1004/1000 1444 2022-05-25 11:44 usr/share/man/nl/man1/faked.1.gz
-rw-r--r-- 1004/1000 4797 2022-05-25 11:44 usr/share/man/nl/man1/fakeroot.1.gz
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/pt/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/pt/man1/
-rw-r--r-- 1004/1000 1435 2022-05-25 11:44 usr/share/man/pt/man1/faked.1.gz
-rw-r--r-- 1004/1000 4509 2022-05-25 11:44 usr/share/man/pt/man1/fakeroot.1.gz
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/sv/
drwxr-xr-x 0/0 0 2022-05-25 11:44 usr/share/man/sv/man1/
-rw-r--r-- 1004/1000 1438 2022-05-25 11:44 usr/share/man/sv/man1/faked.1.gz
-rw-r--r-- 1004/1000 4292 2022-05-25 11:44 usr/share/man/sv/man1/fakeroot.1.gzOffline
Sounds suspiciously like the uid/gid of one of my build slaves:
uid=1004(slave5) gid=1000(slaves) groups=1000(slaves)
No clue, why this permission are now suddenly in the package though..
Can confirm, this is comming from the package, if I install fakeroot I also
get:
-rw-r--r-- 1 1004 test 4509 May 25 09:44 /usr/share/man/pt/man1/fakeroot.1.gz
Tar/bsdtar/pacman unpack the uid/gids as they are (they are just numbers), the
users don't have to exist on the system.
If there is a bug, then in the devtools32/makepkg, which should set sane ownerships
for files in the package (in this case 0/0, root/root).
Offline
I've found files with users 1001 and 1005, which are not valid users on my system. They all seem to have group 1000. Most of mine seem to be in my manpages, and there's nothing in /usr/bin. The wrong users in my manpages doesn't seem to stop me using man though, so I'm not sure how long this has been going on, or indeed what the effect of it is.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
I reviewed my old logs,
at 2022-04-14 the after update check is fine,
at 2022-05-27 the logs shows the issue after the update.
Files in this folders are currently affected on my machine:
/usr/share/alsa/ucm2/
/usr/share/info
/usr/share/man/ Last edited by alf9009 (2022-07-23 15:26:01)
Offline
maybe helpful, affected object types on my machine:
directories
.conf files (in the alsa directoy)
.gz files (most of the issue)
Offline
Yes, I also found conf files in usr.share/alsa/ucm2/. The gz files are in /uwr/share/man, and also in /usr/share/info, and also a couple of files in /usr/share/ROX-Filer, which is weird since there are other files in there and I'd have thought they would be all from the same package. The misconfigured directories I've got are in /usr/share/alsa/ucm2
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline