Re: DCOPServer could not be started

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: DCOPServer could not be started
by hansa on Monday 28/Oct/2002, @05:28

One of my colleagues had this problem.
It appeared that she was out of disk space (due to quota limitations).
When logging in, the system could not make a .DCOPserver_hostname:0 file under her account that contains data about the sockets KDE uses.
Starting KDE, the system starts looking for this .DCOPserver_hostname:0 file, which is not there (of course).
This generates the error.

Raising the quota, or deleting some files is a solution here.

Related Links

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

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

Re: DCOPServer could not be started
by Rusty on Wednesday 06/Nov/2002, @19:01

That worked for me. Thanks. I am using Bastille and that turned on quotas.

[ Reply To This | View ]

Re: DCOPServer could not be started
by mavis on Wednesday 04/Jun/2003, @00:08

But that don't worked for me!
Help me!

[ Reply To This | View ]

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


		"Karate is the ideal counterpart to programming and really great to get your head cleared." -- Michael Brade
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.