Re: DCOPServer could not be started

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: DCOPServer could not be started
by Phil Vossler on Monday 01/Sep/2003, @03:20

I had the same trouble last week and tried the solutions listed here. None appeared to work.

I could run kmail and other kde apps as root but not as the (only) existing end user. In the end I used "chown" and chowned all the files in the users home directory.

E.G. "cd /home/jack ;chown -R jack.jack ."

that worked.....why i dont know but I didnt have the time to delve in to the detail I just needed it functioning.

regards
Phhil

Related Links

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

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

Re: DCOPServer could not be started
by dt on Friday 12/Sep/2003, @11:45

Same problem, different solution...

A nasty install script clobbered my /etc/ld.so.conf file and it was missing critical ld library paths (such as /usr/X11/lib). Here's what mine contains:

sh-2.05a$ cat /etc/ld.so.conf
/usr/local/lib
/usr/X11R6/lib
/usr/i386-slackware-linux/lib
/opt/kde/lib
/usr/lib/qt/lib

Hope that helps anyone that remains stuck.

dt

[ Reply To This | View ]

Re: DCOPServer could not be started
by wathavy on Wednesday 28/Sep/2005, @17:27

Thanks to Phhil's.
Worked out fine.

chown -R uname:uname .

Bye.
wathavy

[ Reply To This | View ]

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


		"No fake - I'm a big fan of konqueror, and I use it for everything." -- Linus Torvalds
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.