Opened at 2013-05-02T10:13:01Z
Closed at 2013-05-08T07:25:38Z
#1052 closed defect (duplicate)
bitlbee connection pinging out
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | BitlBee | Version: | 3.2 |
| Keywords: | Cc: | ||
| IRC client+version: | irssi 0.8.15 | Operating System: | Linux |
| OS version/distro: | Arch |
Description
Recently, with irssi and bitlbee, I have been receiving absurdly high lag and inexplicable reconnections, despite running on localhost.
Attachments (0)
Change History (8)
comment:1 Changed at 2013-05-02T15:45:05Z by
comment:2 Changed at 2013-05-02T16:57:57Z by
Note however that my copy of bitlbee is linked to libgnutls.
comment:3 Changed at 2013-05-06T15:12:18Z by
Can you make VERY sure that's the case? That seems highly unlikely, everybody else with this problem found out they were (maybe unknowingly) using OpenSSL. GnuTLS+GTalk is working fine for me and others for ages.
comment:4 Changed at 2013-05-07T04:32:17Z by
The command ldd /usr/sbin/bitlbee contained the line
libgnutls.so.28 => /usr/lib/libgnutls.so.28 (0x00007fbb5e66a000)
comment:5 Changed at 2013-05-07T23:00:39Z by
Do you have debugging symbols in your binary? Are you handy with gdb? Would be good to get a stacktrace of where it gets stuck..
comment:6 Changed at 2013-05-07T23:43:07Z by
The binary does not have debugging symbols but I have recompiled bitlbee from the Arch package with them. I've not used gdb before but I have found the command for producing a stacktrace. I will attempt to reproduce the issue and provide a stacktrace.
comment:7 Changed at 2013-05-08T00:57:55Z by
The version with debugging symbols did not seem to suffer the bug. I suspect that in fact despite updating to 3.2-2 linked to gnutls from 3.2-1 linked to openssl, I never actually restarted the bitlbee executable.
comment:8 Changed at 2013-05-08T07:25:38Z by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Yep, that was one of my guesses too. :-) Thanks, will close this bug then.
Maybe same bug as http://bugs.bitlbee.org/bitlbee/ticket/1048