Comment 2 for bug 585516

The error in bug #522538 is different. In that bug it is a socket error (connection refused). Here it is an AttributeError due to 'sock' being None. I get this particular error every time immediately when I start Gwibber. I never get the error in bug #522538.

I started getting the bug after I tried File -> New Stream (or something like that, can't open gwibber to see), and my gwibber window went blank. I closed it and tried to restart it, but it didn't work. Running in the command line gives the above output precisely.

I don't think this is a duplicate of bug #522538.