[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 03:00:32 EDT 2007
#1756: Pidgin causes a Windows Socket Error 10054, my modem resets, I lose all
internet connectivity.
---------------------------+------------------------------------------------
Reporter: vinnyc | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: pidgin (gtk) | Version: 2.0.2
Resolution: | Keywords:
Pending: 1 |
---------------------------+------------------------------------------------
Changes (by kstange):
* pending: 0 => 1
Comment:
Windows Socket error 10054 is "connection reset by peer" and means that
Pidgin was disconnected by the remote side. Windows socket errors are not
"fatal system errors", they are merely errors generated by the "winsock"
library used for making connections to the Internet. The purpose of these
errors is to indicate to the application why a connection failed. There
are some winsock errors that can be caused by the application or operating
system, but 10054 is one that is caused by losing the connection to the
remote system, and does not even necessarily indicate that you have lost
total connectivity to the network. In other words, Pidgin does not cause
10054 errors.
Thus, the more likely situation is that your Internet connection suddenly
drops, and as a result, Windows throws a socket error of 10054 to Pidgin
(and any other applications that are currently connected to the Internet).
Pidgin reports the numeric error for informational purposes when it is
disconnected. Other programs on your computer are receiving the same
error number, they just may not be saying it numerically.
If you are seeing your cable modem hard reset, it is almost definitely not
a software issue, and is pretty likely to be a problem with your cable
modem or service.
--
Ticket URL: <http://developer.pidgin.im/ticket/1756#comment:1>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list