I setup a friend with an account on my bip server and it was working fine. He has a dell mini9 with ubuntu on it and xchat: xchat 2.8.4 Linux 2.6.24-24-lpia compiled 9-Apr-2008 Whenever they connect to my bip server it crashes. I installed debuginfo and ran it under gdb: Program received signal SIGSEGV, Segmentation fault. 0x0000000000412d24 in bip_on_event (bip=0x7fff43a6c620, conn=0xc7acc0) at src/irc.c:2479 2479 mylog(LOG_ERROR, "[%s] Error in protocol, closing...", (gdb) where #0 0x0000000000412d24 in bip_on_event (bip=0x7fff43a6c620, conn=0xc7acc0) at src/irc.c:2479 #1 0x0000000000412e0b in irc_main (bip=0x7fff43a6c620) at src/irc.c:2550 #2 0x000000000040aa70 in main (argc=<value optimized out>, argv=<value optimized out>) at src/bip.c:1316 bip-0.8.4-1.fc12.x86_64 bip-debuginfo-0.8.4-1.fc12.x86_64 Happy to test patches or try and provide more info.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Could you try v0.8.6 when it hits updates-testing and let me know if you still have problems? Also, leaving feedback on bodhi would help: https://admin.fedoraproject.org/updates/bip-0.8.6-1.fc12 To install the test version run: yum --enablerepo=updates-testing update bip
I've updated here and asked my friend with the weird client to test. Will let you know what I find out.
Well, it no longer crashes. ;) Now the client can't connect and I see in the logs: 27-10-2010 12:24:28 ERROR: [X] Invalid credentials (user: X) but the password is correct. Puzzling.
Progress! Are you sure the password is being sent as un:pw:connection? Maybe try generating a new one with bipmkpw? I'm sure the format didn't change from 0.8.4, I didn't need to change anything when I upgraded my system to 0.8.6
Yeah, the password is right. They can connect from several other machines just fine with that pass. So, its sounding to me like the client on that machine is just broken and doing the wrong thing somehow. ;(
Time to fire up wireshark and sniff the connection :) Sounds like this bug is fixed though, so I'm going to close it.