The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: DCOPServer could not be started
by Niko on Monday 20/Jan/2003, @13:50
|
On my computer the problem occured because of a crash of the whole system.
removing /tmp/.ICE_unix directory and the ~/.DCOPserver_<machinename>_-0 worked for me.
thanks!
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by Tan Hong Cheong on Monday 07/Apr/2003, @18:10
|
removing /tmp/.ICE_unix directory and the ~/.DCOPserver* also worked for me.
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by Kevin C. on Friday 15/Aug/2003, @09:42
|
This worked for me, cheerz!
|
[
Reply To This | View ]
|
|
Re: DCOPServer could not be started
by silence on Tuesday 07/Oct/2003, @16:17
|
on my machine (mandrake 9.1) the problem was that it was configured to get a hostname (which looked like this: 1,6,<mac-address of my nic>) from the dhcp server of my isp, which dcopserver seems quite to dislike.
the solution was to enter a hostname in /etc/hostname and to prevent dhcp from resetting it. to achieve this you just have to open /etc/sysconfig/network-scripts/ifcfg-eth1 (in my case eth1 is the nic connected to my cable modem) and change the line "NEEDHOSTNAME=yes" to "NEEDHOSTNAME=no"
silence
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|