This is the third computer that this has happen on using FC3 and right after getting the latest
updates , the three computers where using ,Nvidia,ATI,SIS video cards,Pentiums and
AMD athlons.
After this happen I set Selinux to disabled, but I still can't get back into Gnomeor KDE.

After I login I get this message
could not start kdeinit. Check your installation
if i close the message, this appears
could not read network connection list
/hone/kay/.DCOPserver_kay_0
i get another message that says
ACPI Unable to locate RSDP
next message is there was an error setting up
inter-process communications for KDE. The message
returned by system was: Please check that the
"dcopserver" program is running
I hit ok and it returns me to login window

When I login to Gnome I get the following messages
The application "nautils" has quit unexpectedly. You
can inform the developers of what happened to help
them fix it. Or you can restart the application right
now
three choices
Restart application XClose Inform Developers
I clicked the restart button and Gnome appears, but
not correctly. An application menu lets me do a
little in Gnome. No icons and most programs do not
work.

I sure hope someone can figure this out ,it's not helping me to
support Linux when my friends see this happening.

Thanks

Jim

I had this problem when migrating from Mandrake and it was because of file permissions. Under Mandrake my UID was 501, under Fedora it was 500, so I didn't own the files in my home dir. Doing a chown on everything (just chown -R * isn't enough as it doesn't do . files like .kde) fixed the problem.

Failing that, check that you can ping localhost and your network adapter and that you can ping your hostname.

Does Selinux change permissions ?
I t seems this problem happen each time a new Selinux Policy
change came out, on the three different computers that had problems.

Thanks

Jim

I have same error - what do you mean "Doing a chown on everything" please ??

Mel P

He was refering changing ownership of the files with the chown command.

You can type 'man chown' at the command prompt it will bring up a man page with the syntax on the command and usage.

Will look at that - thanks

Mel P

I am still having the problem. I use KDE applications on IceWM desktop. Comparing with another Mandrake 10.1 I observed that somehow my .DCOPserver file and some other files got deleted. How can I regenerate these files; the absence of which throws up the above error.

Thank you.

I would not worry about the DCOPServer file itself. This can be removed with out any fatal errors. It is mainly, it appears, communicating with the actual DCOP server itself and creating the new DCOPServer file. So it appears that this file cannot be created withing you home directory. If this is a id problem, I would go with the numerical uid.gid first. If you are the main user on the system, it would be safe to assume that your uid and gid are 500 . So

This should take care of all the permission issues, after this has been completed, I would suggest checking your setting in system-config-users or kuser. If there are any inconsistencies, correct them and reboot. Also, depending on what you are upgrading from it could be a different ID, most common are 500 501 and 1000. If the 500 does not work, I would try 1000 then 501.

I might not speak for everyone here when I say this, but if you are going to user a system for desktop use, I would strongly encourage you stay away from SELinux for now. It can cause many headaches (as I am sure you are aware), though it does appear to be progressing along nicely for server user.

there are 2 users on my system besides the root 500 and 501.

should i do a chown as root or as the respective user (500 or 501). doing a chown as a normal user returns messages for many files as "Operation not permitted".

why are there 2 chown commands, are both to be used.

what inconsistencies?


Thank you for the help already provided...looking forward to working on my linux box again but still a little help behind...Please help me.

Diabolic Preacher
As Is

p.s. there is a mandrake advisory about some vulnerability in kde 3.2.x do u think that is an affecting factor?