please check that the "dcopserver" program is running
alrighty here is the thing.
As with most newb's I am curious and always trying new things. I have been playing with ownership/permissions and in the process have lost rights to all /home folders respectively for my users. I am getting the error: quote: There was an error settuping up inter-process communications for KDE. The message returned by the system was: Could not read Network Connection List. //: .DCOPserver_stealth__0 Please check that DCOPserver program is running. I have tried (as per other posts and google findings): chmod -R +w /home/*username removing one file: /root/.ICEauthority su -c "chown $WHO:users /home/$WHO/.ICEauthority" exit where $WHO is the user Currently I can login as root and have no issues with KDE. When in a root shell and su to my main account 'thanotos' to try and view permissions that the user has, this is the return root@stealth:/home/windows# su thanotos bash: /home/thanotos/.bashrc: Permission denied thanotos@stealth:/home/windows$ cd bash: cd: /home/thanotos: Permission denied So all that I know for sure is that I do not have permissions for any of my users other than root. Nor can I change them back. Any suggestions would be appreciated. I really dont want to remove and readd users. |
Re: please check that the "dcopserver" program is running
Quote:
LMAO............... now that we got that out of the way........what are the permissions for "/home" ??? |
drwx--x--x 2 forlamp users 80 2005-11-04 18:40 forlamp/
drwxr-xr-x 2 root root 48 2005-07-14 05:14 ftp/ drwx--x--x 9 pickel users 400 2005-11-11 09:18 pickel/ drwx--x--x 2 test users 80 2005-11-11 13:23 test/ drwx--x--x 2 test2 users 80 2005-11-11 15:55 test2/ drwx--x--x 16 thanotos users 1024 2005-11-11 13:56 thanotos/ drwxr-xr-x 3 thanotos users 72 2005-11-04 09:57 windows/ looking at it everything looks good ...... (to me anyway) root@stealth:/# id uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel),11(floppy) Quote:
Appreciate the help. And I am glad that I could bring a smile to ones face with self induced suffering :D |
I've had this problem recently when changing from SuSE back to Slackware. I reused a disk for /home, since I wanted to keep the files on it, and the user names and groups didn't match up, so DCOP saw ownership and group problems. I knew there was a problem when I did 'ls -al' to look at the dotfiles in my home dir and the user and group shown were numbers instead of my login and a group name.
I fixed it by chown'ing the dotdirs and dotfiles in my home dir to my login and chgrp'ing them to 'users'. I didn't know how to do only the dirs and files, but not the parent dir, so I did it in a series of commands: chown -R my_login .a* .b* ... then: chgrp -R users .a* .b* ... If I did 'chown -R .*' it would have tried to do the parent dir (..) too. Maybe someone can chime in with an easier way, but this fixed the problem for me. Jim |
You could use find and chown the files appropriately
example for 1 user : Code:
# cd /home/thanotos |
appreciate the info,
I will post with the results and steps that resolved. (might be a day before anything is posted.....need sleep) |
I have spent the last couple of days trying to resolve this issue too. I eventually resolved it by setting my Home directory permissions to the default Home directory settings of 755 (I had other users to compare the settings with), i.e.
Owner: read, write, execute Group: read, execute Others: read, execute Hope this helps :cool: |
So here be a bit of an update.
keefaz = appreciate the solution, however it did not seem to work - whether I was not applying the info correctly or it just wants to be difficult. Here is an update: Code:
root@stealth:/# ls -l Code:
root@stealth:/# su thanotos |
All times are GMT -5. The time now is 02:59 AM. |