The same happens with me, though my logs are more innocuous. It appears that on the first refresh after startup, the gwibber service starts to consume 100% of one of my CPUs.
My log has a facebook failure when the CPU consumption starts: 2010-03-31 17:02:40,178 - Gwibber Dispatcher - ERROR - <facebook:images> Operation failed 2010-03-31 17:02:40,181 - Gwibber Dispatcher - INFO - Loading complete: 2 - ['Success', 'Success', 'Failure'] -- gwibber-service stays at 90% cpu after adding twitter account https://bugs.launchpad.net/bugs/545841 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
