I think this is caused by a permission leak coming from the maintainer's system. I've successfully made an ISO without these problems just by following steps detailed in https://wiki.archlinux.org/index.php/Archiso and making sure to keep file permissions right. To keep them right some adjustments have to be made. Command:

# cp -r /usr/share/archiso/configs/profile/* ~/archlive

needs to be altered by adding the -a switch:

# cp -ar /usr/share/archiso/configs/profile/* ~/archlive

Also, if the maintainer uses ACLs, they need to be removed before copying anything into ~/archlive with:

# setfacl -b ~/archlive

However, I think it'd be better to build ISO images in a clean chroot, as it's the case for packages in Parabola repositories.

May I ask the hacker in charge of creating ISO images to build a new one, with the issues I've described fixed?

niitotantei wrote:

May I ask the hacker in charge of creating ISO images to build a new one, with the issues I've described fixed?

I would also like that, this problem keeps messing with me...

niitotantei wrote:

There are problems with file permissions on the live system:

• Some files/directories are owned by a nonexistent user/group 1003, for instance:
  [...]
  Incorrect ownership makes e.g., sudo emit warning messages.
• Many directories have default ACL entries set, for instance:
  [...]
  This pollutes file permissions when files are moved from the live system to the installed system, e.g., when moving files from /root to /mnt.

is this fixed in the current iso/a way to fix it for the current iso...