stream update in gwibber don't work no more

Bug #604716 reported by Bernd Schlapsi on 2010-07-12
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: gwibber

When I start gwibber on the command line with "gwibber --debug" I get the following output:

No dbus monitor yet
Updating...
Updating...

** (gwibber:5684): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:5684): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:5684): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
ERROR:dbus.proxies:Introspect error on com.Gwibber.Accounts:/com/gwibber/Accounts: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Accounts was not provided by any .service files
ERROR:dbus.proxies:Introspect error on com.Gwibber.Streams:/com/gwibber/Streams: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.Gwibber.Streams was not provided by any .service files
/usr/bin/gwibber:68: GtkWarning: gtk_container_add: assertion `GTK_IS_CONTAINER (container)' failed
  gtk.main()
No dbus monitor yet
Updating...
Updating...
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 68, in <module>
    gtk.main()
KeyboardInterrupt

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gwibber 2.30.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Jul 12 19:35:23 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100403)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gwibber

Bernd Schlapsi (bernd-sch) wrote :
Omer Akram (om26er) wrote :

Thanks for the bug report. can you please go to software sources and enable lucid-proposed and update gwibber to the proposed version. that version solves many problems.

Changed in gwibber (Ubuntu):
status: New → Incomplete
Bernd Schlapsi (bernd-sch) wrote :

I updated to package version "2.30.1-0ubuntu1" and now I'm getting the following error with "gwibber --debug".
The latest entry in my stream is 22 hours old :-(

** (gwibber:8323): WARNING **: Trying to register gtype 'WnckWindowState' as enum when in fact it is of type 'GFlags'

** (gwibber:8323): WARNING **: Trying to register gtype 'WnckWindowActions' as enum when in fact it is of type 'GFlags'

** (gwibber:8323): WARNING **: Trying to register gtype 'WnckWindowMoveResizeMask' as enum when in fact it is of type 'GFlags'
No dbus monitor yet
Updating...
ERROR:dbus.proxies:Introspect error on com.Gwibber.Service:/com/gwibber/Service: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Traceback (most recent call last):
  File "/usr/bin/gwibber", line 67, in <module>
    client.Client()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 447, in __init__
    self.w = GwibberClient()
  File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 29, in __init__
    self.model = gwui.Model()
  File "/usr/lib/python2.6/dist-packages/gwibber/gwui.py", line 43, in __init__
    self.services = json.loads(self.daemon.GetServices())
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Victor Vargas (kamus) on 2010-07-13
Changed in gwibber (Ubuntu):
importance: Undecided → Low
Bernd Schlapsi (bernd-sch) wrote :

Is there a workaround for this problem? Updating my stream dont' work and so gwibber is useless!
(at the moment) I switched to Pino. Pino needs more features, but it's so much faster than gwibber

Victor Vargas (kamus) wrote :

@Bernd, Please could you run in a terminal: gwibber-service -d -o and attach all resulted output to a textfile (following your steps to reproduce this issue), Thanks!

Bernd Schlapsi (bernd-sch) wrote :

Since a few day I'm using the gwibber-daily-ppa. At the moment the stream update works fine
This is the output with the latest version in the ppa:

gwibber-service -d -o
Updating...
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Monitors are up
Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - Tue Jul 20 22:00:20 2010 **
Gwibber Dispatcher: DEBUG <identica:receive> Performing operation
Gwibber Dispatcher: DEBUG <identica:responses> Performing operation
Gwibber Dispatcher: DEBUG <facebook:receive> Performing operation
Gwibber Dispatcher: DEBUG <facebook:images> Performing operation
Gwibber Dispatcher: DEBUG <facebook:responses> Performing operation
Gwibber Dispatcher: DEBUG <identica:private> Performing operation
Gwibber Dispatcher: DEBUG <identica:responses> Finished operation
Gwibber Dispatcher: DEBUG <STATS> facebook:images account:c5ff69a119b9e0a8ebf0676c05f14024 since:2010-07-12 21:36:00.00 size:808
Gwibber Dispatcher: INFO Facebook error 4 - Application request limit reached
Gwibber Dispatcher: DEBUG <facebook:images> Finished operation
Gwibber Dispatcher: DEBUG <identica:receive> Adding record
Gwibber Dispatcher: DEBUG <STATS> facebook:receive account:c5ff69a119b9e0a8ebf0676c05f14024 since:2010-07-20 21:14:42.00 size:614
Gwibber Dispatcher: INFO Facebook error 4 - Application request limit reached
Gwibber Dispatcher: DEBUG <identica:private> Finished operation
Gwibber Dispatcher: DEBUG <facebook:receive> Finished operation
Gwibber Dispatcher: DEBUG <identica:receive> Finished operation
Gwibber Dispatcher: DEBUG <STATS> facebook:responses account:c5ff69a119b9e0a8ebf0676c05f14024 since:2010-05-12 09:52:33.00 size:778
Gwibber Dispatcher: INFO Facebook error 4 - Application request limit reached
Gwibber Dispatcher: DEBUG <facebook:responses> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - ['Success', 'Success', 'Success', 'Success', 'Success', 'Success']
Gwibber Dispatcher: DEBUG Checking message 42597208 timestamp (2010-07-20 21:59:45.00) to see if it is newer than 2010-07-20 21:50:22.64
Gwibber Dispatcher: DEBUG Message 42597208 newer than 2010-07-20 21:50:22.64, notifying

Omer Akram (om26er) wrote :

the problem you are facing is because facebook is throttling gwibber. your logs say "Gwibber Dispatcher: INFO Facebook error 4 - Application request limit reached" previously gwibber downloaded 270kb data on every refresh even if there was nothing new. now that problem is solved and you should use the latest gwibber its in updates.. I am marking this bug as a duplicate of the other bug.. read https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/595265/comments/69 for more information

Changed in gwibber (Ubuntu):
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers