Custom Query (1098 matches)

For some reason it keeps sending me JOIN #twitter_xyz over and over again. After a while it crashes.

recvfrom(17, "*\2\207u\3\317", 6, 0, NULL, NULL) = 6
recvfrom(17, "\0\r\0\t\0\0\0\0\0\24\0\2\0\1\21\0\3\0<\0\2\0\n\0\3\0\1\26\0\4\0\2"..., 975, 0, NULL, NULL) = 975
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
read(9, "JOIN #twitter_xyz \r\n", 512) = 28
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
read(9, "JOIN #twitter_xyz  \r\nJOIN"..., 512) = 112
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
read(4, 0x7fffba9c0be0, 16)             = -1 EAGAIN (Resource temporarily unavailable)
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
read(9, "JOIN #twitter_xyz \r\n", 512) = 28
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
getsockopt(24, SOL_SOCKET, SO_ERROR, [110], [4]) = 0
close(24)                               = 0
close(24)                               = -1 EBADF (Bad file descriptor)
open("/dev/tty", O_RDWR|O_NOCTTY|O_NONBLOCK) = -1 ENXIO (No such device or address)
writev(2, [{"*** Error in `", 14}, {"/usr/local/sbin/bitlbee", 23}, {"': ", 3}, {"double free or corruption (fastt"..., 35}, {": 0x", 4}, {"00007f59d13352f0", 16}, {" ***\n", 5}], 7Feb 09 15:56:36 
[redacted] bitlbee[17918]: *** Error in `/usr/local/sbin/bitlbee': double free or corruption (fasttop): 0x00007f59d13352f0 ***
) = 100

git version: db5ef3a204c3a518adb7cedde0ffb067d6336add

When sending WHO replies Bitlbee does not check the away settings for the local IRC user. If I set myself as /away, any future replies will wrongly tell the IRC client that I'm not away. See irc_send_who in ​irc_send.c, line 306

This breaks Quassel IRC's "auto-away on detach" functionality. The Quassel core (bouncer) sets /away when the client disconnects, but whenever a WHO reply is received indicating the account nick is no longer away (H instead of G), the core assumes Bitlbee cleared the away status. As a result, the Quassel core won't send the appropriate AWAY\r\n upon reattaching the client. See ​Quassel coresessioneventprocessor.cpp, line 766

Perhaps use a form of set_getstr(&irc->b->set, "away", away) to check what's set by irc_cmd_away in ​irc_commands.c, line 731?

strace output of Bitlbee (strace -e write,read -p $BITLBEE_PID -t -s 400):

16:12:36 read(11, "AWAY :I'm here, just testing Bitlbee\r\n", 512) = 38
16:12:36 write(11, ":localhost 306 digitalcircuit :You're now away: I'm here, just testing Bitlbee\r\n", 76) = 76
16:13:30 read(11, "WHO &bitlbee\r\n", 512) = 33
16:13:30 write(11, ":localhost 352 digitalcircuit &bitlbee quassel localhost localhost digitalcircuit H :0 Digital\r\n:localhost 352 digitalcircuit &bitlbee root localhost localhost root H :0 User manager\r\n:localhost 315 digitalcircuit &bitlbee :End of /WHO list\r\n", 454) = 454

expected reply (G not H):

16:13:30 write(11, ":localhost 352 digitalcircuit &bitlbee quassel localhost localhost digitalcircuit G :0 Digital\r\n:localhost 352 digitalcircuit &bitlbee root localhost localhost root H :0 User manager\r\n:localhost 315 digitalcircuit &bitlbee :End of /WHO list\r\n", 454) = 454

When you blocked someone on Twitter and they mention you, then the mention still appears in bitlbee (and even trigger a notification). This shouldn't happen and doesn't happen in other 3rd-party-clients. People get blocked for a reason.