On 2018-07-01 19:35:46 William Morder wrote:
> Some command-line may work the magic you want. [Change ~ to your username!]
> � chmod -R 700 /home/~/.trinity | chown -R ~/home/~/.trinity | chgrp -R ~
> /home/~/.trinity
> and/or
> chmod -R 700 /home/~/.trinity/* | chown -R ~/home/~/.trinity/* | chgrp -R
> ~ /home/~/.trinity/*
> (This give rwx permissions to user only, dep or whatever you call your
> username.)
>
> If this doesn't work, try:
> chmod -R 770 /home/~/.trinity | chown -R ~/home/~/.trinity | chgrp -R
> ~ /home/~/.trinity
> and/or
> chmod -R 770 /home/~/.trinity/* | chown -R ~/home/~/.trinity/* | chgrp -R
> ~ /home/~/.trinity/*
> (This will give rwx permissions to user and group, both the same as your
> username; some processes may operate under your group name, not as user.)
>
> NOTE WELL that I am using ~ to represent your top-secret username (which it
> is better that you don't publish online, of course); the /* in this case
> represents everything inside that folder, so I need the asterisk for that.
> (I don't give out my own username to anybody, although I feel sure that all
> the 3-letter government agencies have got it by now.)
>
> If this doesn't solve your problems, then you might have some deeper
> issues. In the past, when I had similar experiences, I used to just
> reinstall my system; but nowadays I try to avoid doing that when possible.
>
> Bill

	Since this is an ownership issue, not a privileges issue, one should use

|	chown <user>:<group> <filepath>

to fix the ownership instead of changing the access privileges.

Leslie