[Bug 413376] [NEW] tweets go to Twitter but I can't receive tweets in gwibber 0.9.1

[threethirty]

Public bug reported:

Binary package hint: gwibber

Uubntu Version: 9.04
Package Version: 0.9.1
Expected: to get updates from Twitter
Instead: I don't get an updates from Twitter

Short Version: HTTPError: HTTP Error 400: Bad Requset when using Gwibber
version 0.9.1

Long Version: My tweets go to Twitter but I can't receive tweets.
Identi.ca (the only other account I have enabled) works without an
issue. If I go view the errors it lists "HTTPError: HTTP Error 400: Bad
Request" and then here is the out put when you double click the error:

File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 209, in receive
    for data in self.get_messages():
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 159, in get_messages
    urllib.urlencode({"count": self.account["receive_count"] or "20"})))
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 154, in connect
    url, data, {"Authorization": self.get_auth()})).read()
  File "/usr/lib/python2.6/urllib2.py", line 124, in urlopen
    return _opener.open(url, data, timeout)
  File "/usr/lib/python2.6/urllib2.py", line 389, in open
    response = meth(req, response)
  File "/usr/lib/python2.6/urllib2.py", line 502, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/lib/python2.6/urllib2.py", line 427, in error
    return self._call_chain(*args)
  File "/usr/lib/python2.6/urllib2.py", line 361, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.6/urllib2.py", line 510, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
HTTPError: HTTP Error 400: Bad Request

and running it through the terminal shows no output at all or I would
have posted that too.

** Affects: gwibber (Ubuntu)
     Importance: Undecided
         Status: New

-- 
tweets go to Twitter but I can't receive tweets in gwibber 0.9.1
https://bugs.launchpad.net/bugs/413376
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs