← Back to team overview

gwibber-bugs team mailing list archive

[Bug 789851] Re: Direct Messages don't work since July 1st, 2011

 

I got this ; at this point, the red banner with the error is showing.

adrian@motoko:~/.cache/gwibber$ gwibber -d
ERROR:dbus.proxies:Introspect error on com.Gwibber.Messages:/com/gwibber/Messages: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Messages was not provided by any .service files

(gwibber:14049): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed
(gwibber:14049): LIBDBUSMENU-GTK-DEBUG: Could not handle image type 6

{}
/usr/lib/python2.7/dist-packages/gwibber/gwui.py:870: GtkWarning: gtk_box_pack: assertion `child->parent == NULL' failed
  self.pack_start(content_area, False)

-- 
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:
  New
Status in “gwibber” package in Ubuntu:
  Triaged

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


References