gwibber tries to call has_key on list (results in not updating streams)

Bug #576081 reported by Maciej Piechotka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gwibber
New
Undecided
Unassigned

Bug Description

% /usr/bin/gwibber-service -do
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Wed May 5 23:02:11 2010 **
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: ERROR <twitter:responses> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/dispatcher.py", line 75, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py", line 155, in responses
    return self._get("statuses/mentions.json", count=count, since_id=since)
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'list' object has no attribute 'has_key'

Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/dispatcher.py", line 75, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py", line 149, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py", line 136, in _get
    if data.has_key("error"):
AttributeError: 'list' object has no attribute 'has_key'

Gwibber Dispatcher: DEBUG <identica:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <identica:responses> Performing operation
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
error: (56, 'Peer closed the TLS connection')
Gwibber Dispatcher: ERROR Failed to communicate with https://identi.ca/api/statuses/mentions.json?count=200&since_id=23915625
Gwibber Dispatcher: ERROR <identica:responses> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/dispatcher.py", line 75, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/identica.py", line 144, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/identica.py", line 153, in responses
    return self._get("statuses/mentions.json", count=count, since_id=since)
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/identica.py", line 134, in _get
    if data.has_key("error"):
AttributeError: 'list' object has no attribute 'has_key'

Gwibber Dispatcher: DEBUG <identica:private> Performing operation
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/gwibber/microblog/network.py", line 32, in __init__
    self.curl.perform()
error: (56, 'Peer closed the TLS connection')
Gwibber Dispatcher: ERROR Failed to communicate with https://identi.ca/api/direct_messages.json?count=200
Gwibber Dispatcher: DEBUG <identica:private> Finished operation
Gwibber Dispatcher: DEBUG <identica:user_messages> Performing operation

Revision history for this message
Omer Akram (om26er) wrote :

@Maciej Piechotka instead of the error from terminal was there any other problem that you are facing with gwibber?

Revision history for this message
Maciej Piechotka (uzytkownik2) wrote :

Ups. I was sure I mentioned it - gwibber does not update message - any messages. Last message I see in gwibber is 32 days old.

summary: - gwibber tries to call has_key on list
+ gwibber tries to call has_key on list (results in not updating streams)
Revision history for this message
Omer Akram (om26er) wrote : Re: [Bug 576081] Re: gwibber tries to call has_key on list
Download full text (4.8 KiB)

This bug is certainly a duplicate of bug 530195 (i gave that bug title from
this bug ;))

On Mon, May 17, 2010 at 6:36 PM, Maciej Piechotka <email address hidden>wrote:

> Ups. I was sure I mentioned it - gwibber does not update message - any
> messages. Last message I see in gwibber is 32 days old.
>
> ** Summary changed:
>
> - gwibber tries to call has_key on list
> + gwibber tries to call has_key on list (results in not updating streams)
>
> --
> gwibber tries to call has_key on list (results in not updating streams)
> https://bugs.launchpad.net/bugs/576081
> You received this bug notification because you are subscribed to
> Gwibber.
>
> Status in Gwibber: New
>
> Bug description:
> % /usr/bin/gwibber-service -do
> Updating...
> Gwibber Dispatcher: DEBUG Setting up monitors
> Gwibber Dispatcher: DEBUG Monitors are up
> Gwibber Dispatcher: INFO Gwibber Service is reloading account
> credentials
> Gwibber Dispatcher: DEBUG Refresh interval is set to 5
> Gwibber Dispatcher: DEBUG ** Starting Refresh - Wed May 5 23:02:11 2010
> **
> Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
> Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
> Gwibber Dispatcher: ERROR <twitter:responses> Operation failed
> Gwibber Dispatcher: DEBUG Traceback:
> Traceback (most recent call last):
> File "/usr/lib64/python2.6/site-packages/gwibber/microblog/dispatcher.py",
> line 75, in perform_operation
> message_data = PROTOCOLS[account["protocol"]].Client(account)(opname,
> **args)
> File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py",
> line 146, in __call__
> return getattr(self, opname)(**args)
> File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py",
> line 155, in responses
> return self._get("statuses/mentions.json", count=count, since_id=since)
> File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py",
> line 136, in _get
> if data.has_key("error"):
> AttributeError: 'list' object has no attribute 'has_key'
>
> Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
> Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
> Gwibber Dispatcher: DEBUG Traceback:
> Traceback (most recent call last):
> File "/usr/lib64/python2.6/site-packages/gwibber/microblog/dispatcher.py",
> line 75, in perform_operation
> message_data = PROTOCOLS[account["protocol"]].Client(account)(opname,
> **args)
> File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py",
> line 146, in __call__
> return getattr(self, opname)(**args)
> File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py",
> line 149, in receive
> return self._get("statuses/home_timeline.json", count=count,
> since_id=since)
> File "/usr/lib64/python2.6/site-packages/gwibber/microblog/twitter.py",
> line 136, in _get
> if data.has_key("error"):
> AttributeError: 'list' object has no attribute 'has_key'
>
> Gwibber Dispatcher: DEBUG <identica:receive> Performing operation
> Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
> Gwibber Dispatcher: DEBUG <identica:responses> Performing operation
> Traceback (mo...

Read more...

Revision history for this message
Maciej Piechotka (uzytkownik2) wrote :

I tried to clean the desktopcouch (so far gwibber is only app using it) - it happens also on empty database.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.