[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sheflug] KDE DcopServer Problems



Hi Alan,

We only encountered this problem when attempting to connect to a 
remote server via NFS. The /home directories were on the remote 
machine, and we *think* that some kind of RPC problem caused the 
aggro.

I suggest logging onto a root shell and creating a new user, and then 
see if you still have problems with that user starting up KDE then. 
This is to make sure there aren't any hidden dcop related kludges in 
that user's home. (Alternatively, try logging on from the shell as an 
existing user and expunging any .DCOP* and related hidden files from 
that user's home directory.)

Those pesky hidden files from the old version of KDE *may* be 
annoying the new version.

Just in case those files are vital (I'm pretty confident they aren't, 
but you can't be too careful) you can always delete the new user and 
start again with another test. (If you opted to move all of those 
.DCOP* files to .DCOP*.bak on an existing user, it'll be a bigger 
hassle to put everything back where it should be - I reckon it's 
probably quicker to make a new user for test purposes).

There's also a hidden directory called ".mcop" which could be 
worthwhile to back up or get rid of.

If I'm right, all of these hidden files and directories will be 
remade by KDE once you successfully log in. I *think* I vaguely 
remember that these files are all kludges created by KDE to solve a 
known dcopserver error... But kludges are notorious for 
future-incompatibility!

Let me know how you get on.

Personally, I've found that we have had so many upgrade glitches that 
the only real answer is to keep /home on a separate drive and 
reinstall the whole distro each time you want to upgrade. It's harsh, 
but these problems can be intractably complex if you're working with 
many machines.

Good luck!

James
=====

>Hi James,
>
>Any help would be really apprecated thanks.
>
>Well I've had this problem for a while.  I started with Mandrake 8.0 on
>a stand alone PC, everything worked fine (that was KDE 2.1.1)  Then I
>upgraded to the Beta relase of KDE 2.2 from the internet, that worked
>fine.  The problems started when I tried to go from KDE 2.2 to KDE 2.2.1
>Which I've tried RPM's for Mandrake 8.0 (from the KDE website) and in a
>final last ditch attempt I upgraded from Mandrake 8.0 to 8.1 and used
>the binaries that came with the distro.  Still no luck I'm afraid, but
>every time I have tried it has been on top of the old version, i.e. I've
>not formated my hard drive and done a complete rebuild.
>
>I'm not trying to connect to a remote server at all, but I did try and
>configure my box to be able to connect to a LAN (to no avail as my
>Network card isn't supported) so it is possible that I still have some
>networky stuff lieing around causing problems.
>
>If my .xsession-errors file would help too, let me know.
>
>Thanks
>
>
>Alan
>
>On Fri, 2002-02-01 at 18:06, James Wallbank wrote:
>>  Hello Alan,
>>
>>  DCOPserver problems are our speciality! We had loads of DCOPserver
>>  errors using Mandrake 7.2 at Access Space. We solved them by
>>  upgrading to Mandrake 8.0, but in fact you *can* get a 7.2 patch from
>>  mandrake.com or kde.org as I remember.
>>
>>  What distro are you using?
>>
>>  Are you installing KDE on top of an existing distro, or is it bundled
>>  in with the distro on a fresh install?
>>
>>  Are you trying to connect to a remote server when you start KDE, or
>>  is yours a standalone machine?
>>
>>  Will try to help more when I know more.
>>
>>  Cheers,
>>
>>  James
>>  ======
>>
>>  >Can anyone help me, I seem to be in a bit of an old chicken and egg
>>  >situation.
>>  >
>>  >I'm still having problems getting KDE to start up.
>>  >
>>  >When I start KDE I get an error telling me that the "DCOPserver" isn't
>>  >running and to remove .DCOPlocalhost.localdomain:0 from my home
>>  >directory.
>>  >
>>  >So I do that and start the dcopserver from the command prompt and KDE
>>  >will then get to the part where it starts kwin but I then get a message
>>  >like the following in my .xsession-errors file.
>>  >
>  > >DCOPserver all ready running
>>  >
>>  >I've tryied starting KDE with or without the dcopserver running and
>>  >neither seem to get me into KDE, has anyone else had a simular problem
>>  >or know what is going on ?
>>  >
>>  >Any Ideas at all would be much appreciated.
>>  >
>>  >Thanks
>>  >
>>  >Alan
>>  >
>>  >
>>  >___________________________________________________________________
>>  >
>>  >Sheffield Linux User's Group - http://www.sheflug.co.uk .
>>  >To unsubscribe from this list send mail to
>>  >shef-lug-request [at] list.sheflug.org.uk with the word
>>  >"unsubscribe" in the body of the message.
>>  >
>>  >   GNU the choice of a complete generation.
>>
>
>
>___________________________________________________________________
>
>Sheffield Linux User's Group - http://www.sheflug.co.uk .
>To unsubscribe from this list send mail to
>shef-lug-request [at] list.sheflug.org.uk with the word
>"unsubscribe" in the body of the message.
>
>   GNU the choice of a complete generation.

-- 
who: James Wallbank
org: Redundant Technology Initiative
tel: +44 114 2495522
fax: +44 114 2495533
eml: rti [at] lowtech.org
web: www.lowtech.org
loc: Access Space
      1 Sidney Street
      Sheffield
      S1 4RG
      UK
___________________________________________________________________

Sheffield Linux User's Group - http://www.sheflug.co.uk . 
To unsubscribe from this list send mail to 
shef-lug-request@list.sheflug.org.uk with the word
"unsubscribe" in the body of the message. 

  GNU the choice of a complete generation.