Comment 83 for bug 530195

Bharath,

Your problem seems to be different than mine. It seems more like a network
communication error (thats just my prima facie assessment) which if you look
at other items in the thread is probably due to some certificates issue.
This might just fix it for you :
https://bugs.launchpad.net/gwibber/+bug/530195/comments/6

While I edited twitter.py in dist-packages/.../ microblog in your case it is
not applicable since your problem seems to be a different one.

As a suggestion from abundant caution, perspective, if you are not sure,
wait a while longer for the bug fixes. Changing code without knowing the
implications could make things worse.

Cheers,
Dhananjay

On Fri, May 14, 2010 at 11:41 AM, Bharath C J
<email address hidden>wrote:

> Mr. Dhananjay,
>
> I have taken liberty to write to you, I hope you will excuse me for this.
>
> I am unable to load twitter.... and facebook also doesn't refresh
> properly.....
>
> Error:
> 2010-05-14 09:41:39,572 - Gwibber Dispatcher - ERROR - Failed to parse the
> response, error was: No JSON object could be decoded
> 2010-05-14 09:41:39,572 - Gwibber Dispatcher - ERROR - <facebook:images>
> Operation failed
> 2010-05-14 09:41:40,360 - Gwibber Dispatcher - ERROR - Failed to
> communicate with https://twitter.com/statuses/home_timeline.json?count=200
> 2010-05-14 09:41:40,360 - Gwibber Dispatcher - ERROR - Failed to parse the
> response, error was: No JSON object could be decoded
> 2010-05-14 09:41:40,361 - Gwibber Dispatcher - ERROR - <twitter:receive>
> Operation failed
>
> I am not a not a Techie (developer), I see many twitter.py files:
>
> /usr/lib/python2.6/dist-packages/gwibber/lib/gtk/twitter.py
> /usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py
> /usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.pyc
> /usr/share/pyshared/gwibber/lib/gtk/twitter.py
> /usr/share/pyshared/gwibber/microblog/twitter.py
>
> Which file should I edit.... Kindly help me out...
>
> Bharath
> 98450 76117
>
>
> On Thu, 2010-05-13 at 22:57 +0000, Dhananjay Nene wrote:
>
> After waiting for this bug to get fixed for a loooong time, I finally
> decided the best way was to investigate it myself by modifying the code.
>
> Turns out an exception was received at line 136 of twitter.py due to
> "unsupported locale setting"
>
> Changing line 12 of util/__init__.py to ->
> locale.setlocale(locale.LC_ALL, 'en_IN') Fixed it.
>
> (Note: en_IN is my default locale, will vary across installations)
>
> Maintainers kindly note and fix the problem.
>
> YoooHooo!, gwibber works for me now.
>
>
>

--
--------------------------------------------------------
blog: http://blog.dhananjaynene.com
twitter: http://twitter.com/dnene