Comment 1 for bug 396248

This issue is not related to a released BeBot version but to the currently unreleased aocpatch branch, which might be a part of the next release.

I can't reproduce the error. Its working here just fine in exactly the same runtime environment. Also I can't "guess" the problem from just an "EOF error" and even if I could, I'm afraid I'm not able to go that deep into the network protocol handling. So we are pretty much stuck here as long as nobody else comes up with a solution or more detailed reports.

Problem may be related to this bug: https://bugs.launchpad.net/bebot/+bug/396198