KWrite thinks it is running as root

[probonopd]

Tried to bundle KWrite. Result:

linux@linux:~/makeaoi> ./kwrite-x86_64.AppImage 
Executing KWrite as root is not possible. To edit files as root use:
SUDO_EDITOR=kwrite sudoedit <file>

linux@linux:~/makeaoi> ./testdir/AppRun 
Executing KWrite as root is not possible. To edit files as root use:
SUDO_EDITOR=kwrite sudoedit <file>

[lvml]

Some applications just don't know the great "user namespaces" kernel feature yet, and wrongly assume that "pid = 0" necessarily means you have privileges...

At this time I have no better idea how to fix this than changing kwrite to have a look at /proc/self/uid_map to find out it is "root" only in his very own user namespace.

Try unshare -r chroot / /bin/bash - bash will also think you are "root", while you are not.
If anyone knows how to make a process that was started like this to use the "original" PID of the user who invoked "unshare", please let me know...

[probonopd]

Do we have to run as PID 0?

[lvml]

The "chroot" only works if the user is mapped to PID 0 in the user namespace, that is the only weird reason for the whole "unshare" use.
Theoretically, the processes started inside the chroot environment could well run under the normal PID of the user - but I have not yet found a good way how to do this.

[lvml]

Labelled this "help wanted" to signal that good ideas how to avoid software inside an "unshare -r chroot ..." environment to think it runs as "root" would be welcome.