This kind of error messages are related to files in components
directory
of an extensions which are not real XPCOM components, but usually
they're not cause of problems. (Makefile and MozRepl.idl should be
originated
from mozrepl, the other files come from some other extensions)
> When starting manually the error does not appear, but only
> sometimes does netstat shows localhost:4242, usually TIME_WAIT. But
> putty still can't connect to it (no prompt).
> Where should I look?
> Petr
I've not a Windows PC to test this problem myself, I'll try to find
one in the next days.
In the mean time you could test if a local firewall service rejects
your
connections to local ports.
---
rpl
I was able to find an error (copying only part of it, firefox -console
apparently does not allow copy)
NS_ERROR_FAILURE nsServerSocket.init
server.js, line 95 data:no
Hope it helps
And it helps :-)
The error seams to be related to an internal XPCOM component (socket-server)
and I'm not able (until now) to reproduce the problem :-(
Can you try to create a new clean firefox profile to test the problem in an
isolated environment or on a different machine/window installation to verify
how it can be reproduced?
--
Luca Greco @ Alca Società Cooperativa
Follow me on http://twitter.com/lucagreco
If you are still experiencing problems connecting to mozrepl by telnet,
you can try to use mozrepl-panel (http://ubik.cc/projects/mozrepl-panel),
distribuited separately until I get the time to integrate it in mozrepl.
Happy hacking to all,
rpl