Ticket #11070 (closed defect: invalid)
BUG: xchat2 2.6.8_0 - NAT DCC error from perl scripts
| Reported by: | dir123@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Low | Milestone: | |
| Component: | ports | Version: | 1.3.2 |
| Keywords: | Cc: | ||
| Port: |
Description
Using Xchat 2.6.6 and Obsidian2 2.0.0-rc2, I think I've uncovered what appears to be a problem with the interaction between the perl module and the "Get my address from the IRC server" preference.
Obsidian sends the following command: Xchat::command("dcc chat $nick", undef, $server);
If the "Get my address" box is unchecked, and there is no DCC IP address specified, $nick receives a dcc chat with an IP and port ("DCC CHAT chat 3232238182 55532", for instance). If either one of those is filled in, then all that comes across is the string "DCC CHAT chat". This doesn't appear to be a problem with Obsidian, as it appears to rely on Xchat to provide the IP and port.
I'm pretty sure this is not a problem with xchat itself, as I've failed to reproduce it on a Gentoo install, and an xchat dev couldn't reproduce it either.
There's a script available at this link which should reproduce the problem with a minimal amount of code.
For the record, this is not a Blocker, not part of the base, not as severe, is based on version 1.3.2, and should be assigned to mij@….
On the other hand, this was the fourth time in two days I tried to submit this bug, and every previous time, I set those options... And got dumped to a "server not responding" https page (instead of the current http one I'm on right now). This fourth try, I figured "I'll just see if it loads this page called preview." It did, but unlike a real preview, I couldn't then make changes and/or cancel. So I apologize for the extra work someone's going to have to do to sort it out, but it's the server's fault :p