[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    [Fwd: [kde-linux] DCOPClient::attachInternal. Attach failed Could
From:       James Richard Tyrer <tyrerj () acm ! org>
Date:       2005-07-30 20:31:33
Message-ID: 42EBE3A5.1080503 () acm ! org
[Download RAW message or body]

I do not know the exact cause of this problem.  However, the attached 
patch seems to fix it.

Does this change in order in the "startkde" script cause other issues?

-- 
JRT

-------- Original Message --------
Subject: [kde-linux] DCOPClient::attachInternal. Attach failed Could not 
open network socket
Date: Fri, 29 Jul 2005 18:04:20 -0700
From: James Richard Tyrer <tyrerj@acm.org>
Reply-To: For people using KDE on Linux with related questions/problems 
<kde-linux@kde.org>
To: kde-linux@kde.org

I switched my SVN 'trunk/KDE' to 'branches/KDE/3.5' and although I had
some problems with SVN, I now have KDELibs and KDEBase built and installed.

However, it won't run -- KDE won't start.  I seem to have the:

DCOPClient::attachInternal. Attach failed Could not open network socket

problem. :-(

I have this set up the same way for the user: KDE_Test that I had with
'trunk'.  KDE-3.5 is installed with a separate prefix: /usr/kde-3.5 and
my .bash_profile includes:

	PATH=/usr/kde3.5/bin:$PATH
	LD_LIBRARY_PATH=/usr/kde3.5/lib
	KDEDIR=/usr/kde3.5
	KDEHOME=$HOME/.kde
	export PATH LD_LIBRARY_PATH KDEDIR KDEHOME

My output from "startkde" is attached.

What should I check?

-- 
JRT



["error.txt" (text/plain)]

startkde: Starting up...
kbuildsycoca running...
KWrited - Listening on Device /dev/pts/5
ICE default IO error handler doing an exit(), pid = 9328, errno = 0
ICE default IO error handler doing an exit(), pid = 9335, errno = 0
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
WARNING: DCOP communication problem!
kdeinit: Communication error with launcher. Exiting!
Warning: connect() failed: : Connection refused
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
FATAL: DCOP communication problem!


["file:///tmp/nsmail-2.tmp" (text/plain)]

___________________________________________________
This message is from the kde-linux mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

["startkde-3.5.patch" (text/plain)]

--- startkde.old	2005-07-30 13:27:02.000000000 -0700
+++ startkde	2005-07-30 13:17:32.000000000 -0700
@@ -284,10 +284,6 @@
      ;;
 esac
 
-# certain features such as Konqueror preloading work only with full KDE running
-KDE_FULL_SESSION=true
-export KDE_FULL_SESSION
-
 # We set LD_BIND_NOW to increase the efficiency of kdeinit.
 # kdeinit unsets this variable before loading applications.
 LD_BIND_NOW=true kdeinit +kcminit
@@ -297,6 +293,10 @@
   xmessage -geometry 500x100 "Could not start kdeinit. Check your installation."
 fi
 
+# certain features such as Konqueror preloading work only with full KDE running
+KDE_FULL_SESSION=true
+export KDE_FULL_SESSION
+
 # If the session should be locked from the start (locked autologin),
 # lock now and do the rest of the KDE startup underneath the locker.
 if test -n "$DESKTOP_LOCKED"; then


 =

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscrib=
e <<


[prev in list] [next in list] [prev in thread] [next in thread]