faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: DCOPServer could not be started
by Dremus on Wednesday 09/Oct/2002, @22:23
|
I've got the same problem with my SuSE Linux 7.3:
Starting Linux and X-Server will show me the graphical login-screen. I switch to Textmode [Ctrl-Alt-F3], login as root and start the text-based setup-tool YAST.
I searched for installed packages with "dcopserver", deinstall & reinstall it and shutdown the computer.
After starting again, everything works fine (until the next time error ??). I can't explain it, because I'm Linux-newbie. May be, specialists will do it for me. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
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.
|
[
Reply To This | View ]
|
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 )
|
|