The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: DCOPServer could not be started/ LOGIN FAILURE
by Saumil Mehta on Friday 16/May/2003, @01:35
|
Hello all,
I am facing (it seems) the mother of all the problems described in this thread. I am running KDE using RedHat 7.3 on Linux. I logged in just fine to KDE, but tried to use KUser to add a new user - this gave me an error message saying that "error in /my/path/dcopserver_<machinename>_0 make sure dcopserver is running".
Not sure what to do, I went ahead and added the user alright and tried to log out of X to see if I could reboot and figure something out. Big mistake - I have not been able to log in _AT ALL_ ever since. I have tried both Runlevel 5 and 3 and _no_user_ can log in, including root (me). I am currently reduced to Runlevel 1 and have tried bizarre things to no avail. First, deleteing .ICE-UNIX or .Xauthority did not do anything for me. I also deleted some files to free up space. Finally, I managed to get dcopserver running on Runlevel 1 but of course as soon as I say "telinit 3", it seems to wipe it out. If I reboot, it automatically shuts down dcopserver. Is there anything I can do to avoid this problem? I can possibly write a script in /etc/rc.d/rc3d that tries to start up dcopserver (and switch at boot to runlevel 3) but I wonder if that would do any good.
Please - any suggestions or pointers will be greatly appreciated.
Regards
SAUMIL MEHTA
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started/ LOGIN FAILURE
by Ovidiu on Friday 12/Nov/2004, @02:50
|
I recently ran into a similar problem: a message box informed me that I should make sure that the "dcopserver" is running and then the desktop login failed.
The cause of this in my situation was that the owner of the file .ICEauthority was set to root:root. How did it get set to that? Couldn't figure it out (maybe I ran something as root in my home dir).
The fix is simple. Login as root and issue
chown myuser:myuser .ICEauthority
(where myuser is, of course, your user name :) )
Cheers,
Ovidiu
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started/ LOGIN FAILURE
by john on Saturday 19/Nov/2005, @05:58
|
Hi I am facing similiar problems. I have three logins two users a1 and a2 and a root. With login a1 I am able login, but with other login a2 I am facing similiar problem. I tryied to change the owner ship on .ICEauthority file. now the problem is if I try to login as root it overwriting .ICEauthority filr for login a2, because of that root login is also failing. Any suggestion to avoid this issue.
-- john.
|
[
Reply To This | View ]
|
|
Re: DCOPServer could not be started
by Geoff Gibbs on Tuesday 02/Mar/2004, @02:55
|
Yes! We had the same problem with DCOP on a
bunch of Sun Rays, which have a bunch of users
on one server. The first user to fire up KDE
ends up creating /tmp/.ICE-unix/ and of course,
they own it. The next user is unable to write
to the directory! When this is fixed the next
user can run KDE. I guess that the directory
should be owned by root with world write?
Geoff Gibbs
|
[
Reply To This | View ]
|
Re: DCOPServer could not be started
by anonymous on Tuesday 02/Mar/2004, @07:00
|
Please see http://wiki.kdenews.org/tiki-index.php?page=Performance+Tips and search for ICE-unix.
|
[
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)
