#135 closed defect (fixed)

Yahoo reconnection trouble with socks proxy.

Reported by: it-ll-be-bitlbee@… Owned by: wilmer
Priority: normal Milestone:
Component: Yahoo Version: 1.0.1
Keywords: patch Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro: Slackware 10.2


I've a trouble using bitlbee with yahoo and socks. Config file:

RunMode = Inetd
AuthMode = Registered
Proxy = socks5://


15:17 <@root> YAHOO - Reconnecting in 60 seconds..
15:18 <@root> YAHOO - Logging in: Connecting
15:18 [bitlbee] -!- (process:10010): GLib-WARNING **: giounix.c:400Error while getting flags for FD: Bad file descriptor (9)
15:18 [bitlbee] -!- (process:10010): GLib-WARNING **: giounix.c:400Error while getting flags for FD: Bad file descriptor (9)
--- 100% CPU usage here.
15:18 <@darkk> account off 3
--- still 100% CPU usage

Tested bitlbee versions: 1.0.1, 1.0.2.

The issue arizes when there is no socks server at (that's port-forwarding created with SSH).

All other protocols seems to work fine.

Attachments (2)

yahoo-fix.patch (541 bytes) - added by darkk at 2007-02-18T21:27:08Z.
works-for-me fix
yahoo-fix.2.patch (554 bytes) - added by darkk at 2007-02-18T21:37:14Z.
same without memory leak

Download all attachments as: .zip

Change History (5)

Changed at 2007-02-18T21:27:08Z by darkk

Attachment: yahoo-fix.patch added

works-for-me fix

Changed at 2007-02-18T21:37:14Z by darkk

Attachment: yahoo-fix.2.patch added

same without memory leak

comment:1 Changed at 2007-12-03T00:41:02Z by wilmer

Component: BitlBeeYahoo
Owner: set to wilmer

comment:2 Changed at 2014-07-07T12:05:27Z by dx

Keywords: patch added

Still happening. Very ugly.

The idea behind the patch sounds good, although I doubt it would apply cleanly now. Adding patch tag to consider it later.

comment:3 Changed at 2015-10-21T08:53:45Z by dx

Resolution: fixed
Status: newclosed

Modify Ticket

as closed The owner will remain wilmer.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.