Public bug reported:

Gwibber does not seem to be getting any updates on twitter.  Here's my
gwibber log from start to failure to update and including a "refresh":

2012-05-19 09:06:46,380 - root         MainThread    :  INFO     - Logger 
initialized
2012-05-19 09:06:46,380 - Service      MainThread    :  INFO     - Service 
starting
2012-05-19 09:06:46,381 - Service      MainThread    :  INFO     - Running from 
the source tree
2012-05-19 09:06:57,177 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 0
2012-05-19 09:06:57,177 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 0
2012-05-19 09:06:57,184 - Dispatcher   Thread-1      :  ERROR    - 
<twitter:receive> Operation failed
2012-05-19 09:06:57,191 - Dispatcher   Thread-1      :  INFO     - Loading 
Error: 0 - Error
2012-05-19 09:06:57,195 - Dispatcher   Thread-2      :  ERROR    - 
<twitter:responses> Operation failed
2012-05-19 09:06:57,201 - Dispatcher   Thread-2      :  INFO     - Loading 
Error: 0 - Error
2012-05-19 09:06:57,205 - Dispatcher   Thread-3      :  ERROR    - 
<twitter:private> Operation failed
2012-05-19 09:06:57,211 - Dispatcher   Thread-3      :  INFO     - Loading 
Error: 0 - Error
2012-05-19 09:06:57,215 - Dispatcher   Thread-4      :  ERROR    - 
<twitter:lists> Operation failed
2012-05-19 09:06:57,221 - Dispatcher   Thread-5      :  ERROR    - 
<twitter:user_messages> Operation failed
2012-05-19 09:06:57,225 - Dispatcher   Thread-4      :  INFO     - Loading 
Error: 0 - Error
2012-05-19 09:06:57,229 - Dispatcher   Thread-6      :  ERROR    - 
<twitter:user_messages> Operation failed
2012-05-19 09:06:57,242 - Dispatcher   Thread-7      :  ERROR    - 
<twitter:user_messages> Operation failed
2012-05-19 09:06:57,243 - Dispatcher   Thread-5      :  INFO     - Loading 
Error: 0 - Error
2012-05-19 09:06:57,253 - Dispatcher   Thread-8      :  ERROR    - 
<twitter:user_messages> Operation failed
2012-05-19 09:06:57,246 - Dispatcher   Thread-6      :  INFO     - Loading 
Error: 0 - Error
2012-05-19 09:06:57,256 - Dispatcher   Thread-7      :  INFO     - Loading 
Error: 0 - Error
2012-05-19 09:06:57,265 - Dispatcher   Thread-8      :  INFO     - Loading 
Error: 0 - Error
2012-05-19 09:06:57,266 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 10
2012-05-19 09:06:57,493 - Dispatcher   Thread-9      :  INFO     - Loading 
complete: 1 - 0
2012-05-19 09:06:59,561 - Twitter      Thread-10     :  ERROR    - Twitter 
failure - {...}
2012-05-19 09:06:59,562 - Dispatcher   Thread-10     :  ERROR    - 
<twitter:search> Operation failed
2012-05-19 09:06:59,563 - Dispatcher   Thread-10     :  INFO     - Loading 
Error: 1 - Error
2012-05-19 09:07:08,914 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 10
2012-05-19 09:07:08,914 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 0
2012-05-19 09:07:08,918 - Dispatcher   Thread-12     :  ERROR    - 
<twitter:responses> Operation failed
2012-05-19 09:07:08,928 - Dispatcher   Thread-11     :  ERROR    - 
<twitter:receive> Operation failed
2012-05-19 09:07:08,932 - Dispatcher   Thread-13     :  ERROR    - 
<twitter:private> Operation failed
2012-05-19 09:07:08,935 - Dispatcher   Thread-14     :  ERROR    - 
<twitter:user_messages> Operation failed
2012-05-19 09:07:08,939 - Dispatcher   Thread-15     :  ERROR    - 
<twitter:user_messages> Operation failed
2012-05-19 09:07:08,943 - Dispatcher   Thread-16     :  ERROR    - 
<twitter:user_messages> Operation failed
2012-05-19 09:07:08,945 - Dispatcher   Thread-12     :  INFO     - Loading 
Error: 1 - Error
2012-05-19 09:07:08,955 - Dispatcher   Thread-14     :  INFO     - Loading 
Error: 1 - Error
2012-05-19 09:07:08,959 - Dispatcher   Thread-17     :  ERROR    - 
<twitter:user_messages> Operation failed
2012-05-19 09:07:08,965 - Dispatcher   Thread-15     :  INFO     - Loading 
Error: 1 - Error
2012-05-19 09:07:08,968 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 9
2012-05-19 09:07:08,977 - Dispatcher   Thread-16     :  INFO     - Loading 
Error: 1 - Error
2012-05-19 09:07:08,981 - Dispatcher   Thread-13     :  INFO     - Loading 
Error: 1 - Error
2012-05-19 09:07:08,986 - Dispatcher   Thread-11     :  INFO     - Loading 
Error: 1 - Error
2012-05-19 09:07:08,999 - Dispatcher   Thread-17     :  INFO     - Loading 
Error: 1 - Error
2012-05-19 09:07:09,153 - Dispatcher   Thread-18     :  INFO     - Loading 
complete: 2 - 0
2012-05-19 09:07:10,339 - Twitter      Thread-19     :  ERROR    - Twitter 
failure - {...}
2012-05-19 09:07:10,341 - Dispatcher   Thread-19     :  ERROR    - 
<twitter:search> Operation failed
2012-05-19 09:07:10,342 - Dispatcher   Thread-19     :  INFO     - Loading 
Error: 2 - Error

ProblemType: Bug
DistroRelease: LinuxMint 12
Package: gwibber 3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Sat May 19 09:04:06 2012
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: gwibber
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gwibber (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 lisa

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/1001629

Title:
  not updating

Status in “gwibber” package in Ubuntu:
  New

Bug description:
  Gwibber does not seem to be getting any updates on twitter.  Here's my
  gwibber log from start to failure to update and including a "refresh":

  2012-05-19 09:06:46,380 - root         MainThread    :  INFO     - Logger 
initialized
  2012-05-19 09:06:46,380 - Service      MainThread    :  INFO     - Service 
starting
  2012-05-19 09:06:46,381 - Service      MainThread    :  INFO     - Running 
from the source tree
  2012-05-19 09:06:57,177 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 0
  2012-05-19 09:06:57,177 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 0
  2012-05-19 09:06:57,184 - Dispatcher   Thread-1      :  ERROR    - 
<twitter:receive> Operation failed
  2012-05-19 09:06:57,191 - Dispatcher   Thread-1      :  INFO     - Loading 
Error: 0 - Error
  2012-05-19 09:06:57,195 - Dispatcher   Thread-2      :  ERROR    - 
<twitter:responses> Operation failed
  2012-05-19 09:06:57,201 - Dispatcher   Thread-2      :  INFO     - Loading 
Error: 0 - Error
  2012-05-19 09:06:57,205 - Dispatcher   Thread-3      :  ERROR    - 
<twitter:private> Operation failed
  2012-05-19 09:06:57,211 - Dispatcher   Thread-3      :  INFO     - Loading 
Error: 0 - Error
  2012-05-19 09:06:57,215 - Dispatcher   Thread-4      :  ERROR    - 
<twitter:lists> Operation failed
  2012-05-19 09:06:57,221 - Dispatcher   Thread-5      :  ERROR    - 
<twitter:user_messages> Operation failed
  2012-05-19 09:06:57,225 - Dispatcher   Thread-4      :  INFO     - Loading 
Error: 0 - Error
  2012-05-19 09:06:57,229 - Dispatcher   Thread-6      :  ERROR    - 
<twitter:user_messages> Operation failed
  2012-05-19 09:06:57,242 - Dispatcher   Thread-7      :  ERROR    - 
<twitter:user_messages> Operation failed
  2012-05-19 09:06:57,243 - Dispatcher   Thread-5      :  INFO     - Loading 
Error: 0 - Error
  2012-05-19 09:06:57,253 - Dispatcher   Thread-8      :  ERROR    - 
<twitter:user_messages> Operation failed
  2012-05-19 09:06:57,246 - Dispatcher   Thread-6      :  INFO     - Loading 
Error: 0 - Error
  2012-05-19 09:06:57,256 - Dispatcher   Thread-7      :  INFO     - Loading 
Error: 0 - Error
  2012-05-19 09:06:57,265 - Dispatcher   Thread-8      :  INFO     - Loading 
Error: 0 - Error
  2012-05-19 09:06:57,266 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 10
  2012-05-19 09:06:57,493 - Dispatcher   Thread-9      :  INFO     - Loading 
complete: 1 - 0
  2012-05-19 09:06:59,561 - Twitter      Thread-10     :  ERROR    - Twitter 
failure - {...}
  2012-05-19 09:06:59,562 - Dispatcher   Thread-10     :  ERROR    - 
<twitter:search> Operation failed
  2012-05-19 09:06:59,563 - Dispatcher   Thread-10     :  INFO     - Loading 
Error: 1 - Error
  2012-05-19 09:07:08,914 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 10
  2012-05-19 09:07:08,914 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 0
  2012-05-19 09:07:08,918 - Dispatcher   Thread-12     :  ERROR    - 
<twitter:responses> Operation failed
  2012-05-19 09:07:08,928 - Dispatcher   Thread-11     :  ERROR    - 
<twitter:receive> Operation failed
  2012-05-19 09:07:08,932 - Dispatcher   Thread-13     :  ERROR    - 
<twitter:private> Operation failed
  2012-05-19 09:07:08,935 - Dispatcher   Thread-14     :  ERROR    - 
<twitter:user_messages> Operation failed
  2012-05-19 09:07:08,939 - Dispatcher   Thread-15     :  ERROR    - 
<twitter:user_messages> Operation failed
  2012-05-19 09:07:08,943 - Dispatcher   Thread-16     :  ERROR    - 
<twitter:user_messages> Operation failed
  2012-05-19 09:07:08,945 - Dispatcher   Thread-12     :  INFO     - Loading 
Error: 1 - Error
  2012-05-19 09:07:08,955 - Dispatcher   Thread-14     :  INFO     - Loading 
Error: 1 - Error
  2012-05-19 09:07:08,959 - Dispatcher   Thread-17     :  ERROR    - 
<twitter:user_messages> Operation failed
  2012-05-19 09:07:08,965 - Dispatcher   Thread-15     :  INFO     - Loading 
Error: 1 - Error
  2012-05-19 09:07:08,968 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 9
  2012-05-19 09:07:08,977 - Dispatcher   Thread-16     :  INFO     - Loading 
Error: 1 - Error
  2012-05-19 09:07:08,981 - Dispatcher   Thread-13     :  INFO     - Loading 
Error: 1 - Error
  2012-05-19 09:07:08,986 - Dispatcher   Thread-11     :  INFO     - Loading 
Error: 1 - Error
  2012-05-19 09:07:08,999 - Dispatcher   Thread-17     :  INFO     - Loading 
Error: 1 - Error
  2012-05-19 09:07:09,153 - Dispatcher   Thread-18     :  INFO     - Loading 
complete: 2 - 0
  2012-05-19 09:07:10,339 - Twitter      Thread-19     :  ERROR    - Twitter 
failure - {...}
  2012-05-19 09:07:10,341 - Dispatcher   Thread-19     :  ERROR    - 
<twitter:search> Operation failed
  2012-05-19 09:07:10,342 - Dispatcher   Thread-19     :  INFO     - Loading 
Error: 2 - Error

  ProblemType: Bug
  DistroRelease: LinuxMint 12
  Package: gwibber 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  Date: Sat May 19 09:04:06 2012
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: gwibber
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/1001629/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to