-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 . Ouch, you should not have deleted all files in /tmp . If you can, restore them. Also, try setting aside ~/.kde , log out, restart X, and log in again. It will reconstruct the .kde dir, maybe right this time. Do not do this with /root/.kde .h On Thursday 23 May 2002 13:16, Matthias Hentges wrote:
Hi all!
Sorry for posting in german. Now here is the english version:
A few days ago i did a clean install of SuSE 8.0 with KDE3. Everything was working fine (at least there were no problems i could not sort out in a few minutes)
But now my KDE3 installation seems to be broken. Each time i try to log in into KDE3 using Kdm or Gdm the loading process stops at "Setting up interprocess comunication". The reason for this is that the dcopserver can not be started. Here are the messages that i get when i run the kde startup script manually:
mhentges@mhcln01:..c/opt/gnome/gdm/Sessions >./kde //usr/lib/qt-3.0.3/plugins/imageformats/libqjpeg.so: Feature JPEG already defined in /usr/lib/qt3/plugins/imageformats/libqjpeg.so! //usr/lib/qt-3.0.3/plugins/imageformats/libqmng.so: Feature MNG already defined in /usr/lib/qt3/plugins/imageformats/libqmng.so! QObject::connect: No such slot QNetworkProtocol::newClient(int) QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'unnamed') DCOPServer self-test failed. QFile::getch: File not open QFile::getch: File not open kdeinit: DCOPServer could not be started, aborting. QObject::connect: No such slot QNetworkProtocol::slotTerminate() QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'unnamed') QObject::connect: No such slot QNetworkProtocol::slotCleanDeadConnections() QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'unnamed') Warning: connect() failed: : Connection refused DCOPServer self-test failed. QFile::getch: File not open QFile::getch: File not open kdeinit: DCOPServer could not be started, aborting.
As one can see, the dcopserver "self-test" fails, hence preventing KDE to launch.
If i run dcopserver in the console it starts fine:
mhentges@mhcln01:..c/opt/gnome/gdm/Sessions >dcopserver DCOPServer up and running. mhentges@mhcln01:..c/opt/gnome/gdm/Sessions >
Since i do not use KDE3 most of the time i have no idea what could have caused this error. I did install the lastes patches with YOU but that didnt help.
I do have write permission to /tmp. Also i deleted all files and folders in /tmp, and moved my ~/.kde but its still not working.
Since i did not find anything in the support database i now try it this way. Maybe someone else had the same problem and found a soloution.
Da ich KDE3 nicht als Desktop verwende weis ich leider nicht was das Problem hervorgerufen haben könnte. Die neusten Updates von YOU sind installiert, und mir gehen die Ideen aus :(
Ich habe schreibrechte für /tmp, habe alle alten Dateien und Ordner aus /tmp gelöscht und mein ~/.kde bzw ~/Desktop verschoben aber es hat nichts gebracht
Vieleicht hat jemand das gleiche Problem und kennt die Lösung? In der Supportdatenbank war jedenfalls nichts zu finden. --
Matthias Hentges
Contact-Information:
E-Mail@Home: eebe@gmx.net My Homepage: http://www.hentges.net
You can get my public PGP or GnuPG key from http://www.hentges.net/keys.html
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjztNY0ACgkQnQ18+PFcZJvtTQCfbsE4enXDERwxtH/UWAUuihhq U/QAn2+rP+Bb/wOEKc3C/pLq0iKXnFlh =U9Lv -----END PGP SIGNATURE-----