-
Member
DCOPServer could not be started
Have had three crashes in the past 10 days. I get the "DCOPServer could not be started" error and lose all KDE functions. I also get something about IceAuthority. Flux still works. Googling this error I get all kinds of activity going all the way back to 2003 with varying solutions.
For me, I finally started using Acronis and take an image of EXT2 and just reapply the image when the error occurs. Only takes 8 minutes and a reapplication of the gopher grub.
But, this seems very hokey. I actually thought Linux via BT2 was ready to use as a full time o/s but this makes me hesitate.
Does anyone know WHY this occurs? Does anyone know an alternate fix ...preferably a preventive fix?
Thanks for any feedback.
Alacrity
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules