The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
|
Over 40 comments listed.
Printing out index only. |
Re: DCOPServer could not be started
by Ralf Habacker on Wednesday 05/Jun/2002, @13:51
|
See http://cygwin.kde.org for howtos and mailing lists relating to the kde-cygwin project. I think this isn't the right place to ask for installation support.
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by mike on Friday 05/Jul/2002, @17:17
|
Did you ever find a solution to this? I noticed the QA deal, but that didn't seem to help me...
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by saurabh naik on Wednesday 31/Jul/2002, @05:37
|
I was getting the similer problem and was not able to login in KDE
now please tell me what is dcopserver is all about and why such a
problem occurs.
thanks
saurabh
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by Jared on Thursday 29/Aug/2002, @16:52
|
I use kde that is installed with RedHat 7.3 and I had the same problem. IT was because my path was screwed up. I needed to add /usr/X11R6/bin.
|
[
Reply To This | View ]
|
|
|
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.
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by Musa Williams on Wednesday 04/Dec/2002, @11:54
|
I don't know if you found anything out as of yet, but I had the same issue and resolved it by deleting both the /tmp/.ICE_unix directory and the ~/.DCOPserver_<machinename>_-0 link. Logged out and it worked fine. Trying to find out if KDE's bugzilla has a report on this as of yet
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by Kartik on Monday 13/Jan/2003, @08:31
|
Did you manage to get this sorted out? I am having the exact same problem...any help?
Thanks,
Kartik
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by Muammer on Wednesday 02/Apr/2003, @07:56
|
You must set the trust permision to the .ICE-unix directory under the /tmp.
|
[
Reply To This | View ]
|
|
|
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
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by Jim Forney on Thursday 27/Nov/2003, @08:11
|
Problem here is slightly different in that root and users (with accounts) other than me have no problem. Trying to log in as myself I run into the same DCOPserver problem though it seems. Problem started for no apparent reason; just simply was there one morning at startup.
I have tried removing myself as a user (500), then creating a new myself (502) did not help. Also removing the /tmp/.icw* directory mentioned above did not help. There is no .DCOP* file or link to be found in the affected home directory.
I have even tried removing the entire KDE, then reinstalling KDE but whatever the problem seems to be tied to files not affected by removing/reinstalling.
System(s) here use SuSE 8.2 on, the one in question is SMP with plent of gigs to spare on HD.
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by UltraOne on Thursday 18/Dec/2003, @17:09
|
I had a similar problem doing a Debian Sarge install (using the Debian Next-Gen installer). The problem was permissions on /usr/X11R6/bin, which contains the program iceauth, which (I think) dcopserver needs to start. As installed, the directory was owned by root:root, and permissions were set to drwx------.
I used CTRL+ALT+F1 to get a text terminal. Logged as root, and then `cd /usr/X11R6` and `chmod go+rx bin`. Permissions are then drwxr-xr-x.
I switched back to the X Server with ALT+F7, and login worked fine.
Hope this helps.
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by alexander on Saturday 14/Feb/2004, @18:58
|
I had the same problem with dcopserver but didn't find the solution here.
When fixing something under gnome I fixed dcopserver. I am running gentoo
and when I installed it I didn't set up /etc/hosts correctly. That made
an anoying message pop up in gnome and caused kde to crash. By adding
127.0.0.1 <mymachinename> localhost
all was well. Hope this helps someone out there.
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by bob wachunas on Thursday 25/Mar/2004, @11:12
|
i am having the same problem. i got around it by creating a new user account and logging in as that user.
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by Raga on Sunday 02/May/2004, @08:43
|
I am having the same problem with KDE 3.2 after some apt-get upgrade (debian/testing). I removed the ICE/auth files as someone here suggested - but kde-init --exit keeps giving me these errors:
/usr/X11R6/bin/iceauth: timeout in locking authority file /home/knoppix/.ICEauthority
DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
ICE Connection rejected!
DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
DCOPServer self-test failed.
ICE Connection rejected!
iceauth: timeout in locking authority file /home/knoppix/.ICEauthority
kdeinit: DCOPServer could not be started, aborting.
___
above actions where done while being logged in to kde as root. trying to login as user 'knoppix' created these 3 lines in auth.log:
May 2 17:11:46 AMD1800 kdm: :0[5141]: (pam_unix) session closed for user knoppix
May 2 17:16:01 AMD1800 CRON[5873]: (pam_unix) session opened for user knoppix by (uid=0)
May 2 17:19:41 AMD1800 kdm: :0[6925]: (pam_securetty) access denied: tty ':0' is not secure !
Maybe this gives a hint...
Thanks for any help
Raga
|
[
Reply To This | View ]
|
Solved!
by Raga on Sunday 02/May/2004, @10:07
|
Well, don't ask me why, but this is how I solved the bug:
1) create new user (root console: adduser <username>)
2) successfully login as new user with kde3.2
3) open root console
4) rm /home/knoppix/.ICE* and .DCOP*
5) cp /home/<new user>/.ICE* /home/knoppix/
same with .DCOP (only the file, not the link)
6) chown knoppix.knoppix /home/knoppix/.DCOP*
(same with .ICE*)
Instead of '*' I typed the <TAB> key until match.
I hope this helps somebody after me - and that the causing error will be detected soon. Before this I had tried to change the access rights to these files (no success) and to delete them (no successful recreation).
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by Sebastian on Friday 14/May/2004, @11:53
|
Maybe its not a direct reply but helpful in someways. After launching a kde session from kdm I get an error that the dcopserver could not be started. I am running the current debian/sarge. It seems that dcopserver is run as the same user login in. For locking purposes I believe it quite often occurs that application want to write to /tmp. So a user rights check gives me
drwxr-xr-x 6 root root 192 May 14 20:45 tmp
Okay so I add the sticky bit to /tmp via
# chmod u+t /tmp
Which gives me no solution. So I decide to change the rights to
# chmod 1777 /tmp
Which leaves me with
drwxrwxrwt 6 root root 192 May 14 20:45 tmp
And *whoa*: my login user can start dcopserver manually. Okay: Some people might say that I am digging a security whole and so on, but I do not want every user to write to their own ~/tmp directory but rather that my system gets back to work. Supposedly that package causing the trouble will be fixed one day *g. Hope that was of help
Sebastian
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by Angel Sosa on Sunday 16/May/2004, @18:07
|
I am getting the same error message in addition I am also getting "kdeinit communication error.
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by Yi-Kun Yang on Wednesday 02/Jun/2004, @08:44
|
Got the same problem. I am running Fedora Core I with multiple computers accessing home directory at the same time. I removed ~/.ICEauthority-c and
~/.ICEauthority-l then it works fine.
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by Oli on Thursday 24/Jun/2004, @12:07
|
I got the same message when starting konsole.
I use Gnome as the desktop manager, but I do use konsole and konqueror because I like them.
I got the message about the DCOPServer not running when I started konsole.
So I chmod'ed ~/.ICEauthority to a+rw and this way it works like a charm.
ICEauthority was for some reason owned by root.root.
hth,
Oli
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by zoline on Friday 25/Mar/2005, @18:51
|
I installed cygwin with Kde3 on my note.
First time it worked, but After several setting, startx repeted followings..
_KDE_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
iceauth: creating new authority file /home/?????/.ICEauthority
Could not load library! Trying exec....
DCOPServer self-test failed.
kdeinit: Launched DCOPServer, pid = 3736 result = 0
kdeinit: DCOPServer could not be started, aborting.
+ test -n ''
+ kwrapper ksmserver
Warning: connect() failed: : Connection refused
kdeinit: entering main
kdeinit: Warning, socket_file already exists!
KDEINIT_KIO_EXEC
I found that dcopserver couldn't find my home directory,
cause of my userid is korean using env LANG=ko_KR.EUC.
so i changed LANG to C.
Now it work fine..
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by temp-join on Monday 10/Apr/2006, @20:08
|
hi, I have encountered the similar problem when try to login KDE.
But have to clarify the point before explain the phenomenon,
that is: I have set the default shell as "tcsh" for my users and root.
default shell in REDHAT-7.3 is "bash".
in order to start kde, the only way for me is setting default shell back.
then problem is gone.
actually, I am used to work with tcsh,not familiar with bash.
For the more depth reason, should be solved by linux-developer.
hope help.
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by alex cox on Sunday 25/Jun/2006, @10:04
|
I think this happens when you are logged into linux as an ordinary, su to root and then use /sbin/shutdown instead of logging out in the conventional way (at least that's what has happened to me.
In the past, as root, I have solved this problem by creating a symbolic link thus:
ln ~/.DCOPserver_localhost.localdomain__0 /home/alex/.DCOPserver_localhost.localdomain__0
This link will be readable by ordinary users by default.
I'm not sure this is strictly speaking the proper solution but in the past it has worked. I came here to see if I could find anything better but I don't like the idea of messing around with those files, as mentioned above, so I will now try this again.
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by Darren on Tuesday 14/Nov/2006, @13:09
|
may be a bit late but I fixed it this way after trying many other suggestions here.
If you delete ~/.ICEauthority file(make a back up just in case) and restart your session. This did it for me. Not sure what the problem was though.
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by YOUR FRIEND GURU on Friday 05/Jan/2007, @15:34
|
please, REMOVE the f#$%&/ spaces from your HOSTNAME="DONOTUSESPACESHERE"
it works.
cheers,
~your friendly nearby guru
p.s. paranoid is a noob =)
|
[
Reply To This | View ]
|
|
|
Re: DCOPServer could not be started
by Ken Banks on Saturday 20/Jan/2007, @08:44
|
This problem has been plaguing me for a while now, but I finally squelched it.
FIRST let me clarify how I was seeing these same errors:
I would connect to a server using VNC as a normal user. From there I would su as root and start a Konsole. After this, I would begin to see these errors everytime I attempted to start a Konqeror, or just about any other command that I typed into the Konsole. I basically could get anywhere from there even though I was root.
SOLUTION: As root, I could, however, remove ~/.DCOP*, then I closed out my Konsole session and simply performed another 'su' to start another Konsole. Everything has worked fine ever since. Somewhere along the way, these ~/.DCOP* files had gotten corrupted after a server crash, I think, and couldn't be corrected, until I completely removed them. I hope this helps!
Ken Banks
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by pingu on Monday 29/Jan/2007, @02:43
|
The solution is to change the hostname in the next FILES:
/etc/hostname
/etc/hosts
/etc/mailname
/etc/init.d/knoppix-autoconfig
The hostname can't contain special symbols, like space,....
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by Ali Ayoub on Monday 04/Jun/2007, @01:34
|
try adding this line on top of $HOME/.vnc/xstartup
"""
ICEAUTHORITY="$HOME/.ICEauthority"
"""
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by jim on Thursday 10/Jan/2008, @10:35
|
i just ran into this using kde on aix.
i finally tracked MY problem down to laziness on my part.
i am using dhcp on this install, and after i successfully
got an ip address, i added it to /etc/hosts with my machine's
name (this machine will pretty much be up all the time and
i don't expect the ip address to change).
so i added:
x.x.x.x myname
but i really needed to add a fully qualified name as well,
so i changed the line to:
x.x.x.x myname myname.fully.qualified.com
that fixed it.
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
