Re: DCOP errors and libkdeui errors
>I don't know exactly what for but programs need to register with a
>DCOP server that runs on your machine: [ ps -afux output ]
>
>magnus 2291 0.0 1.3 15076 5140 ? S 11:35 0:03
>kdeinit: dcopserver --nosid
>
Well, I don't have any dcopserver running on my system, but I have tried
starting it manually, with each option available. I'll give it another go
and see what errors I can provide.
>I _*think*_ that KDE programs cannot start if they can't connect to a
>DCOP server. And (as I've just found your message in my trash ...)
>this seems to be the case for you. NORMALLY, though, KDE applications
>that don't find a running DCOP server start it automatically so
>obviously something with your configuration / install of the DCOP
>server has gone quite wrong.
>
Obviously, but why? I wish I knew.
>Does that help you? Otherwise, please look into your DCOP
>configuration and maybe provide some more detail so that I can look
>into it more closely. Also, your first E-Mail would be nice (I can't
>find it in the list archives and it's already purged from my trash
>folder).
>
<ORIGINAL MAIL>
Subject: kde-devel broke my X?
I updated kdevelop to 2.0 and was very impressed. I needed to install the
kdelibs source before the configure routine would finish but then I got a
very impressive kdevelop and was able to check the progress of my small
project.
I thought I'd have a go at playing around with a KDE app, so I tried to
create a new project, but after creating all the files the configure
routine said that I was missing qtlib2.2.2, so I used apt-get to install
the missing qt libs. Now configure complained I was missing some KDE
headers. I installed kde-devel, but this broke most of the rest of kde.
Figuring that a re-boot would sort out the lib issues, I found that I could
no longer log into KDE with gdm. I kept getting errors about a missing dcop
file and to make sure the dcopserver was running. After several attempts to
find out why the dcopserver was not starting again (Manually starting
dcopserver didn't work) now I can not even get X to start. I finally tried
a full apt-get dist-upgrade with testing set to 1001 in my preferences, but
even this failed to fix X.
Obviously I've got soem serious problems with libs on my system again, but
I really want to avoid a complete re-install as the latest CD I've got is
Progeny and takes about 5 days to download the updates to testing before I
can re-install KDE again.
Could someone please send me a list of the valid libs needed for testing
KDE so I can find which ones need removing?
I can log in as myself or as root to the terminal, but startkde can not
connect to the display. startx give a KDE-like pop-up warning that a dcop
file is missing and to be sure the dcopserver is running.
I can start the dcopserver manually, after setting DISPLAY=:0 but the
startx only gives the blank screen with an X for a mouse and never gets
past this.
I guess I should learn to leave well enough alone.
Thanks again for all the help.
Cheers,
John Gay
--
To UNSUBSCRIBE, email to debian-kde-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
</ORIGINAL MAIL>
As dcop has no man pages, I'm not sure where to look for config files.
apt-cache search and dpkg -S both show dcopserver is provided by kdelibs3.
I'll have another look in the kdelibs3 package to see if I can find where
the config files go and see what is wrong with mine.
At least this gives me a little more info than I had before.
>Sorry that nobody answered your question on this list, please don't
>let that discourage you. KDE 2.2.2 is so cool (really) that it's
>worth the pain to install it (I had some problems, too).
Sorry I got a little short, but I've had a hard week with my KDE 2.2.1
crashing and bringing X down with it, spent a week trying to restore it and
most of the time only having a console login, and finding out that I'll
probably be made redundant at the start of the year and the Irish economy
has hit a bit of a slump so jobs are getting rare now. It's been a very
tough week.
Thanks for your offer of information. At least I can start to examine the
fault and find the culprit. I was really happy with KDE2.2.1 and I'm sure
that KDE2.2.2 is even better. Once I can get KDE to play nicely again on my
system I can stop using Gnome.
Cheers,
John Gay
Reply to: