master.sh does not set permissions when installing. This results in logout/login or rebooting not actually causing the themes to appear in the settings manager after installation or re-installation.
Resolved by running:
find ${INSTALL_DIR} -type d -exec chmod o+rx {} \;
find ${INSTALL_DIR} -type f -exec chmod o+r {} \;
for each install directory:
/usr/share/plasma
/usr/share/aurorae
/usr/share/color-schemes
/usr/share/konsole
/usr/share/konversation
/usr/share/Kvantum
/usr/share/plasma
/usr/share/wallpapers
/usr/share/yakuake
After updating permissions and logout/login, everything appears correctly. Expressed in manjaro Sikaris 22.0.0 (manjaro fully updated to 2022-10-17).
/etc/login.defs (unchanged):
$ grep UMASK /etc/login.defs
106:# UMASK Default "umask" value.
116:UMASK 077
User effective UMASK:
install.sh does not control file permissions, and is affected by the current user's UMASK on installation/removal (something, something, executing remote shell scripts with pipe). Meaning users with a 0022 umask will find install.sh works properly, while those with other umasks (such as 0027) will not.
I believe this to be an actual arc-kde issue; as there should not be an assumption of what a given user's UMASK is.
master.sh does not set permissions when installing. This results in logout/login or rebooting not actually causing the themes to appear in the settings manager after installation or re-installation.
Resolved by running:
for each install directory:
After updating permissions and logout/login, everything appears correctly. Expressed in manjaro Sikaris 22.0.0 (manjaro fully updated to 2022-10-17).
/etc/login.defs (unchanged):
$ grep UMASK /etc/login.defs 106:# UMASK Default "umask" value. 116:UMASK 077User effective UMASK:
$ umask 0027install.shdoes not control file permissions, and is affected by the current user's UMASK on installation/removal (something, something, executing remote shell scripts with pipe). Meaning users with a0022umask will findinstall.shworks properly, while those with other umasks (such as0027) will not.I believe this to be an actual arc-kde issue; as there should not be an assumption of what a given user's UMASK is.