Failed to communicate with Failed to communicate with
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I am using Ubuntu 10.04 Beta 1
$ dpkg -s gwibber
Package: gwibber
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 2636
Maintainer: Ubuntu Developers <email address hidden>
Architecture: all
Version: 2.29.92.1-0ubuntu1
I have two twitter and identi.ca, but not show me nothing in main windows, the log file below:
2010-03-21 03:33:40,305 - Gwibber GNOME Client - INFO - Running from the system path
2010-03-21 03:33:42,793 - Gwibber Service - INFO - Running from the system path
2010-03-21 03:33:44,449 - Gwibber Accounts - INFO - Running from the system path
2010-03-21 03:34:11,806 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:11,807 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:11,808 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-03-21 03:34:11,808 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:11,809 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:11,809 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-03-21 03:34:19,877 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:19,878 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:19,878 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-03-21 03:34:19,879 - Gwibber Dispatcher - INFO - Loading complete: 1 - ['Failure', 'Failure', 'Failure']
2010-03-21 03:34:22,107 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:22,108 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:22,108 - Gwibber Dispatcher - ERROR - <identica:receive> Operation failed
2010-03-21 03:34:22,119 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:22,119 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:22,119 - Gwibber Dispatcher - ERROR - <identica:
2010-03-21 03:34:23,205 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:23,205 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:23,206 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-03-21 03:34:23,218 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:23,218 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:23,219 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-03-21 03:34:30,176 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:30,176 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:30,176 - Gwibber Dispatcher - ERROR - <identica:private> Operation failed
2010-03-21 03:34:30,177 - Gwibber Dispatcher - INFO - Loading complete: 2 - ['Failure', 'Failure', 'Failure']
2010-03-21 03:34:31,295 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:31,296 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:31,296 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-03-21 03:34:31,299 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:31,300 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:31,300 - Gwibber Dispatcher - ERROR - <identica:receive> Operation failed
2010-03-21 03:34:39,367 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:39,368 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:39,369 - Gwibber Dispatcher - ERROR - <identica:
2010-03-21 03:34:39,387 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 03:34:39,388 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 03:34:39,388 - Gwibber Dispatcher - ERROR - <identica:private> Operation failed
2010-03-21 03:34:39,389 - Gwibber Dispatcher - INFO - Loading complete: 3 - ['Failure', 'Failure', 'Failure', 'Failure', 'Failure', 'Failure']
2010-03-21 03:36:11,766 - Gwibber Dispatcher - INFO - Gwibber Service is being shutdown
2010-03-21 03:36:11,767 - Gwibber GNOME Client - INFO - Gwibber Client quit
2010-03-21 03:36:11,828 - Gwibber GNOME Client - INFO - Gwibber Client closed
2010-03-21 18:45:29,915 - Gwibber Service - INFO - Running from the system path
2010-03-21 18:45:41,032 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:45:41,033 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:45:41,033 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-03-21 18:45:41,034 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:45:41,035 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:45:41,035 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-03-21 18:45:49,249 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:45:49,249 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:45:49,250 - Gwibber Dispatcher - ERROR - <identica:receive> Operation failed
2010-03-21 18:45:49,257 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:45:49,257 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:45:49,257 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-03-21 18:45:57,401 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:45:57,401 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:45:57,401 - Gwibber Dispatcher - ERROR - <identica:
2010-03-21 18:45:57,414 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:45:57,415 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:45:57,415 - Gwibber Dispatcher - ERROR - <identica:private> Operation failed
2010-03-21 18:45:57,416 - Gwibber Dispatcher - INFO - Loading complete: 1 - ['Failure', 'Failure', 'Failure', 'Failure', 'Failure', 'Failure']
2010-03-21 18:50:40,662 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:50:40,663 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:50:40,663 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-03-21 18:50:40,667 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:50:40,668 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:50:40,668 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-03-21 18:50:48,731 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:50:48,732 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:50:48,732 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-03-21 18:50:48,757 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:50:48,758 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:50:48,758 - Gwibber Dispatcher - ERROR - <identica:receive> Operation failed
2010-03-21 18:50:56,817 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:50:56,818 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:50:56,818 - Gwibber Dispatcher - ERROR - <identica:
2010-03-21 18:50:56,840 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:50:56,840 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:50:56,841 - Gwibber Dispatcher - ERROR - <identica:private> Operation failed
2010-03-21 18:50:56,842 - Gwibber Dispatcher - INFO - Loading complete: 2 - ['Failure', 'Failure', 'Failure', 'Failure', 'Failure', 'Failure']
2010-03-21 18:55:43,150 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:55:43,149 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:55:43,390 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:55:43,390 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:55:43,390 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-03-21 18:55:43,390 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-03-21 18:55:51,620 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:55:51,620 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:55:51,620 - Gwibber Dispatcher - ERROR - <twitter:private> Operation failed
2010-03-21 18:55:51,624 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:55:51,625 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:55:51,625 - Gwibber Dispatcher - ERROR - <identica:receive> Operation failed
2010-03-21 18:55:59,716 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:55:59,717 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-03-21 18:55:59,717 - Gwibber Dispatcher - ERROR - <identica:private> Operation failed
2010-03-21 18:55:59,739 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-03-21 18:55:59,740 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
Changed in gwibber: | |
status: | New → Confirmed |
I upgraded my Lucid from beta 2 to RC. I deleted all things of beta 2 (I am using this in my virtual machine environment) and installed RC from scratch. In this condition, I tried gwibber as the first starting application, but this still occurred.
ubuntu-rc:~> dpkg -s gwibber ------- -@lists. ubuntu. com> egenix- mxdatetime, python-simplejson, python-webkit, librsvg2-2, librsvg2-common, python-imaging, python-xdg, python-mako, python-gtkspell, python-wnck, python- desktopcouch- records, gwibber-service (= 2.30.0.1-0ubuntu1), python (>= 2.6), python-central (>= 0.6.11) autostart/ gwibber. desktop ------- ------- ------- ------- ------- ---- /launchpad. net/gwibber
Package: gwibber
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 2640
Maintainer: Ubuntu Developers <------
Architecture: all
Version: 2.30.0.1-0ubuntu1
Depends: python-dbus, python-gtk2, python-gconf, python-
Suggests: gwibber-themes
Conffiles:
/etc/xdg/
Description: Open source social networking client for GNOME
Gwibber is a social networking client for GNOME. It supports Facebook,
Twitter, Identi.ca, StatusNet, FriendFeed, Qaiku, Flickr, and Digg.
.
This package includes the Gwibber desktop client
Homepage: https:/
Python-Version: >=2.6
== from ~/.cache/ gwibber/ gwibber. log /twitter. com/statuses/ mentions. json?count= 200 /twitter. com/statuses/ home_timeline. json?count= 200 /twitter. com/statuses/ home_timeline. json?count= 200 /twitter. com/statuses/ mentions. json?count= 200
2010-04-27 09:28:10,535 - Gwibber GNOME Client - INFO - Running from the system path
2010-04-27 09:28:28,303 - Gwibber Service - INFO - Running from the system path
2010-04-27 09:28:29,893 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-04-27 09:28:30,875 - Gwibber Accounts - INFO - Running from the system path
2010-04-27 09:28:44,248 - Gwibber Dispatcher - INFO - Gwibber Service is reloading account credentials
2010-04-27 09:28:52,714 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-04-27 09:28:52,716 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-04-27 09:28:52,716 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-04-27 09:28:52,724 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-04-27 09:28:52,727 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-04-27 09:28:52,727 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-04-27 09:28:55,812 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-04-27 09:28:55,815 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-04-27 09:28:55,817 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-04-27 09:28:55,819 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-04-27 09:28:55,819 - Gwibber Dispatcher - ERROR - <twitter:receive> Operation failed
2010-04-27 09:28:55,819 - Gwibber Dispatcher - ERROR - <twitter:responses> Operation failed
2010-04-27 09:29:00,817 - Gwibber Dispatcher - E...