gwibber-bugs team mailing list archive

[Bug Watch Updater <789851@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=719448.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2011-07-06T21:43:01+00:00 Gerry wrote:

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

Reply at: https://bugs.launchpad.net/gwibber/+bug/789851/comments/15

------------------------------------------------------------------------
On 2011-07-07T14:49:43+00:00 Tom wrote:

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.

Reply at: https://bugs.launchpad.net/gwibber/+bug/789851/comments/17

------------------------------------------------------------------------
On 2011-07-07T14:51:15+00:00 Fedora wrote:

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

Reply at: https://bugs.launchpad.net/gwibber/+bug/789851/comments/18

------------------------------------------------------------------------
On 2011-07-07T14:51:24+00:00 Fedora wrote:

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

Reply at: https://bugs.launchpad.net/gwibber/+bug/789851/comments/19

------------------------------------------------------------------------
On 2011-07-08T17:13:44+00:00 Pete wrote:

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).

Reply at: https://bugs.launchpad.net/gwibber/+bug/789851/comments/23

------------------------------------------------------------------------
On 2011-07-08T18:00:14+00:00 Fedora wrote:

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).

Reply at: https://bugs.launchpad.net/gwibber/+bug/789851/comments/24

------------------------------------------------------------------------
On 2011-07-09T03:29:32+00:00 Gerry wrote:

Upgrade gwibber-3.1.0-2.fc15 and then remove/add your twitter account in
order to utilize the new OAuth method

Reply at: https://bugs.launchpad.net/gwibber/+bug/789851/comments/26

------------------------------------------------------------------------
On 2011-07-18T22:26:36+00:00 Fedora wrote:

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.

Reply at: https://bugs.launchpad.net/gwibber/+bug/789851/comments/27

------------------------------------------------------------------------
On 2011-07-18T22:40:16+00:00 Fedora wrote:

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.

Reply at: https://bugs.launchpad.net/gwibber/+bug/789851/comments/28


** Changed in: gwibber (Fedora)
       Status: Unknown => Fix Released

** Changed in: gwibber (Fedora)
   Importance: Unknown => Undecided

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/789851

Title:
  Direct Messages don't work since July 1st, 2011

Status in Gwibber:
  Fix Released
Status in gwibber package in Ubuntu:
  Fix Released
Status in gwibber package in Debian:
  New
Status in gwibber package in Fedora:
  Fix Released

Bug description:
  According to the Twitter API team, users will not be able to access
  Direct Messages by default after June 30th, 2011. For more on this,
  see [1] and [2].

  It should not require any change in the codebase, just a change in
  permissions level on dev.twitter.com [3]

  [1] http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e954fc0f8b5aa6ec?pli=1
  [2] http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7798d7f728170c5f#
  [3] http://dev.twitter.com

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/789851/+subscriptions