Connectivity problems with https://api.twitter.com leads to crash

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Apparently api.twitter.com is having problems with https
2. Unable to connect to api.twitter.com: SSL Connection Failed
3. crash

What is the expected output? What do you see instead?
I would expect that the plugin could handle this condition, and just retry 
later. 

What version of the product are you using? On what operating system?
mbpurple 0.3.0, pidgin 2.7.1, FreeBSD 9-current (r209614)

Please provide any additional information below.
Here is the stack trace:
#0  0x294a93eb in thr_kill () at thr_kill.S:3
#1  0x29457516 in _thr_send_sig (thread=0x29804140, sig=6)
    at /usr/local/src/lib/libthr/thread/thr_kern.c:92
#2  0x29455033 in _raise (sig=6)
    at /usr/local/src/lib/libthr/thread/thr_sig.c:187
#3  0x295481ca in abort () at /usr/local/src/lib/libc/stdlib/abort.c:65
#4  0x080c74b1 in sighandler (sig=11) at gtkmain.c:192
#5  <signal handler called>
#6  0x5a5a5a5a in ?? ()
#7  0x29ed84be in mb_conn_fetch_url_cb (url_data=0x2a179630, 
    user_data=0x2a172280, url_text=0x0, len=0, 
    error_message=0x2b59c500 "Unable to connect to api.twitter.com: SSL Connection Failed") at mb_net.c:165
#8  0x28e018f4 in purple_util_fetch_url_error (gfud=0x2a179630, 
    format=0x28e56648 "Unable to connect to %s: %s") at util.c:3629
#9  0x28e01e88 in ssl_url_fetch_error_cb (ssl_connection=0x2b5a1a00, 
    error=PURPLE_SSL_CONNECT_FAILED, data=0x2a179630) at util.c:4132
#10 0x28dfbbeb in purple_ssl_connect_cb (data=0x2b5a1a00, source=-1, 
    error_message=0x2a3a7b20 "Operation timed out") at sslconn.c:86
#11 0x28de5376 in purple_proxy_connect_data_disconnect (
    connect_data=0x2a37e3d0, error_message=0x2a3a7b20 "Operation timed out")
    at proxy.c:587
#12 0x28de5ee6 in socket_ready_cb (data=0x2a37e3d0, source=11, cond=3)
    at proxy.c:672
#13 0x080ac5e3 in pidgin_io_invoke (source=0x2a37d540, condition=Variable 
"condition" is not available.
)
    at gtkeventloop.c:73
#14 0x292877ee in g_io_unix_dispatch (source=0x2a37a830, 
    callback=0x80ac5a0 <pidgin_io_invoke>, user_data=0x2a3a58f0)
    at giounix.c:162
#15 0x292367fe in g_main_dispatch (context=0x29841080) at gmain.c:1960
#16 0x29237daf in IA__g_main_context_dispatch (context=0x29841080)
    at gmain.c:2513
#17 0x292382c5 in g_main_context_iterate (context=0x29841080, block=1, 
    dispatch=1, self=0x29809040) at gmain.c:2591
#18 0x29238b19 in IA__g_main_loop_run (loop=0x2a3cc750) at gmain.c:2799
#19 0x28332020 in IA__gtk_main () at gtkmain.c:1219
#20 0x080c7002 in main (argc=Cannot access memory at address 0x5a5a5a5a
) at gtkmain.c:979

Original issue reported on code.google.com by goo...@dougbarton.us on 1 Jul 2010 at 8:23

[GoogleCodeExporter]

keeps giving me invalid certs on occasion.. started more today

Original comment by sparkmon...@gmail.com on 13 Jul 2010 at 11:47

[GoogleCodeExporter]

oh and if you go away for a while its doing this... you could get upto 73 
windows with in an hour asking to auth or deny

Original comment by sparkmon...@gmail.com on 13 Jul 2010 at 11:49

[GoogleCodeExporter]

I'm getting lots of untrusted certificate notifications (like 1 every minute 
and ah half sometimes, it seems like) with Pidgin 2.6.6 and mbpidgin 0.3.0 on 
Windows XP. I haven't had Pidgin crash from it yet, as far as I know. I guess I 
should try updating Pidgin; I just found out there was a newer release (2.7.1).

Original comment by laptop...@gmail.com on 14 Jul 2010 at 6:26

[GoogleCodeExporter]

I guess it is the same issue as #212.

Original comment by e.a.agaf...@gmail.com on 24 Jan 2011 at 9:49

[GoogleCodeExporter]

Original comment by somsaks on 24 Jan 2011 at 9:50

• Changed state: Verified