This log looks useless. Seems to be the only relevant log. Nothing was
logged while I ran through these steps to reproduce the bug.

Nothing else logged when I start it from CLI.

$ tail -n 40 /home/divan/.cache/gwibber/gwibber.log 
2012-10-08 21:16:57,778 - Network      Thread-35     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:16:57,779 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 3
2012-10-08 21:16:57,780 - Network      Thread-37     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:16:57,781 - Network      Thread-36     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:16:57,783 - Network      Thread-37     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:16:57,783 - Dispatcher   Thread-35     :  INFO     - Loading 
complete: 36 - 0
2012-10-08 21:16:57,785 - Dispatcher   Thread-37     :  INFO     - Loading 
complete: 36 - 0
2012-10-08 21:16:57,785 - Dispatcher   Thread-36     :  INFO     - Loading 
complete: 36 - 0
2012-10-08 21:31:57,691 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 3
2012-10-08 21:31:57,691 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 0
2012-10-08 21:31:57,692 - Network      Thread-38     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:31:57,693 - Dispatcher   Thread-38     :  INFO     - Loading 
complete: 37 - 0
2012-10-08 21:31:57,694 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 3
2012-10-08 21:31:57,695 - Network      Thread-39     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:31:57,697 - Network      Thread-40     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:31:57,701 - Network      Thread-40     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:31:57,703 - Dispatcher   Thread-40     :  INFO     - Loading 
complete: 39 - 0
2012-10-08 21:31:57,706 - Dispatcher   Thread-39     :  INFO     - Loading 
complete: 39 - 0
2012-10-08 21:46:57,639 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 3
2012-10-08 21:46:57,639 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 0
2012-10-08 21:46:57,642 - Network      Thread-41     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:46:57,642 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 3
2012-10-08 21:46:57,644 - Network      Thread-42     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:46:57,650 - Dispatcher   Thread-42     :  INFO     - Loading 
complete: 41 - 0
2012-10-08 21:46:57,647 - Dispatcher   Thread-41     :  INFO     - Loading 
complete: 40 - 0
2012-10-08 21:46:57,646 - Network      Thread-43     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:46:57,656 - Network      Thread-43     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 21:46:57,660 - Dispatcher   Thread-43     :  INFO     - Loading 
complete: 42 - 0
2012-10-08 22:01:57,725 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 3
2012-10-08 22:01:57,725 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 0
2012-10-08 22:01:57,728 - Network      Thread-45     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 22:01:57,729 - Network      Thread-46     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 22:01:57,729 - Dispatcher   MainThread    :  INFO     - Running 
Jobs: 3
2012-10-08 22:01:57,733 - Network      Thread-46     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 22:01:57,734 - Dispatcher   Thread-46     :  INFO     - Loading 
complete: 44 - 0
2012-10-08 22:01:57,747 - Dispatcher   Thread-45     :  INFO     - Loading 
complete: 44 - 0
2012-10-08 22:01:57,754 - Network      Thread-44     :  ERROR    - Network 
failure: UNKNOWN
2012-10-08 22:01:57,762 - Dispatcher   Thread-44     :  INFO     - Loading 
complete: 45 - 0
2012-10-08 22:04:57,172 - root         MainThread    :  INFO     - Logger 
initialized
2012-10-08 22:04:57,172 - Accounts     MainThread    :  INFO     - Running from 
the system path

-- 
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/962535

Title:
  Gwibber in Ubuntu 12.04 will not complete facebook authorisation

Status in “gwibber” package in Ubuntu:
  Incomplete

Bug description:
  facebook reports access by the account but Gwibber [eventually]
  returns to "authourise" again - never allowing completion.  all
  details entered as per [sucessful] useage in Ubuntiu 10.04 & 11.10 -
  problems only in 12.o4 version / implementation of Gwibber.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gwibber 3.3.93-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Thu Mar 22 20:47:33 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   LANGUAGE=en_GB:en
   LANG=en_GB.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/962535/+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