Can't login into KDE: DCOPserver problem for *all* users.

Doctafonk · 01-13-2008, 06:26 PM

Hi All

Im at the end of my troubleshooting and I need some help.

I am running a fresh install of Fedora 8 and recently I cannot log into KDE at all.
After trying to log in, I get the following error message:

Quote:

There was an error setting up inter-process communications for KDE. The message returned by the system was:

Could not read network connection list.
/home/<user>/.DCOPserver_<myservername>__0

Please check that the "dcopserver" program is running!

Now, this is a very google-able error, but of all the reading Ive done, I still cannot seem to fix the problem.

The difference between my problem and others Ive read is that it happens
to me for *all* users, including root. So far I have tried the following troubleshooting steps:

Checked that /tmp/.ICE-unix has 777 permissions and is owned by root.

Ive tried manipulate files within /tmp (chaning permissions, ownership etc) as well as totally renaming /tmp.

I sometimes get different error messages, but nothing so far has actually fixed it.

Ive tried unistalling and re-installing kde (using "yum remove" and "yum install"). Same problem.

Ive added new, test users and Im still getting the same error with these users.

I cant for the life of me think of what I did to cause this in the first place.
Does anyone have any more suggestions?

TIA
Matt

Emerson · 01-13-2008, 08:18 PM

As you describe it there has to be a corrupted file in kde directory. I'd uninstall KDE again, manually rm -rf kde directory and reinstall. Uninstall usually does not remove modified files.

Doctafonk · 01-13-2008, 10:00 PM

Emerson, good idea. But unfortuantely still no go. Here's what I ded:

I unistalled everything then searched my system for anything kde related. I then deleted:
- everything in /tmp
- everything in /var/tmp
- everything kde related in the user directories (including root)
- /usr/share/applications/kde/
- /usr/include/kde
- /usr/lib/kde4

But after then after a clean install (with yum), I get the same error!

Do you know if there is anything else I should be deleting?

Emerson · 01-13-2008, 10:09 PM

/usr/kde

Does your distro have it?

Doctafonk · 01-13-2008, 10:31 PM

actually, no it doesnt

Emerson · 01-13-2008, 10:38 PM

Hmh, something is rotten here now. I did a quick ssh to my wife's puter - she has KDE - and she has all directories you do plus /usr/kde. Could you boot your computer from some LiveCD and run filesystem check?

Doctafonk · 01-13-2008, 10:50 PM

Im pretty sure this disk is ok. This is actually a replacement of a corrupted HDD and I made sure to do a check before I started installing anything (a few days ago). And Ive had no other instability problems with anything else.

I really dont want to re-install the whole OS (again) because of this problem

BTW, here's what is remaining on my system related to kde:

Code:

find / -name kde*

/usr/kerberos/bin/kdestroy
/usr/kerberos/man/man1/kdestroy.1.gz
/usr/include/linux/kdev_t.h
/usr/share/switchdesk/pixmaps/kde.png
/usr/share/doc/krb5-workstation-1.6.2/kdestroy.html
/usr/share/doc/nss_ldap-257/pam.d/kde
/usr/share/backgrounds/tiles/kde_passion.jpg
/usr/share/pixmaps/comps/kde-desktop.png
/usr/share/pixmaps/comps/kde-software-development.png
/usr/src/kernels/2.6.23.9-85.fc8-i686/include/asm-i386/kdebug.h
/usr/src/kernels/2.6.23.9-85.fc8-i686/include/linux/kdev_t.h
/usr/src/kernels/2.6.23.9-85.fc8-i686/include/linux/kdebug.h
/usr/src/kernels/2.6.23.9-85.fc8-i686/include/asm-generic/kdebug.h
/usr/src/kernels/2.6.23.1-42.fc8-i686/include/asm-i386/kdebug.h
/usr/src/kernels/2.6.23.1-42.fc8-i686/include/linux/kdev_t.h
/usr/src/kernels/2.6.23.1-42.fc8-i686/include/linux/kdebug.h
/usr/src/kernels/2.6.23.1-42.fc8-i686/include/asm-generic/kdebug.h
/usr/lib/openoffice.org/program/kde-open-url

Emerson · 01-13-2008, 11:00 PM

Dear Doctafonk.

You had hardware problems and you replaced HDD. Now your KDE is malfunctioning. If I was Sherlock Holmes I'd say I do not believe in coincidences. But my name is not Sherlock and it's rather late here.

Good luck.

Edit: How did you get to Tokyo from Sidney that fast?

Doctafonk · 01-13-2008, 11:15 PM

um...this is a brand new disk that I have already fsck'd without finding errors.
Im not sure what else it could be.

PS: Fast flight