When attempting to use "ufw", I was getting loads of errors:

Code: Select all

WARN: uid is 0 but '/etc' is owned by 100000
WARN: uid is 0 but '/lib' is owned by 100000
WARN: uid is 0 but '/etc/default' is owned by 100000
WARN: uid is 0 but '/usr/sbin' is owned by 100000
WARN: uid is 0 but '/usr' is owned by 100000

I looked at the listing of "ls -lah /" and saw this:

Code: Select all

drwxr-xr-x  24 root   root   4.0K Nov 21 09:04 .
drwxr-xr-x  24 root   root   4.0K Nov 21 09:04 ..
drwxr-xr-x   2 100000 colord 4.0K Nov  3 09:24 bin
drwxr-xr-x   4 100000 colord 1.0K Nov 21 09:05 boot
drwxr-xr-x   2 root   root   4.0K Jun 23 10:54 cdrom
drwxr-xr-x  19 root   root   4.0K Nov 23 09:20 dev
drwxr-xr-x 136 100000 colord  12K Nov 23 09:20 etc
drwxr-xr-x   3 100000 colord 4.0K Jun 23 10:54 home
lrwxrwxrwx   1 root   root     33 Nov 21 09:04 initrd.img -> boot/initrd.img-4.10.0-40-generic
lrwxrwxrwx   1 root   root     33 Oct 31 09:04 initrd.img.old -> boot/initrd.img-4.10.0-38-generic
drwxr-xr-x  23 100000 colord 4.0K Sep 27 09:11 lib
drwxr-xr-x   2 100000 colord 4.0K Jun 22 11:20 lib64
drwx------   2 root   root    16K Jun 23 10:52 lost+found
drwxr-xr-x   6 100000 colord 4.0K Oct 18 09:21 media
drwxr-xr-x   2 100000 colord 4.0K Jun 21 11:10 mnt
drwxr-xr-x   4 100000 colord 4.0K Sep 25 09:32 opt
dr-xr-xr-x 184 root   root      0 Nov 23 09:20 proc
drwx------   5 100000 colord 4.0K Sep 12 13:28 root
drwxr-xr-x  29 root   root    940 Nov 23 09:20 run
drwxr-xr-x   2 100000 colord  12K Nov  7 08:46 sbin
drwxr-xr-x   2 root   root   4.0K Apr 29  2017 snap
drwxr-xr-x   2 100000 colord 4.0K Jun 21 11:10 srv
dr-xr-xr-x  13 root   root      0 Nov 23 09:20 sys
drwxrwxrwt   9 root   root   4.0K Nov 23 09:21 tmp
drwxr-xr-x  10 100000 colord 4.0K Jun 21 11:10 usr
drwxr-xr-x  12 100000 colord 4.0K Jun 22 11:33 var
lrwxrwxrwx   1 root   root     30 Nov 21 09:04 vmlinuz -> boot/vmlinuz-4.10.0-40-generic
lrwxrwxrwx   1 root   root     30 Oct 31 09:04 vmlinuz.old -> boot/vmlinuz-4.10.0-38-generic

Surely that's not right, why are all those folders assigned to "100000 colord"?
Can I just chown them to "root root"?
Should I log a bug? This is just a vanilla install of KDE Neon User Edition.

I had a similar issue on initial install with "sudo" as well (that was logged as a bug, which I can't find right now).

It must have been an update or something that did this, I certainly didn't do it (well, not intentionally).
I used the following BASH script to correct, may be of use to some:

Code: Select all

#!/bin/bash

# Skipping /proc as that causes issues
# Skipping /media to prevent spidering of any mounted network shares
find / -mindepth 1 -maxdepth 1 ! -path "/proc" ! -path "/media" |
while read rootFolder
do
        echo "Checking ${rootFolder}"

        find ${rootFolder} -nouser |
        while read filename
        do
                echo "Fixing ${filename}"

                if [ -L ${filename} ]
                then
                        chown -h root:root ${filename}
                else
                        chown root:root ${filename}
                fi
        done
done