I've just tried it on a 64 bits system on debian, it went OK, so I guess
the bug was corrected!
Thanks
--
Unable to connect, and gets frozen when retrying on AMD64
https://bugs.launchpad.net/bugs/71160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
I'm running on a 32 bits processor as my main computer now, so I
wouldn't know. I may try when I get my hands back on a 64 bits though.
Thanks for your concern, even if it's surprising nobody else reported
something related..
--
Unable to connect, and gets frozen when retrying on AMD64
https://b
You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering is this still an issue for you? Thanks in
advance.
** Changed in: gtetrinet (Ubuntu)
Importance: Undecided => Medium
Status: New => Incomplete
--
Unable to connect, and gets frozen wh
Hm didn't bothered to launch it in a terminal, so now I can see a lot of
messages in the output, when connecting for the second time (I don't get
anything the first time):
** (gtetrinet:30595): WARNING **: End of file (server closed
connection).
** (gtetrinet:30595): WARNING **: client_readmsg fa
