> On 09/28/11 14:48, Peter Laws wrote: >> On 09/12/11 12:11, Timothy Pearson wrote: >> > >> After all that ... it hung while booting. I power-cycled it and got the >> KDE^H^H^HTrinity login. Logged in and got a popup that said: >> >> There was an error setting up inter-process communications for KDE. The >> message returned by the system was: >> >> Could not read network connection list. >> /tmp/1571417411/.DCOPserver_toto2__0 >> >> Please check that the "dcopserver" program is running! >> >> Naturally, I clicked OK. Ended up with a frameless xterm window and no >> menus, etc, as if I was in a failsafe session (though there was a >> desktop >> image). Logout/login and get no popup, but still have a single xterm >> albeit >> with frame, menus, etc. Still no icons, menus, etc. >> >> Help? > > Looking at it now, dcopserver is running: > > root 1502 1 0 14:42 ? 00:00:00 dcopserver [kdeinit] > --nosid --suicide > This might be related to a feature that was added a couple of weeks ago. Try editing your /etc/trinity/kdm/kdmrc (or kdmdistrc file if it is present) and edit this line: WindowManager=kwin to read WindowManager= If the WindowManager=<something> line is not present then add it in the [X-*-Greeter] section of the file. Reboot and try logging in again. Let me know if this allows you to login--it is a workaround and the real cause of problem will need to be investigated if this works. Thanks! Tim