Comment # 4 on bug 965653 from Wolfgang Bauer

(In reply to andreas bittner from comment #3)
> I dont know what processes or parts have been waiting or hanging or why, but
> something was wrong.

Well, but that's not enough information to do anything about it, I'm afraid.

As I wrote, the kactivitymanagerd crash is on logout and should not be a
problem.

Closing as WORKSFORME, feel free to reopen (or file a new bug report) if it
happens again.

But if zypper didn't print anything in the xterm, it might not have been a KDE
problem I suppose, but on a lower level.

Maybe kwin (the window manager/compositor) crashed, though.
The problem in this case is that drkonqi (the crash dialog) "grabs" the process
for debugging, which makes the whole graphical session appear to freeze (except
for the mouse pointer, but you cannot interact with anything).

So, if it should happen again, try to only kill "kwin_x11" from a text mode
console instead of the whole X session.
If that is the problem, everything should work fine again then, you should even
be able to restart kwin_x11 manually.