[Slackbuilds-users] transmission messes up permissions

[Robby Workman]

On Sun, 31 Jul 2016 23:41:33 -0300
Edgardo P <villa.ballester at gmail.com> wrote:

> I installed transmission in Slackware64 14.2 and changed lots of
> permissions, making the system unusable for non root users.
> 
> I have a log from the build script, but I'm not sure if I have to
> attach it here or not.
> 
> I could fix this partially reinstalling aaa_base, but X is broken too.


I just built transmission and the package has correct permissions
throughout. I'm reasonably certain that one of these two things
is the case:

1) Your normal user account has a non-standard umask setting,
   i.e. NOT 0022, which is fine on its own, but when you 
   switched to root to build the package, you used "su" as
   as opposed to "su -" and root's umask didn't get set.

2) Your root account has a non-standard umask setting,
   i.e. NOT 0022, which is NOT fine. 

You should be able to fix it with something like this:

for i in $(tar tf /tmp/transmission-2.92-x86_64-1_SBo.tgz | grep /$);
  do [ -d /$i ] && chmod 0755 /$i ; done
chmod 1777 /tmp
rm -rf /tmp/*
reboot

-RW

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160801/3452b09e/attachment.asc>