Hello Milan,
your last statement was the key to success here. Although I knew
off-hand that I had no firewall settings or anything like that in place,
I checked on the loopback device again and oddly enough had to discover
that for *some reason* it had no IP set - hence all connections
targeting localhost were null-routed.
I reconfirmed your assumption that this was a problem on my machine by
simply setting the appropriate IP and now mumble as well as
speech-dispatcher just run fine and do not block anything anymore.
I am really sorry for the inconveniences caused and I hope I didnt
trouble you that much! :(
regards,
Patrick
Milan Zamazal wrote:
"PR" == Patrick Ringl <patri...@freenet.de> writes:
PR> Since snd_open() just not block my system (if speech-dispatched
PR> is installed) but also mumble which depends on the appropriate
PR> speech-dispatcher-library I'd like you to have a closer look on
PR> this.
Well, so apparently libspeechd hangs *in a system call* when trying to
connect to speech-dispatcher.
Does `telnet localhost 6560' work on your system or does it hang too?
If it works, can you type `quit' there and does it close the connection?
How about the logs in /var/log/speech-dispatcher/ I asked about in my
last mail?
Again, I can't see a reason why libspeechd should hang in the `connect'
call -- it should either succeed or fail. Unless there is something
really weird such as firewall set on the loopback interface.
Regards,
Milan Zamazal
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
