Re: DCOPServer could not be started

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: DCOPServer could not be started
by Sebastian on Friday 14/May/2004, @11:53

Maybe its not a direct reply but helpful in someways. After launching a kde session from kdm I get an error that the dcopserver could not be started. I am running the current debian/sarge. It seems that dcopserver is run as the same user login in. For locking purposes I believe it quite often occurs that application want to write to /tmp. So a user rights check gives me

drwxr-xr-x 6 root root 192 May 14 20:45 tmp

Okay so I add the sticky bit to /tmp via

# chmod u+t /tmp

Which gives me no solution. So I decide to change the rights to

# chmod 1777 /tmp

Which leaves me with

drwxrwxrwt 6 root root 192 May 14 20:45 tmp

And *whoa*: my login user can start dcopserver manually. Okay: Some people might say that I am digging a security whole and so on, but I do not want every user to write to their own ~/tmp directory but rather that my system gets back to work. Supposedly that package causing the trouble will be fixed one day *g. Hope that was of help

Sebastian

Related Links

·   Articles on KDE on Unix and other platforms
·   Also by Sebastian
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )


		"I ride my bicycle." -- Michael Häckel
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.