I updated to the latest kde packages from suse kde page and I am getting following error msg. at the startup: "There was an error settint up inter-process communication for KDE. The message returned by the system was: Could not read network connection list. /root/.DCOPserver_earth_:0 Please check that the "dcopserver" program is running" I just simply wonder how could I avoid problems like that in the future? Cheers Peter
On Monday 13 August 2001 12:58, you wrote:
Peter J.Pieczora wrote:
I updated to the latest kde packages from suse kde page and I am getting following error msg. at the startup:
"There was an error settint up inter-process communication for KDE. The message returned by the system was:
Could not read network connection list. /root/.DCOPserver_earth_:0
Please check that the "dcopserver" program is running"
I just simply wonder how could I avoid problems like that in the future?
Cheers
Peter
This is happening because you have old DCOP files in your home directory.
Log into the shell, and type: rm .DCOP* and then try it again.
Good luck! -Steven
Unfortunately it didn't work at all. Anyway, thx for your help cheers, Peter
OK, I will give it one more try, and see what happens after cleaning up /tmp. Thx all, and hopefully I'll be back with 2.2, lol cheers, Peter
Peter J.Pieczora wrote:
I updated to the latest kde packages from suse kde page and I am getting following error msg. at the startup:
"There was an error settint up inter-process communication for KDE. The message returned by the system was:
Could not read network connection list. /root/.DCOPserver_earth_:0
Please check that the "dcopserver" program is running"
I just simply wonder how could I avoid problems like that in the future?
Cheers
Peter
This is happening because you have old DCOP files in your home directory. Log into the shell, and type: rm .DCOP* and then try it again. Good luck! -Steven
Well, the next thing then would be to try renaming the .kde and .kde2 directories, so that when you start KDE2 it automagically recreates them with what it expects to find. I was able to jump from KDE2.1.2 to KDE2.2 pretty simply, and I did have some weird problems at the beginning because the config files were a little "off". Good luck, Steven Peter J.Pieczora wrote:
On Monday 13 August 2001 12:58, you wrote:
Peter J.Pieczora wrote:
I updated to the latest kde packages from suse kde page and I am getting following error msg. at the startup:
"There was an error settint up inter-process communication for KDE. The message returned by the system was:
Could not read network connection list. /root/.DCOPserver_earth_:0
Please check that the "dcopserver" program is running"
I just simply wonder how could I avoid problems like that in the future?
Cheers
Peter
This is happening because you have old DCOP files in your home directory.
Log into the shell, and type: rm .DCOP* and then try it again.
Good luck! -Steven
Unfortunately it didn't work at all. Anyway, thx for your help
cheers,
Peter
Had that problem already, went through changing to blank home directory, and nada... Solution lies in cleaning up the /tmp directory. Older files lying around actually mess up newer kde. Check in /tmp: kde-username ksocket-username mcop-username -tosi Þann mánudagur 13 ágúst 2001 19:24 skrifaðir þú:
Well, the next thing then would be to try renaming the .kde and .kde2 directories, so that when you start KDE2 it automagically recreates them with what it expects to find. I was able to jump from KDE2.1.2 to KDE2.2 pretty simply, and I did have some weird problems at the beginning because the config files were a little "off".
Good luck, Steven
Peter J.Pieczora wrote:
On Monday 13 August 2001 12:58, you wrote:
Peter J.Pieczora wrote:
I updated to the latest kde packages from suse kde page and I am getting following error msg. at the startup:
"There was an error settint up inter-process communication for KDE. The message returned by the system was:
Could not read network connection list. /root/.DCOPserver_earth_:0
Please check that the "dcopserver" program is running"
I just simply wonder how could I avoid problems like that in the future?
Cheers
Peter
This is happening because you have old DCOP files in your home directory.
Log into the shell, and type: rm .DCOP* and then try it again.
Good luck! -Steven
Unfortunately it didn't work at all. Anyway, thx for your help
cheers,
Peter
Tor Sigurdsson wrote:
Had that problem already, went through changing to blank home directory, and nada...
Solution lies in cleaning up the /tmp directory. Older files lying around actually mess up newer kde.
Check in /tmp: kde-username ksocket-username mcop-username
-tosi
Þann mánudagur 13 ágúst 2001 19:24 skrifaðir þú:
Well, the next thing then would be to try renaming the .kde and .kde2 directories, so that when you start KDE2 it automagically recreates them with what it expects to find. I was able to jump from KDE2.1.2 to KDE2.2 pretty simply, and I did have some weird problems at the beginning because the config files were a little "off".
Good luck, Steven
Peter J.Pieczora wrote:
On Monday 13 August 2001 12:58, you wrote:
Peter J.Pieczora wrote:
I updated to the latest kde packages from suse kde page and I am getting following error msg. at the startup:
"There was an error settint up inter-process communication for KDE. The message returned by the system was:
Could not read network connection list. /root/.DCOPserver_earth_:0
Please check that the "dcopserver" program is running"
I just simply wonder how could I avoid problems like that in the future?
Cheers
Peter
This is happening because you have old DCOP files in your home directory.
Log into the shell, and type: rm .DCOP* and then try it again.
Good luck! -Steven
Unfortunately it didn't work at all. Anyway, thx for your help
cheers,
Peter
aaah! I knew it was something to do with temp files! My system autocleans /tmp when I boot, so after I installed KDE2.2, I rebooted and it worked. Thanks, -Steven
How is konqueror working in 2.2 for you guys? For me it's crashing on just about every page if I enable JavaScript, including www.userfriendly.org which has always worked for me in the past. Any clues? Anders On Monday 13 August 2001 21:41, Steven Hatfield wrote:
Tor Sigurdsson wrote:
Had that problem already, went through changing to blank home directory, and nada...
Solution lies in cleaning up the /tmp directory. Older files lying around actually mess up newer kde.
Check in /tmp: kde-username ksocket-username mcop-username
-tosi
Þann mánudagur 13 ágúst 2001 19:24 skrifaðir þú:
Well, the next thing then would be to try renaming the .kde and .kde2 directories, so that when you start KDE2 it automagically recreates them with what it expects to find. I was able to jump from KDE2.1.2 to KDE2.2 pretty simply, and I did have some weird problems at the beginning because the config files were a little "off".
Good luck, Steven
Peter J.Pieczora wrote:
On Monday 13 August 2001 12:58, you wrote:
Peter J.Pieczora wrote:
I updated to the latest kde packages from suse kde page and I am getting following error msg. at the startup:
"There was an error settint up inter-process communication for KDE. The message returned by the system was:
Could not read network connection list. /root/.DCOPserver_earth_:0
Please check that the "dcopserver" program is running"
I just simply wonder how could I avoid problems like that in the future?
Cheers
Peter
This is happening because you have old DCOP files in your home directory.
Log into the shell, and type: rm .DCOP* and then try it again.
Good luck! -Steven
Unfortunately it didn't work at all. Anyway, thx for your help
cheers,
Peter
aaah! I knew it was something to do with temp files! My system autocleans /tmp when I boot, so after I installed KDE2.2, I rebooted and it worked.
Thanks,
-Steven
Anders Johansson wrote:
How is konqueror working in 2.2 for you guys? For me it's crashing on just about every page if I enable JavaScript, including www.userfriendly.org which has always worked for me in the past.
Any clues?
Anders
On Monday 13 August 2001 21:41, Steven Hatfield wrote:
Tor Sigurdsson wrote:
Had that problem already, went through changing to blank home directory, and nada...
Solution lies in cleaning up the /tmp directory. Older files lying around actually mess up newer kde.
Check in /tmp: kde-username ksocket-username mcop-username
-tosi
Þann mánudagur 13 ágúst 2001 19:24 skrifaðir þú:
Well, the next thing then would be to try renaming the .kde and .kde2 directories, so that when you start KDE2 it automagically recreates them with what it expects to find. I was able to jump from KDE2.1.2 to KDE2.2 pretty simply, and I did have some weird problems at the beginning because the config files were a little "off".
Good luck, Steven
Peter J.Pieczora wrote:
On Monday 13 August 2001 12:58, you wrote:
Peter J.Pieczora wrote:
>I updated to the latest kde packages from suse kde page and I am >getting following error msg. at the startup: > >"There was an error settint up inter-process communication for KDE. >The message returned by the system was: > >Could not read network connection list. >/root/.DCOPserver_earth_:0 > >Please check that the "dcopserver" program is running" > >I just simply wonder how could I avoid problems like that in the >future? > >Cheers > >Peter > This is happening because you have old DCOP files in your home directory.
Log into the shell, and type: rm .DCOP* and then try it again.
Good luck! -Steven
Unfortunately it didn't work at all. Anyway, thx for your help
cheers,
Peter
aaah! I knew it was something to do with temp files! My system autocleans /tmp when I boot, so after I installed KDE2.2, I rebooted and it worked.
Thanks,
-Steven
Wow.. I'm not having any problems like that at all. Maybe check the KDE mailing lists, and see what the developers have to say? Good luck! -Steven
participants (4)
-
Anders Johansson -
Peter J.Pieczora -
Steven Hatfield -
Tor Sigurdsson