[Pidgin] #1756: Pidgin causes a Windows Socket Error 10054, my modem resets, I lose all internet connectivity.

Pidgin trac at pidgin.im
Sun Jun 17 01:12:38 EDT 2007


#1756: Pidgin causes a Windows Socket Error 10054, my modem resets, I lose all
internet connectivity.
--------------------------+-------------------------------------------------
 Reporter:  vinnyc        |       Type:  defect
   Status:  new           |   Priority:  minor 
Component:  pidgin (gtk)  |    Version:  2.0.2 
 Keywords:                |    Pending:  0     
--------------------------+-------------------------------------------------
 I see a lot of others posting this error. I however am using NO firewall,
 NO anti-virus, and NO anti-spyware applications. It just happens randomly
 whenever I am online. All firewall options in my router are off. Windows
 Firewall is off.

 Whenever I get it, it actually resets my cable modem too. Odd thing is,
 when I connect my computer directly to the modem and bypass my router, the
 modem does NOT reset when the error occurs. Both my cable modem and router
 are less than a week old. I purchased them to try and correct this
 problem, but to no avail.

 I have already called comcast probably 8 times, and they have run every
 test they can to ensure my connection is rock solid. Their records don't
 even show that I have been disconnected. I would have thought it was
 comcast, but since the modem doesn't reset when I bypass the router, I
 have my doubts. Also, I have re-installed windows and am using the latest
 drivers for all my hardware. I am using Windows XP Pro 32bit on an
 A8N32-SLI DX motherboard.

 I know it sounds strange, but it seems like Pidgin is causing a Windows
 Socket Error 10054, resulting in me losing internet connectivity. Maybe my
 router tries to remedy the error by doing a release / renew?

 All I know is the more this happens, the more it is pointing to Pidgin as
 the culprit. It actually has just taken place while I was typing this, and
 I happened to have the debug window open. Here's what it reports just
 before / during the error:

 (00:05:29) oscar: Scheduling destruction of FLAP connection of type 0x0002

 (00:05:29) oscar: Destroying oscar connection of type 0x0002

 (00:05:29) account: Disconnecting account 00BCD4A8

 (00:05:29) connection: Disconnecting connection 017ACB08

 (00:05:29) connection: Deactivating keepalive.

 (00:05:29) oscar: Destroying oscar connection of type 0x0018

 (00:05:29) oscar: Signed off.

 (00:05:29) connection: Destroying connection 017ACB08

 (00:05:34) util: Writing file blist.xml to directory C:\Documents and
 Settings\Vince\Application Data\.purple

 (00:05:34) util: Writing file accounts.xml to directory C:\Documents and
 Settings\Vince\Application Data\.purple


 Then it sits for like 30 - 45 seconds until it reconnects. Anyone have any
 idea why this is happening? I really don't want to go back to using AIM.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/1756>
Pidgin <http://pidgin.im>
Pidgin


More information about the Tracker mailing list