retrieve messages KeyError: 'stories' when updating digg

Bug #352226 reported by RyanK
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Gwibber
Fix Released
Undecided
Ken VanDine
2.32
Fix Released
Low
Ken VanDine
3.0
Fix Released
Undecided
Ken VanDine
gwibber (Ubuntu)
Fix Released
Medium
Ken VanDine
Maverick
Fix Released
Undecided
Unassigned

Bug Description

Installed Gwibber on the Jaunty beta Live CD, and was not able to add my Digg Account.

With the following message in the error log:
retrieve messages
KeyError: 'stories'

Revision history for this message
RyanK (ryank) wrote :

This just started working 2 days later. I haven't changed anything that I'm aware of on the system so perhaps the issue was an issue on digg's side.

Will leave this issue open for a little while to see if it resurfaces.

Revision history for this message
sathyz (sathyz) wrote :

I'm facing the same problem. I'm on Debian (Squeeze).
Gwibber : 1.0.2

Traceback (most recent call last):
  File "/usr/local/lib/python2.5/site-packages/gwibber/microblog/__init__.py", line 49, in get_data
    for message in method(client):
  File "/usr/local/lib/python2.5/site-packages/gwibber/microblog/digg.py", line 89, in receive
    for data in self.get_diggs():
  File "/usr/local/lib/python2.5/site-packages/gwibber/microblog/digg.py", line 83, in get_diggs
    (self.account["username"])))["stories"]
KeyError: 'stories'

Revision history for this message
Alexander Sack (asac) wrote :

the new version in karmic makes a good step forward. please that the package. If you have no chance to run karmic, try the packages from the gwibber daily: https://edge.launchpad.net/~gwibber-daily/+archive/ppa - those match more or less what is in karmic.

Changed in gwibber (Ubuntu):
status: New → Incomplete
Alexander Sack (asac)
Changed in gwibber (Ubuntu):
importance: Undecided → Low
Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you encounter that this issue is still occurring or even better if you can check in latest Ubuntu Karmic version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!

Changed in gwibber (Ubuntu):
status: Incomplete → Invalid
Changed in gwibber:
status: New → Invalid
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

Reproduced on the latest version from trunk (rev. 868)

Changed in gwibber:
status: Invalid → Confirmed
Changed in gwibber (Ubuntu):
status: Invalid → Confirmed
tags: added: digg
Changed in gwibber:
assignee: nobody → Ken VanDine (ken-vandine)
status: Confirmed → Fix Committed
milestone: none → 3.0
Changed in gwibber (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
Revision history for this message
Victor Vargas (kamus) wrote :

recently tried on 2.32.0.1-0ubuntu1 and same behaviour.

Changed in gwibber (Ubuntu):
status: Confirmed → Triaged
importance: Low → Medium
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted gwibber into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in gwibber (Ubuntu):
status: Triaged → Fix Committed
Changed in gwibber (Ubuntu Maverick):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Omer Akram (om26er) wrote :

i have been using the proposed gwibber for 7 days and have not found any regressions. tried adding digg account and refreshed it multiple times but did not see any such logs. though the stream was empty(which would be another bug).

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gwibber - 2.32.0.2-0ubuntu1

---------------
gwibber (2.32.0.2-0ubuntu1) maverick-proposed; urgency=low

  * New upstream release (LP: #660693)
    - Reuse the libproxy.ProxyFactory object to prevent a race
      condition (LP: #651761)
    - Facebook: Check for new messages since "updated_time" instead
      of "created_time", to prevent losing status updates (LP: #541831)
    - Facebook: Better handling of data returned from facebook (LP: #615339)
    - Facebook: fixed matching of uid with profiles (LP: #524510)
    - Facebook: fixed missing notifications (LP: #575394)
    - Facebook: when checking for new content, use localtime
    - Update existing record if it conflicts instead of just
      ignoring it (LP: #541831)
    - Added a missing import to properly log failure on avatar resize
    - Fix for internal Digg errors, thanks Vadim Rutkovsky (LP: #352226)
    - Branch fixes gwibber icon is broken on the right
      side, thanks Vish. (LP: #655159)
    - start gwibber-service anytime the client needs it, not just for
      service operations
    - dropped print statement used for debugging scrolling
 -- Ken VanDine <email address hidden> Wed, 13 Oct 2010 15:19:46 -0400

Changed in gwibber (Ubuntu Maverick):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

copied to natty as well.

Changed in gwibber (Ubuntu):
status: Fix Committed → Fix Released
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.