Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

master.sh does not set permissions; results in theme not appearing in settings. #140

Open
r-pufky opened this issue Oct 17, 2022 · 0 comments

Comments

@r-pufky
Copy link

r-pufky commented Oct 17, 2022

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:

$ umask
0027

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant