(*** This bug was imported into bugs.kde.org ***) Package: dcopserver Version: KDE 3.0.2 Severity: crash Installed from: Compiled From Sources Compiler: GCC 3.1 OS: Linux OS/Compiler notes: Not Specified When KDE is started the splash screen comes up immediately followed by a pop-up saying: "There was an error setting up inter-process communications for KDE. The message returned by the system was: Could not open network socket. Please check that the dcopserver program is running!" The console shows these lines: kdeinit: Launched DCOPServer pid = 1131 result = 0 DCOP: register 'anonymous-1131' -> number of clients is now 1 ICE default IO error handler doing an exit() pid = 1131 errno = 2 kdeinit: DCOPServer could not be started aborting. Warning: connect() failed: : Connection refused DCOPClient::attachInternal. Attach failed Could not open network socket KCrash: crashing.... crashRecursionCounter = 2 KCrash: Application Name = ksplash path = <unknown> pid = 1128 DCOPClient::attachInternal. Attach failed Could not open network socket kdeinit: Launched DCOPServer pid = 1138 result = 0 DCOP: register 'anonymous-1138' -> number of clients is now 1 ICE default IO error handler doing an exit() pid = 1138 errno = 2 kdeinit: DCOPServer could not be started aborting. DCOPClient::attachInternal. Attach failed Could not open network socket I've tried to run this as user root as well as a newly created user (so there wouldn't be any stale files lying around in the home directory). Running 'strace' on dcopserver didn't show me anything I could use but maybe it's output is desired anyways. If so I'll send it along. (Submitted via bugs.kde.org)
Could it be that the directory /tmp/.ICE-unix is not writable for you?
Another possible hole... diff -u Xtranssock.c~ Xtranssock.c --- Xtranssock.c~ Tue Feb 11 18:49:27 2003 +++ Xtranssock.c Wed Feb 12 23:02:57 2003 @@ -391,6 +391,8 @@ ) { PRMSG (1, "SocketOpen: socket() failed for %s\n", Sockettrans2devtab[i].transname, 0, 0); + if (ciptr->fd > 0) + close(ciptr->fd); xfree ((char *) ciptr); return NULL; In the above, if you exceed TRANS_OPEN_MAX file descriptors you return without closing the socket descriptor.
I have removed the TRANS_OPEN_MAX limit, but it is very unlikely that that caused this problem: The dcopserver is unlikely to be using very much files shortly after startup.
The problem stopped showing up in later KDE releases and I've been unable to forcefully reproduce it.