https://bugs.kde.org/show_bug.cgi?id=333877

--- Comment #1 from Matthew Woehlke <mw_triad@users.sourceforge.net> ---
Comments would be appreciated.

This could probably be avoided if KSMServer::processData timed out; is there a
reason it doesn't?

I've had at least one instance where I was able to "fix" this by quitting the
application on the far end. Presumably this causes the read to fail because the
other end of the socket no longer exists, after which ksmserver is able to go
back to working normally.

-- 
You are receiving this mail because:
You are watching all bug changes.