The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: DCOPServer could not be started
by Sam on Sunday 04/Aug/2002, @04:47
|
Did anyone find a fix for this error, I'm getting it too.
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by ralf habacker on Monday 05/Aug/2002, @05:07
|
See http://kde-cygwin.sourceforge.net/faq/kde2.php#D3.1
Ralf
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by Mike on Tuesday 10/Sep/2002, @15:08
|
I was having this same problem, but only when I logged in as a non-root user. I was not able to find anything that helped at http://kde-cygwin.sourceforge.net. After messing with it for quite a while on my Solaris 8 box I got it to work by chmod 01777 on /tmp/.ICE-unix, /tmp/.X11-pipe, and /tmp/.X11-unix. As best as I can tell, this gives the non-root user enough rights to create the files unix domain sockets stores established sockets in for Solaris. The problem is that these permissions get reset on boot so I had to create a small script to fix this. Hope this helps.
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by vincent on Saturday 02/Apr/2005, @03:11
|
I am having exactly same problem as you for my Solaris 10. The kde version is 3.3.1a that was install from my Solaris 10 companion CD. Could you please tell me your script-:)
cheers
|
[
Reply To This | View ]
|
|
Re: DCOPServer could not be started
by Nils Boysen on Saturday 22/Nov/2003, @07:21
|
hi,
I recently installed 2 Debian testing machines and encountered the same problem. Seems like the permissions of the directory "/usr/X11R6/bin/" are screwed up.
This helped me:
chmod go+rx /usr/X11R6/bin/
hope this helps.
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by Andy Ritchey on Thursday 20/Apr/2006, @21:42
|
I am using slackware 10.2 and this seemed to work. I tried some other methods posted here saying to remove various files but that led to more trouble. Thanks for the help.
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|