dequis / purple-facebook

Facebook protocol plugin for libpurple (moved from jgeboski/purple-facebook)
GNU General Public License v2.0
954 stars 88 forks source link

Failed to read thrift: api.c #468

Open xdmtk opened 5 years ago

xdmtk commented 5 years ago

Anyone else getting

Failed to read thrift: api.c:1893 fb_api_cb_public_pt: assertion 'fb_frist_read_stop(thft)' failed

on Pidgin 2.13 - libpurple 2.13 ?

Partial debug output:

(16:21:02) connection: Connection error on 0x56063be75b90 (reason: 0 description: Failed to read thrift: api.c:1893 fb_api_cb_publish_pt: assertion 'fb_thrift_read_stop(thft)' failed)
(16:21:02) http: Request 0x56063c40eb50 performed successfully.
(16:21:02) http: Performing new request 0x56063b2a42b0 to scontent.xx.fbcdn.net.
(16:21:02) nss: subject=CN=*.facebook.com,O="Facebook, Inc.",L=Menlo Park,ST=CA,C=US issuer=CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
(16:21:02) nss: partial certificate chain
(16:21:02) certificate/x509/tls_cached: Starting verify for scontent.xx.fbcdn.net
(16:21:02) certificate/x509/tls_cached: Checking for cached cert...
(16:21:02) certificate/x509/tls_cached: ...Found cached cert
(16:21:02) nss/x509: Loading certificate from /home/$USER/.purple/certificates/x509/tls_peers/scontent.xx.fbcdn.net
(16:21:02) certificate/x509/tls_cached: Peer cert matched cached
(16:21:02) nss/x509: Exporting certificate to /home/$USER/.purple/certificates/x509/tls_peers/scontent.xx.fbcdn.net
(16:21:02) util: Writing file /home/xdmtk/.purple/certificates/x509/tls_peers/scontent.xx.fbcdn.net
(16:21:02) nss: Trusting CN=*.facebook.com,O="Facebook, Inc.",L=Menlo Park,ST=CA,C=US
(16:21:02) certificate: Successfully verified certificate for scontent.xx.fbcdn.net
(16:21:02) account: Disconnecting account ************@gmail.com (0x56063aeb3c90)
(16:21:02) connection: Disconnecting connection 0x56063be75b90
(16:21:02) http: Request 0x56063b2a42b0 performed without success.
(16:21:02) http: Request 0x56063bf40440 performed without success.
(16:21:02) http: Request 0x56063c519dc0 performed without success.
(16:21:02) http: Request 0x56063b3e3220 performed without success.
(16:21:02) connection: Destroying connection 0x56063be75b90
(16:21:02) prefs: /pidgin/conversations/im/x changed, scheduling save.
(16:21:02) prefs: /pidgin/conversations/im/y changed, scheduling save.
(16:21:02) prefs: /pidgin/blist/y changed, scheduling save.
(16:21:02) prefs: /pidgin/blist/height changed, scheduling save.
(16:21:04) prefs: /pidgin/blist/y changed, scheduling save.
(16:21:04) prefs: /pidgin/blist/height changed, scheduling save.
^C(16:21:06) sighandler: Caught signal 2

This happened within the last couple of days. I've been using purple-facebook for a while now, and have seen Facebook serverside changes affect purple-facebook, so I'm wondering if this may be the case again, or if I have something off on my end.

xdmtk commented 5 years ago

Seems to have resolved itself.. Assuming Facebook issue.. Closing

xdmtk commented 4 years ago

This is has been going on intermittently since I originally opened this issue. Can anyone else reproduce this?

dequis commented 4 years ago

It could plausibly just mean the network connection got interrupted. Does it happen during login, or are you unable to reconnect after it happens?

xdmtk commented 4 years ago

Unfortunately I am unable to connect after it happens. Some other interesting behavior to note:

Login actually succeeds momentarily, as I end up receiving any unread messages, but I am unable to respond to any of them. Nor do any of the messages get marked as read, since if I try and reconnect, the same previously unread messages get sent to me repeatedly.

xdmtk commented 4 years ago

Looks like this should be fixed in #480 , thanks @dequis. Is there another release coming out with the latest changes?