Comment 11 for bug 244081

Chris, I may know what your problem is. By default in 0.1, Entertainer required that the backend be started separately. However, the current trunk does not require that the backend be started separately. So your problem may be that you are using the trunk, started the backend, then tried to start the frontend. If that is the case, then the frontend is trying to start the backend a second time, but the port is already in use by the backend process. Is this what is happening to you?