Bug 719448 - Gwibber can not view Direct Messages due to the new OAuth method
Summary: Gwibber can not view Direct Messages due to the new OAuth method
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gwibber
Version: 15
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-06 21:43 UTC by Gerry
Modified: 2011-07-18 22:40 UTC (History)
2 users (show)

Fixed In Version: gwibber-3.1.0-2.fc15
Clone Of:
Environment:
Last Closed: 2011-07-18 22:26:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gerry 2011-07-06 21:43:01 UTC
Description of problem:
I can't view any direct message. The following message displays at the top of my Messages list:
This application is not allowed to access or delete your direct messages

Version-Release number of selected component (if applicable):
gwibber-3.1.0-1.fc15.noarch

How reproducible:
100%

Steps to Reproduce:
1. Launch gwibber
2. From the left nagivation panel, click Private
3. No direct messages are observed
4. Wait a minute or less
5. Receive the error message: This application is not allowed to access or delete your direct messages
  
Actual results:
Can't view any of the direct messages that I receive

Expected results:
View any of the direct messages that I receive

Additional info:
*** Debug result
$ gwibber --debug
{}
/usr/lib/python2.7/site-packages/gwibber/gwui.py:875: GtkWarning: gtk_box_pack: assertion `child->parent == NULL' failed
  self.pack_start(content_area, False)
Gwibber GNOME Client: INFO     Gwibber Client closed

*** Not certain but perhaps a step to fix OAuth issue with the Fedora maintained Gwibber?
http://groups.google.com/group/twitter-api-announce/browse_thread/thread/4956a4dd169be70c

Comment 1 Tom "spot" Callaway 2011-07-07 14:49:43 UTC
Yeah, you were right about the OAuth issue, but there was another issue too, where the last update was not using the Fedora OAuth credentials. Both should be fixed, I can see my direct messages in testing. Please test and let me know if it works for you.

Comment 2 Fedora Update System 2011-07-07 14:51:15 UTC
gwibber-3.1.0-2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/gwibber-3.1.0-2.fc14

Comment 3 Fedora Update System 2011-07-07 14:51:24 UTC
gwibber-3.1.0-2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/gwibber-3.1.0-2.fc15

Comment 4 Pete Zaitcev 2011-07-08 17:13:44 UTC
It still happens with 3.1.0-2.fc14. I'm wondering if I need to force
reauthorization somehow (there is no button in account page).

Comment 5 Fedora Update System 2011-07-08 18:00:14 UTC
Package gwibber-3.1.0-2.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gwibber-3.1.0-2.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/gwibber-3.1.0-2.fc15
then log in and leave karma (feedback).

Comment 6 Gerry 2011-07-09 03:29:32 UTC
Upgrade gwibber-3.1.0-2.fc15 and then remove/add your twitter account in order to utilize the new OAuth method

Comment 7 Fedora Update System 2011-07-18 22:26:36 UTC
gwibber-3.1.0-2.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2011-07-18 22:40:16 UTC
gwibber-3.1.0-2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.