On 17/07/2014 23:31, Dale wrote: > Alan McKinnon wrote: >> On 17/07/2014 21:42, Dale wrote: >>> Alan McKinnon wrote: >>>> On 16/07/2014 18:45, Volker Armin Hemmann wrote: >>>>> easiest way to test: new user. Copy over config files until problem >>>>> occurs. >>>> <doh> >>>> Yes of course, that's the best way. Didn't think of that >>>> >>>> >>> I just did my KDE upgrade so I renamed the .kde4 directory. I logged >>> in, set up enough that I could test things and then logged out. When I >>> logged back in, it worked like it should. Let's see how long that lasts. >>> >>> Alan, make sure you change the permissions on those file. I have a test >>> account that I rarely use as well. In the past, I had to change the >>> owner from dale to dale2 which is my account names. Usually the group >>> is the same so the owner is all that needs changing. >> Why change the permissions? They must be rw for the user using them >> which means chmod 6xx, the group being entirely irrelevant as it will >> never be referenced. If the new user is doing the copy then they will be >> owned by that new user anyway. "cp -a" will just always do the right >> thing in this case :-) >> >> > > Well, I usually copy as root which leaves the permissions the same. > Since you do it as user then you are right.
DO NOT DO THAT COPY AS ROOT. That's just needlessly asking for trouble. Do it as the destination user, as long as it can read the source user's home dir it all works out fine. Group membership is usually sufficient and the only case where it's an issue is if home dirs are set to rwx------ or encrypted -- Alan McKinnon [email protected]
