| Summary: | Gwibber can not view Direct Messages due to the new OAuth method | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gerry <gerry> |
| Component: | gwibber | Assignee: | Tom "spot" Callaway <tcallawa> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | tcallawa, zaitcev |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gwibber-3.1.0-2.fc15 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-07-18 22:26:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
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. 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 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 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). 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). Upgrade gwibber-3.1.0-2.fc15 and then remove/add your twitter account in order to utilize the new OAuth method 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. 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. |
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