Bug 495159

Summary: Gwibber not displaying twitter timeline due to API change upstream requiring GET instead of POST
Product: [Fedora] Fedora Reporter: James Gregory-Monk <jgxenite>
Component: gwibberAssignee: Ian Weller <ian>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 10CC: ian, ssiren, wmealing
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: https://bugs.launchpad.net/gwibber/+bug/358341
Whiteboard:
Fixed In Version: 1.0.1-1.286bzr.fc10 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-22 00:51:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description James Gregory-Monk 2009-04-09 23:46:55 UTC
Description of problem:
As of this morning, Twitter deprecated part of the API which Gwibber uses to query for timeline updates. This means that Twitter support is now broken in Gwibber.

While an official release hasn't been sent out yet, it is possible to patch Gwibber, based on the updates made upstream, and was wondering if it was possible to update Gwibber to temporarily fix this issue (until an official release is made).

The diff for the fix is available at:
http://bazaar.launchpad.net/~gwibber-committers/gwibber/trunk/revision/286/gwibber/microblog/twitter.py

Version-Release number of selected component (if applicable):
Gwibber 0.9.1

How reproducible:
Always

Steps to Reproduce:
1. Load Gwibber and add a Twitter account
2. Attempt to retrieve the timeline, which will fail with HTTP error 400
  
Actual results:
The timeline fails to load with HTTP error 400

Expected results:
The timeline and replies should load in the relevant tabs

Comment 1 Ian Weller 2009-04-10 01:41:17 UTC
Thanks for the reminder, was going to get to this later today but forgot ;)

Comment 2 Fedora Update System 2009-04-10 02:53:28 UTC
gwibber-1.0.1-1.286bzr.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/gwibber-1.0.1-1.286bzr.fc10

Comment 3 James Gregory-Monk 2009-04-10 08:29:59 UTC
I've just installed the updated version and it works fine for me - thanks for fixing this Ian

Comment 4 Wade Mealing 2009-04-12 16:35:36 UTC
Confirmed fixed.

For anyone else coming across this bug.  You can tell if this affects you by going to the View menu -> Errors and looking for "Error 400" messages associated to the twitter account.

Comment 5 Fedora Update System 2009-04-13 19:39:18 UTC
gwibber-1.0.1-1.286bzr.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gwibber'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-3556

Comment 6 Sami Siren 2009-04-17 06:10:08 UTC
I just installed gwibber.noarch 0:1.0.1-1.286bzr.fc10 and I can see my twitter feed again.

Comment 7 Fedora Update System 2009-04-22 00:51:42 UTC
gwibber-1.0.1-1.286bzr.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.