search

free-wheeling / freewheeling

Freewheeling Live Looper
http://freewheeling.sourceforge.net/
GNU General Public License v2.0
107 stars 7 forks source link

config doesn't have the right permissions #10

Closed magnetophon closed 7 years ago

magnetophon commented 7 years ago

After #9 happened, I got:

INIT: Copying all config files from shared folder...
Backing up your old configuration to: /home/bart/.fweelin/basics.xml.backup.1
INIT: Copying: cp "/home/bart/.fweelin/basics.xml" "/home/bart/.fweelin/basics.xml.backup.1"
INIT: Copying: cp "/nix/store/17g8x2bd9sv3c30v4ld28ldpzr7r513p-freewheeling-2017-04-03/share/fweelin/basics.xml" "/home/bart/.fweelin"
cp: cannot create regular file '/home/bart/.fweelin/basics.xml': Permission denied

And similar lines for the other config files. Ending with:

CONFIG: Reading new config...
INIT: ERROR: Config in install dir is not up to date!
Did you run 'make install'?

These didn't go away until I manually changed the permissions.

bill-auger commented 7 years ago
magnetophon commented 7 years ago
bill-auger commented 7 years ago

the error from cp kinda says it all

cp: cannot create regular file '/home/bart/.fweelin/basics.xml': Permission denied

the program gets $HOME from the user's environment so that strongly indicates that the user running the program was 'bart' and bart did not have permissions in bart's ~/.fweelin dir - if you had freewheeling installed before the most likely thing that happened was that the permissions on the orphaned ~/.fweelin dir got changed somehow at some time - if you can make it print "cp: cannot create regular file '/home/bart/.fweelin/basics.xml': Permission denied" again i would be interested to see what the output of ls -al /home/bart/.fweelin/ looks like immediately afterward

i would not be too concerned about this unless it happens again - it seems like a fluke but it could be made more robust if need be - if you would like to experiment, you can delete that entire directory at any time if you like and run the program again - it is harmless unless you made customizations in there - it will just reset everything

rm -rf /home/bart/.fweelin/

perhaps also uninstall the package and make sure the nix buld dir gets deleted too (to force it to rebuild) then try to reproduce the issue - we can always re-open the issue if you can make it happen deterministically

*** UNINSTALL THE PACKAGE PROPERLY BEFORE RUNNING THE NEXT COMMAND ***
rm -rf /nix/store/17g8x2bd9sv3c30v4ld28ldpzr7r513p-freewheeling-2017-04-03/

btw - the defualt perms for that dir are 700 and all files under it are 644 on my system - you should be able to set it like that with no trouble

chmod 700 /home/bart/.fweelin/
chmod 644 /home/bart/.fweelin/*
magnetophon commented 7 years ago

OK, thanks.

bill-auger commented 7 years ago

oh also i was going to ask - do you plan to submit your nix recipe to nix? i see that they have been packaging it for years a very old version

in any case i would be happy to accept a PR with the nix recipe in the ./packaging dir once it works well

magnetophon commented 7 years ago

Yeah, I wanted to upstream it, but atm it barely runs.