Bug definitely remains on 3.2.0-0ubuntu2 (3 days with no new tweets seems fairly suspicious :-).
Looking at my gwibber.log when I restart...
$ tail ~/.cache/gwibber/gwibber.log 2011-10-04 16:59:16,982 - Gwibber Service - INFO - Running from the system path 2011-10-04 16:59:31,387 - Gwibber Dispatcher - ERROR - Cannot parse message data: request 2011-10-04 16:59:31,388 - Gwibber Dispatcher - ERROR - Cannot parse message data: error 2011-10-04 16:59:31,415 - Gwibber Dispatcher - ERROR - Cannot parse message data: request 2011-10-04 16:59:31,416 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed 2011-10-04 16:59:32,960 - Gwibber Dispatcher - ERROR - Cannot parse message data: request 2011-10-04 16:59:32,960 - Gwibber Dispatcher - ERROR - Cannot parse message data: error 2011-10-04 16:59:34,364 - Gwibber Dispatcher - INFO - Loading complete: 1 - [] $
Bug definitely remains on 3.2.0-0ubuntu2 (3 days with no new tweets seems fairly suspicious :-).
Looking at my gwibber.log when I restart...
$ tail ~/.cache/ gwibber/ gwibber. log
2011-10-04 16:59:16,982 - Gwibber Service - INFO - Running from the system path
2011-10-04 16:59:31,387 - Gwibber Dispatcher - ERROR - Cannot parse message data: request
2011-10-04 16:59:31,388 - Gwibber Dispatcher - ERROR - Cannot parse message data: error
2011-10-04 16:59:31,415 - Gwibber Dispatcher - ERROR - Cannot parse message data: request
2011-10-04 16:59:31,416 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2011-10-04 16:59:32,960 - Gwibber Dispatcher - ERROR - Cannot parse message data: request
2011-10-04 16:59:32,960 - Gwibber Dispatcher - ERROR - Cannot parse message data: error
2011-10-04 16:59:34,364 - Gwibber Dispatcher - INFO - Loading complete: 1 - []
$