Comment 11 for bug 613420

Revision history for this message
Pedro Bessa (deltrem1984) wrote :

I guess I have to wait:

deltrem@deltrem-desktop:~/gwibber-2.30$ ./bin/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 - Wed Aug 25 18:19:39 2010 **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: INFO Twitter failure - This account is locked due to too many failed login attempts -- try again in 1499 seconds
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: INFO Twitter failure - This account is locked due to too many failed login attempts -- try again in 1498 seconds
Gwibber Dispatcher: DEBUG <twitter:receive> Finished operation
Gwibber Dispatcher: INFO Twitter failure - This account is locked due to too many failed login attempts -- try again in 1496 seconds
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - ['Success', 'Success', 'Success']
^CTraceback (most recent call last):
  File "./bin/gwibber-service", line 83, in <module>
    loop.run()