Thank you for taking the time to report this bug and helping to make
Ubuntu better. Part of this particular bug has already been reported and
in bug 626023, so this bug will be used to track the latter issue.
Please look at the other bug report to see if there is any missing
information that you can provide regarding the Buzz issue, or to see if
there is a workaround for the bug. Additionally, any further discussion
regarding that bug, it should occur in the other report. Feel free to
continue to report any other bugs you may find and this bug will be left
open to track the Ping.FM issue.
I was able to reproduce the Ping.FM issue noted in the original report
by doing the following:
1. Creating a Ping.FM account
2. Setting up the Ping.FM account in Gwibber using the API key provided by
Ping.FM
3. Attempting to send multiple messages to ultimately route to other social
media platform from Ping.FM
4. No messages after left the Gwibber platform or reached my Ping.FM account.
Output from 'gwibber-service -d -o' as recommended in bug #626023:
**STARTUP**
**Please note the Google API was edited for privacy**
abuda...@ourfamilys-desktop:~$ gwibber-service -d -o
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Refresh interval is set to 15
Gwibber Dispatcher: DEBUG ** Starting Refresh - 2010-11-23 00:22:07.70 **
Gwibber Dispatcher: DEBUG <buzz:receive> Performing operation
Gwibber Dispatcher: DEBUG libproxy: getting proxies
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/gwibber/microblog/network.py", line
53, in __init__
self.curl.perform()
error: (56, 'GnuTLS recv error (-9): A TLS packet with unexpected length was
received.')
Gwibber Dispatcher: ERROR Failed to communicate with
https://www.googleapis.com/buzz/v1/activities/@me/@consumption?oauth_nonce=0000000&oauth_timestamp=00000000&oauth_consumer_key=anonymous&oauth_signature_method=HMAC-SHA1&oauth_version=1.0&oauth_token=0000000000000&oauth_signature=000000000&alt=00000
Gwibber Dispatcher: ERROR <buzz:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line
79, in perform_operation
message_data = PROTOCOLS[account["service"]].Client(account)(opname, **args)
File "/usr/lib/python2.6/dist-packages/gwibber/microblog/buzz.py", line 117,
in __call__
return getattr(self, opname)(**args)
File "/usr/lib/python2.6/dist-packages/gwibber/microblog/buzz.py", line 120,
in receive
return self._get("activities/@me/@consumption")
File "/usr/lib/python2.6/dist-packages/gwibber/microblog/buzz.py", line 113,
in _get
if parse: return [getattr(self, "_%s" % parse)(m) for m in
data["data"][collection]]
KeyError: 'data'
Gwibber Dispatcher: INFO Loading complete: 1 - []
**SENDING MESSAGE FROM PING.FM**
Gwibber Dispatcher: DEBUG *** Sending Message ***
Gwibber Dispatcher: DEBUG <pingfm:send> Performing operation
Gwibber Dispatcher: DEBUG libproxy: getting proxies
Gwibber Dispatcher: DEBUG <pingfm:send> Finished operation
Gwibber Dispatcher: INFO Loading complete: 3 - []
** Summary changed:
- Send/Receive messages or posts for Google Buzz and Ping.fm accounts don't work
+ Gwibber: Send/Receive messages or posts for Ping.fm account doesn't work
** Changed in: gwibber (Ubuntu)
Status: New => Confirmed
--
Gwibber: Send/Receive messages or posts for Ping.fm account doesn't work
https://bugs.launchpad.net/bugs/680368
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
