(*** This bug was imported into bugs.kde.org ***) Package: unknown Version: 2.0.1 Severity: normal Installed from: Suse 7.0 RPMs We have problem with KDE 2.0.1 installed on SUSE 7.0 systems. The problem occurs after running KDE for a few days and is related? to the dcopserver. The error messages that appears on the screen is: ----------------------------------------------------- Tere was some 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 ------------------------------------------------------ Some notes: 1. The dcopserver program is running 2. Most applications are still working although this error message appears every time an application is started. 3. Some application are not working like being able to log out from KDE. 4. I don't know what triggers the error. Solution? /Mattias Ohlsson (submitted via bugs.kde.org)
> We have problem with KDE 2.0.1 installed on SUSE 7.0 > systems. The problem occurs after running KDE > for a few days and is related? to the dcopserver. > > ----------------------------------------------------- > Tere was some 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 > ------------------------------------------------------ > > Some notes: > 1. The dcopserver program is running > 2. Most applications are still working although > this error message appears every time an application > is started. > 3. Some application are not working like being able to > log out from KDE. > 4. I don't know what triggers the error. Something eating up all filedescriptors (maybe)? Kuba
On Wednesday 10 January 2001 18:35 Kuba Ober wrote: > > Some notes: > > 1. The dcopserver program is running > > 2. Most applications are still working although > > this error message appears every time an application > > is started. > > 3. Some application are not working like being able to > > log out from KDE. > > 4. I don't know what triggers the error. > > Something eating up all filedescriptors (maybe)? > Kuba which reminds me of bug 16190 fixed on Dez 26.
Wolfgang Rohdewald wrote: > > On Wednesday 10 January 2001 18:35 Kuba Ober wrote: > > > Some notes: > > > 1. The dcopserver program is running > > > 2. Most applications are still working although > > > this error message appears every time an application > > > is started. > > > 3. Some application are not working like being able to > > > log out from KDE. > > > 4. I don't know what triggers the error. > > > > Something eating up all filedescriptors (maybe)? > > Kuba > > which reminds me of bug 16190 fixed on Dez 26. Hi I applied the patch suggested in bug 16190 but with no results. The problem still occurs. /Mattias
Can you send me the output of "netstat -p"? Thanks. Cheers Waldo -- bastian@kde.org | SuSE Labs KDE Developer | bastian@suse.com
Hi The problem with the DCOPserver still occurs! Background: Some months ago I reported about my problems with the dcop server. > We have problem with KDE 2.0.1 installed on SUSE 7.0 > systems. The problem occurs after running KDE > for a few days and is related? to the dcopserver. > > ----------------------------------------------------- > There was some 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 > ------------------------------------------------------ > > Some notes: > 1. The dcopserver program is running > 2. Most applications are still working although > this error message appears every time an application > is started. > 3. Some application are not working like being able to > log out from KDE. > 4. I don't know what triggers the error. Since then I have installed the latest version of KDE (2.1) but the problem remains. It is even worse since I can't start any KDE application after the first occurrence of the problem. The only thing that helps is to restart KDE!! A recompilation of KDE 2.1 did not help. Could the problem be related to fact that we have a lot of workstations running KDE and that I frequently run (KDE) programs on other computers even though my home directory resides on my "own" workstation (autofs)? Help would be appreciated! Regards Mattias -- ******************************************************************* Mattias Ohlsson PhD | email: mattias@thep.lu.se * Department of Theoretical Physics II | phone: +46 46 222 77 82 * Lund University Solvegatan 14A | fax: +46 - 46 222 96 86 * S-223 62 Lund Sweden | WWW: http://www.thep.lu.se * *******************************************************************
Were you able to get KDE up and running based on the posting on the website? http://bugs.kde.org/db/18/18352.html I have the EXACT same problem right now and can't get past it. Any suggestions??? -- Jeff
"Widom Jeffrey" wrote: > > Were you able to get KDE up and running based on the posting on the website? > http://bugs.kde.org/db/18/18352.html I have the EXACT same problem right > now and can't get past it. Any suggestions??? > > -- Jeff Well I could not solve the problem but it disappeared after we upgraded to Suse 7.2 and KDE 2.1.1. /Mattias -- ******************************************************************* Mattias Ohlsson PhD | email: mattias@thep.lu.se * Department of Theoretical Physics II | phone: +46 46 222 77 82 * Lund University Solvegatan 14A | fax: +46 - 46 222 96 86 * S-223 62 Lund Sweden | WWW: http://www.thep.lu.se * *******************************************************************
Same problem but with debian etch stable. Get error after open Konqueror. I don't get the error all the time.
what's the exact solution for this?