Hi Brian, Well asked. I remember having a similar problem a while back, with KDE 3.1 after I compiled it from source myself (on a Debian system, not that it's relevant). Anyway, I don't think anything is fundamentally broken - I seem to remember, although it was quite some time ago and my memory is fuzzy, that I had an environment variable set wrong somewhere. Unless I am getting mixed up, which is quite possible, I think I added something to the /usr/local/bin/startkde script (maybe be in /usr/bin on your system?) setting KDEDIR=/usr/local/ (for that is where I have installed it), and something else... I think something that points to the binaries, perhaps called something like 'KDEBIN' although I can not find it now.
I have tried, now, to reproduce the error - and I can't :-/ So I might very well be talking out my ass ;) But my hunch is that the startkde script can't find the correct location to start 'dcop' from. If I do: ~$ ls /usr/local/bin/*dcop* /usr/local/bin/dcop /usr/local/bin/dcopidl /usr/local/bin/dcopref /usr/local/bin/dcopstart /usr/local/bin/dcopclient /usr/local/bin/dcopidl2cpp /usr/local/bin/dcopserver /usr/local/bin/kdcop /usr/local/bin/dcopfind /usr/local/bin/dcopobject /usr/local/bin/dcopserver_shutdown I see that I have a lot of stuff in my bin directory with 'dcop' in the name. Check that you have at least something in there, probably bin/dcop at the very least. Just in case your installation _is_ borked and you somehow didn't get dcop installed. But yeah, I'm pretty sure it's a simple matter of setting something like KDEDIR in the startkde script. Maybe also check that your QTDIR environment variable points somewhere useful. On my system: ~$ echo $QTDIR /usr/local/qt That's about all I can think of right now. It's annoying, this problem looks _so_familiar_ to me, and I just can't nail it down. Anyway, hope this helps. Cheers, Gareth On Thursday 31 July 2003 10:14, Brian Connell wrote: > Hi everyone, > > although I have had Linux on my Computer for some time....Redhat at one > time, Mandrake9 now. > I'm still just basically a point and clicker. > > So I decided to try to install gentoo, as a means of learning more about > Linux. > And as Yoda might have remarked............... Learning I am. > > I started with the stage3 livecd, as I only have dialup 56K connection, > and installed by chrooting from > my existing Mdk9 distro. > > It's taken me over 2 weeks so far, but I'm almost there. : ) I > couldn't believe how long it took to emerge X and KDE. > Also I had probs. with my USB mouse and Geforc4 card, among other things, > > However the thing I'm stuck on at the moment is when I type "startx" > from the prompt ....as root presently, although I have > tried adding a user to no avail .... kde tries to start, I get the > kde-3.1 startup screen, then a popup message box saying .... > > "error setting up inter-process communications for kde. > could not read network connection list /root/.DCOPServer_127.0.0.1 local > host _0 > please check that dcopserver is running" > > .......I am then returned to the prompt,where there are other > interesting messages waiting such as.... > > DCOPClient: attachInternal. attach failed authentification rejected, > reason ..none of the authentification protocols specified > are supported and host based authentification failed. > ICE connection rejected. > kdeinit DCOPServer could not be started. > Warning: connect ( ) failed: connection refused. > Error: can't contact kdeinit (end)..... > I originally wrote this down longhand, so may have lost something in > the retelling, but I think its accurate. > > I have tried googling on this one, and have found nothing useful, except > that heaps of other folks are having the same problem. > The advice on the net seemed to range from the arcane to the heroic, > and I really don't want to mess up the distro at this stage, > if I can avoid it, hoping someone can help. > > Thanks, > Brian Connell.