Gwibber does not display any messages for Google-Buzz
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gwibber |
Invalid
|
Medium
|
Unassigned | ||
gwibber (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gwibber
Although the correct settings for my Google Buzz account, Gwibber does not display any messages.

Victor Vargas (kamus) wrote : | #1 |
Changed in gwibber (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Incomplete |

Michał Mrówczyński (ups5) wrote : | #2 |
This is the result of this command:
<code>Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Refresh interval is set to 15
Gwibber Dispatcher: DEBUG Refresh interval is set to 15
Gwibber Dispatcher: DEBUG ** Starting Refresh - 2010-09-06 17:36:00.30 **
Gwibber Dispatcher: DEBUG <facebook:receive> Performing operation
Gwibber Dispatcher: DEBUG <facebook:
Gwibber Dispatcher: DEBUG <STATS> facebook:receive account:
Gwibber Dispatcher: INFO Facebook error 4 - Application request limit reached
Gwibber Dispatcher: DEBUG <facebook:receive> Finished operation
Gwibber Dispatcher: DEBUG <facebook:lists> Performing operation
Gwibber Dispatcher: DEBUG <STATS> facebook:responses account:
Gwibber Dispatcher: INFO Facebook error 4 - Application request limit reached
Gwibber Dispatcher: DEBUG <facebook:
Gwibber Dispatcher: DEBUG <buzz:receive> Performing operation
Traceback (most recent call last):
File "/usr/lib/
self.
error: (56, 'GnuTLS recv error (-9): A TLS packet with unexpected length was received.')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
Gwibber Dispatcher: ERROR <buzz:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if parse: return [getattr(self, "_%s" % parse)(m) for m in data["data"
KeyError: 'data'
Gwibber Dispatcher: INFO Facebook error 4 - Application request limit reached
Gwibber Dispatcher: DEBUG <facebook:lists> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - []
^CTraceback (most recent call last):
File "/usr/bin/
loop.run()
KeyboardInterrupt
Gwibber Dispatcher: DEBUG Unlocking password cache!</code>

Victor Vargas (kamus) wrote : | #3 |
According to curl doc that error is caused by a network error while received data. is this behaviour still occurring with facebook or other accounts?

Shark Tek (marbin1) wrote : | #4 |
I'm having the same issue with Gwibber 2.31.93
Here is my output:
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Refresh interval is set to 15
Gwibber Dispatcher: DEBUG ** Starting Refresh - 2010-09-11 14:59:39.01 **
Gwibber Dispatcher: DEBUG <buzz:receive> Performing operation
Gwibber Dispatcher: ERROR <buzz:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if parse: return [getattr(self, "_%s" % parse)(m) for m in data["data"
KeyError: 'data'

shoo_ash (ash-mail) wrote : | #5 |
Got the same problem.
Shows no buzz messages for quite a long time. Updates change nothing (updating in maverick).
Gwibber Dispatcher: DEBUG <buzz:receive> Performing operation
Traceback (most recent call last):
File "/usr/lib/
self.
error: (56, 'GnuTLS recv error (-9): A TLS packet with unexpected length was received.')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
Gwibber Dispatcher: ERROR <buzz:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if parse: return [getattr(self, "_%s" % parse)(m) for m in data["data"
KeyError: 'data'

shoo_ash (ash-mail) wrote : | #6 |
I suppose, it might be some bug in getting the right authentication link from google. By the way, when you enter your credentials, google says it doesn't trust gwibber - and asks to press additionaly a confirmation button - may be here comes the problem with the link, as it catches some wrong address?

Victor Vargas (kamus) wrote : | #7 |
I have enabled my Buzz account for testing and I am able to confirm this behaviour too.
Changed in gwibber (Ubuntu): | |
status: | Incomplete → Confirmed |

Vitali Kulikou (sabotatore) wrote : | #8 |
I have the same problem:
$ gwibber-service -d -o
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - 2010-10-02 11:11:02.82 **
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:lists> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <buzz:receive> Performing operation
Traceback (most recent call last):
File "/usr/lib/
self.
error: (56, 'GnuTLS recv error (-9): A TLS packet with unexpected length was received.')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
Gwibber Dispatcher: ERROR <buzz:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/lib/
return getattr(self, opname)(**args)
File "/usr/lib/
return self._get(
File "/usr/lib/
if parse: return [getattr(self, "_%s" % parse)(m) for m in data["data"
KeyError: 'data'
Gwibber Dispatcher: DEBUG <twitter:lists> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - []
$ apt-cache policy gwibber
gwibber:
Installed: 2.32.0-0ubuntu1
Candidate: 2.32.0-0ubuntu1
Version table:
*** 2.32.0-0ubuntu1 0
500 http://
100 /var/lib/
$ apt-cache policy gwibber-service
gwibber-service:
Installed: 2.32.0-0ubuntu1
Candidate: 2.32.0-0ubuntu1
Version table:
*** 2.32.0-0ubuntu1 0
500 http://
100 /var/lib/

പ്രിന്സ് പോള് (prince-paul) wrote : | #9 |
Me too have the same problem:
$ 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-10-06 20:58:22.07 **
Gwibber Dispatcher: DEBUG <facebook:receive> Performing operation
Gwibber Dispatcher: DEBUG <facebook:
Gwibber Dispatcher: DEBUG <STATS> facebook:receive account:
Gwibber Dispatcher: DEBUG <facebook:receive> Adding record
Gwibber Dispatcher: DEBUG <facebook:receive> Adding record
Gwibber Dispatcher: DEBUG <facebook:receive> Adding record
Gwibber Dispatcher: DEBUG <facebook:receive> Adding record
Gwibber Dispatcher: DEBUG <facebook:receive> Finished operation
Gwibber Dispatcher: DEBUG <facebook:lists> Performing operation
Gwibber Dispatcher: DEBUG <facebook:lists> Adding record
Gwibber Dispatcher: DEBUG <facebook:lists> Adding record
Gwibber Dispatcher: DEBUG <facebook:lists> Adding record
Gwibber Dispatcher: DEBUG <facebook:lists> Adding record
Gwibber Dispatcher: DEBUG <facebook:lists> Adding record
Gwibber Dispatcher: DEBUG <facebook:lists> Adding record
Gwibber Dispatcher: DEBUG <facebook:lists> Adding record
Gwibber Dispatcher: DEBUG <facebook:lists> Adding record
Gwibber Dispatcher: DEBUG <facebook:lists> Adding record
Gwibber Dispatcher: DEBUG <facebook:lists> Finished operation
Gwibber Dispatcher: DEBUG <twitter:receive> Performing operation
Gwibber Dispatcher: DEBUG <STATS> facebook:responses account:
Gwibber Dispatcher: DEBUG <facebook:
Gwibber Dispatcher: DEBUG <facebook:
Gwibber Dispatcher: DEBUG <facebook:
Gwibber Dispatcher: DEBUG <facebook:
Gwibber Dispatcher: DEBUG <twitter:responses> Performing operation
Gwibber Dispatcher: DEBUG <twitter:receive> Finished operation
Gwibber Dispatcher: DEBUG <twitter:private> Performing operation
Gwibber Dispatcher: DEBUG <twitter:responses> Finished operation
Gwibber Dispatcher: DEBUG <twitter:lists> Performing operation
Gwibber Dispatcher: DEBUG <twitter:private> Finished operation
Gwibber Dispatcher: DEBUG <buzz:receive> Performing operation
Traceback (most recent call last):
File "/usr/lib/
self.
error: (56, 'GnuTLS recv error (-9): A TLS packet with unexpected length was received.')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
Gwibber Dispatcher: ERROR <buzz:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
Changed in gwibber (Ubuntu): | |
importance: | Low → Medium |

Gabriel Samfira (gabriel-samfira) wrote : | #10 |
Looks like its a combination of 2 problems.
The first problem is that gwibber doesn't use the correct Authentication URL with google. I think it uses:
when it should be using:
The second problem is in:
/usr/lib/
at line 63:
m["text"] = data["object"
I changed this line in:
try:
m["text"] = data["object"
except:
m["text"] = "None"
After authorizing gwibber using:
and changing that line (i KNOW there is a better way to change that line) my buzz feeds apeared in gwibber.
Here is the output of gwibber-service -d -o after the above mentioned modiffications:
$ 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-10-08 14:57:07.48 **
Gwibber Dispatcher: DEBUG <buzz:receive> Performing operation
Traceback (most recent call last):
File "/usr/lib/
self.
error: (56, 'GnuTLS recv error (-9): A TLS packet with unexpected length was received.')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispat...

Gabriel Samfira (gabriel-samfira) wrote : | #11 |
One last thing. I used the readonly scope in the authorisation request. Posting a new buzz might not work :).

Sebas (comandantecobra) wrote : | #12 |
I'm also affected. I've the last version of Gwibber downloaded
I can't see nothing from my Buzz, and when I try to post something I get:
Gwibber Dispatcher: DEBUG *** Sending Message ***
Gwibber Dispatcher: DEBUG <buzz:send> Performing operation
Traceback (most recent call last):
File "/usr/lib/
self.
error: (56, 'GnuTLS recv error (-9): A TLS packet with unexpected length was received.')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
Gwibber Dispatcher: ERROR <buzz:send> Operation failed

Gabriel Samfira (gabriel-samfira) wrote : | #13 |
Hi Sebas,
Try copy and pasting this link into your browser:
After that, copy and paste this command into a terminal:
sudo sed -i -e '63 s/.*/ try:\n m["text"] = data["object"
And see if that helps.

Sebas (comandantecobra) wrote : | #14 |
Thanks Gabriel.
It worked only with the link :).
Both: publishing and previewing the Buzz content. I did not modified the /usr/lib/

Arthur Alikulov (hd-smasher) wrote : | #15 |
As I see, solution of problem is quite simple. Is anyone going to fix it and push it to repo?

Gabriel Samfira (gabriel-samfira) wrote : | #16 |
- adds another callback to authorize the oauth_token for google buzz Edit (974 bytes, text/plain)
I created 2 patches that solved this bug on my system. The coding is not pretty...but it seamed to work. Hope this helps someone.

Gabriel Samfira (gabriel-samfira) wrote : | #17 |
- fixes KeyError on some buzzez that do not have "content", just "title" (private buzz i think) Edit (603 bytes, text/plain)
tags: | added: patch |

Gabriel Samfira (gabriel-samfira) wrote : | #18 |
- gwibber.tar.gz Edit (969 bytes, application/x-tar)
Made a few corrections to the patch to handle failure of token authorisation. Also made a mistake in the try...except statement (mea culpa).

Victor Vargas (kamus) wrote : | #19 |
Ken, can you take a look into this patch please! Thanks.
Changed in gwibber (Ubuntu): | |
status: | Confirmed → Triaged |

Simon (simschi) wrote : | #20 |
Patch from #18 worked for me!
Thank you very much!

Gabriel Samfira (gabriel-samfira) wrote : | #21 |
- Fixes IndexError when importing Twitter feeds with no href tag Edit (796 bytes, text/plain)
Found another small bug that does not treat an IndexError.
Google buzz can aggregate feeds from popular sites like twitter. Most times the feeds look like:
<a href="http://
But in rare cases the feed looks like this:
TwitterUSERID: Message from Twitter here
Unfortunately when an exception is thrown no feeds are imported. The modified patch should take care of that to.

Jack Deslippe (jdeslip) wrote : | #22 |
Is this patch being incorporated into the ubuntu packages?

Abner (pauloabner) wrote : | #23 |
I applied this patch and the buzz window is showing the messages now

Mynk (mr-mynk) wrote : | #24 |
Is this fix in the official release? Kindly let know when we can see the same in the official repositories.

Omer Akram (om26er) wrote : | #25 |
Gabriel Samfira, a real patch is usually one file for a single fix i see three different patches. could you make a single .patch for all the changes.

Gabriel Samfira (gabriel-samfira) wrote : | #26 |
- gwibber.patch Edit (2.2 KiB, text/plain)
Sorry about that. Its my first patch :). I created a single file containing all changes to both /usr/lib/
cd /usr/lib/
should work on a default instalation. After applying, adding a new account, viewing current buzzes and posting new ones should work.

Omer Akram (om26er) wrote : | #27 |
i have build gwibber with this patch in my ppa https:/
Traceback (most recent call last):
File "/usr/lib/
self.
error: (56, 'GnuTLS recv error (-9): A TLS packet with unexpected length was received.')
Gwibber Dispatcher: ERROR Failed to communicate with https:/
Changed in gwibber: | |
importance: | Undecided → Medium |
status: | New → Confirmed |

Gabriel Samfira (gabriel-samfira) wrote : | #28 |
The only way i managed to get rid of that error, was by recompiling libcurl with OpenSSL instead of GnuTLS and then recompiling python-pycurl against the new cURL library.
as an ugly hack i did:
apt-get source curl
then modified line 80 of debian/rules to compile using openSSL:
cd debian/build-gnutls && ./configure ${CONFIGURE_ARGS} --with-
After rebuilding, i installed the debs generated by dpkg-buildpackage and rebuild python-pycurl:
apt-get source python-pycurl
cd pycurl-7.19.0 && dpkg-buildpackage && dpkg -i ../python-
I must mention that i can see some avatars but not others. Don't know if its related.
This is the output after rebuilding curl and python-pycurl:
$ gwibber-service -o -d
Gwibber Dispatcher: DEBUG Setting up monitors
Gwibber Dispatcher: DEBUG Refresh interval is set to 5
Gwibber Dispatcher: DEBUG ** Starting Refresh - 2010-12-06 16:15:05.36 **
Gwibber Dispatcher: DEBUG <buzz:receive> Performing operation
Gwibber Dispatcher: DEBUG libproxy: getting proxies
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Adding record
Gwibber Dispatcher: DEBUG <buzz:receive> Finished operation
Gwibber Dispatcher: INFO Loading complete: 1 - []
Gwibber Dispatcher: DEBUG Raising gwibber client
Gwibber Dispatcher: DEBUG Gwibber Client raised

Gabriel Samfira (gabriel-samfira) wrote : | #29 |
- gwibber.patch Edit (2.5 KiB, text/plain)
About the avatar. It looks like the json received from google, in some cases does not include the thumbnailUrl (avatar) in the "actor" block:
"actor": {
"id": "10173573489042
"name": "Gabriel-Adrian Samfira"
}
The _actor method looks for the thumbnailUrl key, and defaults to:
https:/
if it doesn't exist. Unfortunately it exists, but its and empty string. I added a condition that deletes the key in case its an empty string, so it can default to blue_ghost.

Gabriel Samfira (gabriel-samfira) wrote : | #30 |
Looks like its a google account feature not to share your photo with everyone. You can change that behavior by following the instructions here:
http://
(step 7)
The "GnuTLS recv error" seems to be of little consequence in regards to the avatar being shown. Don't know if it affects any functionality.

Yaron (sh-yaron) wrote : | #31 |
I can't send as well.

Didier Roche-Tolomelli (didrocks) wrote : | #32 |
Ken, can you have a look at the patches and see if they make sense?

Didier Roche-Tolomelli (didrocks) wrote : | #33 |
(subscribe only because the assign don't want to find you doh!)

Ken VanDine (ken-vandine) wrote : | #34 |
Thanks for the patch!
I've ported the patch in comment #29 to trunk and push my bzr branch to lp:~ken-vandine/gwibber/lp_626023
I am still getting errors and can't get messages, but I have never actually gotten Buzz to work with gwibber from my gmail account. Can someone look at the branch and verify it works for them and perhaps help figure out why it isn't working for me? Here are the errors I am getting:
Gwibber Dispatcher: DEBUG <buzz:receive> Performing operation
Gwibber Dispatcher: ERROR <buzz:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
File "/home/
message_data = PROTOCOLS[
File "/home/
return getattr(self, opname)(**args)
File "/home/
return self._get(
File "/home/
request.
File "/usr/lib/
self.
File "/usr/lib/
return signature_
File "/usr/lib/
digest = self._build_
File "/usr/lib/
hashed = hmac.new(key, raw, sha)
File "/usr/lib/
return HMAC(key, msg, digestmod)
File "/usr/lib/
self.
TypeError: character mapping must return integer, None or unicode

Gabriel Samfira (gabriel-samfira) wrote : | #35 |
- encode access_token and secret_token to ascii text Edit (573 bytes, text/plain)
Hello Ken!
From what i understand from this post:
the problem is in the input given to the hmac library:
key.translate(
It seams like gwibber stores its account information in unicode format and the hmac library does not accept unicode characters. A quick and dirty fix to the error you posted should be encoding the unicode strings into ASCII text. I have attached a bzr diff to your branch that does this.
There is no doubt a better solution to this error (maybe storing account information as ascii instead of unicode?).

Ken VanDine (ken-vandine) wrote : | #36 |
@gabriel-samfira: Thanks for the patch, I've applied it in both trunk and our 3.0 branches. We still haven't gotten a fix for this error though:
error: (56, 'GnuTLS recv error (-9): A TLS packet with unexpected length was received.')
I suspect it doesn't happen for everyone, it probably depends which server you are trying to reach. Anyone have suggestions that don't include rebuilding libcurl and python-curl?
Changed in gwibber: | |
assignee: | nobody → Ken VanDine (ken-vandine) |

Gabriel Samfira (gabriel-samfira) wrote : | #37 |
I have stumbled across this thread:
http://
In one post it is sugested that the error may be produced by the remote server not sending a notify before ending the tls connection. The following quote may be of interest:
Nikos said, "Several sites terminate the TLS connection without following the TLS protocol (i.e. sending closure alerts), but rather terminate the TCP connection directly. This is a relic of SSLv2 and it seems other implementations ignore this error. GnuTLS doesn't and thus prints this error. You could ignore it, but then you could not distinguish between a premature connection termination (i.e. by someone injecting a stray TCP termination packet) and normal termination."
Like i staded in an earlier post, the gnutls error itself does not seem to affectany functionality.
Gabriel

Guruprasad (lgp171188) wrote : | #38 |
I am facing this issue in Ubuntu 11.04, Gwibber 3.0.0.8
Here is the trackback:
<snip>
Identi.ca : DEBUG <buzz:receive> Performing operation
DEBUG:Identi.
Identi.ca : ERROR <buzz:receive> Operation failed
ERROR:Identi.
Identi.ca : DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/share/
return getattr(self, opname)(**args)
File "/usr/share/
return self._get(
File "/usr/share/
request.
File "/usr/lib/
self.
File "/usr/lib/
return signature_
File "/usr/lib/
digest = self._build_
File "/usr/lib/
hashed = hmac.new(key, raw, sha)
File "/usr/lib/
return HMAC(key, msg, digestmod)
File "/usr/lib/
self.
TypeError: character mapping must return integer, None or unicode
</snip>

maksymov.vlad (maksymov.vlad) wrote : | #39 |
gwibber-service -d -o
Loading plugin Twitter version 1.0
Loading plugin Buzz version 1.0
Loading plugin Facebook version 1.1
Facebook : DEBUG Setting up monitors
Facebook : DEBUG Refresh interval is set to 15
Facebook : DEBUG ** Starting Refresh - 2011-04-29 22:17:05.32 **
Facebook : DEBUG <twitter:private> Performing operation
Facebook : DEBUG <twitter:receive> Performing operation
Facebook : DEBUG <twitter:receive> Finished operation
Facebook : DEBUG <twitter:responses> Performing operation
Facebook : DEBUG <twitter:private> Finished operation
Facebook : DEBUG <twitter:lists> Performing operation
Facebook : DEBUG <twitter:responses> Finished operation
Facebook : DEBUG <twitter:receive> Performing operation
Facebook : DEBUG <twitter:receive> Finished operation
Facebook : DEBUG <twitter:responses> Performing operation
Facebook : DEBUG <twitter:lists> Finished operation
Facebook : DEBUG <twitter:private> Performing operation
Facebook : DEBUG <twitter:responses> Finished operation
Facebook : DEBUG <buzz:receive> Performing operation
Facebook : ERROR <buzz:receive> Operation failed
Facebook : DEBUG Traceback:
Traceback (most recent call last):
File "/usr/lib/
message_data = PROTOCOLS[
File "/usr/share/
return getattr(self, opname)(**args)
File "/usr/share/
return self._get(
File "/usr/share/
request.
File "/usr/lib/
self.
File "/usr/lib/
return signature_
File "/usr/lib/
digest = self._build_
File "/usr/lib/
hashed = hmac.new(key, raw, sha)
File "/usr/lib/
return HMAC(key, msg, digestmod)
File "/usr/lib/
self.
TypeError: character mapping must return integer, None or unicode
Facebook : DEBUG <twitter:private> Finished operation
Facebook : DEBUG <twitter:lists> Performing operation
Facebook : DEBUG <twitter:lists> Finished operation
Facebook : DEBUG Private Messages Indicator count updated to 0
Facebook : DEBUG Replies Indicator count updated to 0
Facebook : DEBUG Messages Indicator count updated to 0
Facebook : INFO Loading complete: 1 - []
Facebook : INFO Cleaning up database...
Facebook : INFO Found 234 records in the messages st...

Guruprasad (lgp171188) wrote : | #40 |
buzz plugin seems to be buggy with more exceptions coming up when I try to use the convert to ascii fix.

maksymov.vlad (maksymov.vlad) wrote : | #41 |
I have the same problem on 11.04 with gwibber 3.1.0. I have download gwibber-

Gabriel Samfira (gabriel-samfira) wrote : | #42 |
The encode to ascii fix was a poor one, but i ment it as an example as to where to start. It will fail if access_token or secret_token will contain a character with no equivalent in ascii:
u'ă'.encode(
You could try to encode to UTF-8 instead of ascii, but i can't guarantee it will work. It gives no errors on my system, but neither did the ascii encoding, so i cant promise it will work. The author of the gwibber plugin may be able to find a more portable and less error prone fix.
Changed in gwibber: | |
assignee: | Ken VanDine (ken-vandine) → nobody |

Aemnas (rustyhaner) wrote : | #43 |
Buzz is being discontinued - http://

Bilal Shahid (s9iper1) wrote : | #44 |
"Thanks for your patch, unfortunately our busy developers haven't been
able to review your patch in a timely manor. The gwibber codebase has
seen significant change and it is likely this patch no longer applies.
Please review it again and if it is still applicable, update it to work
with the latest gwibber trunk. We will be doing a patch review day in
the next few weeks and would like to review your patch. Thanks again for
your contribution!"
tags: | added: patch-day-old |
Changed in gwibber: | |
status: | Confirmed → Incomplete |
Changed in gwibber (Ubuntu): | |
status: | Triaged → Incomplete |

Craig Maloney (craig-decafbad) wrote : | #45 |
Buzz is discontinued. This can be closed.
Changed in gwibber: | |
status: | Incomplete → Invalid |
Changed in gwibber (Ubuntu): | |
status: | Incomplete → Invalid |
Please could you run under latest version of gwibber: gwibber-service -d -o and attach all resulted output to a textfile (following your steps to reproduce this issue), Thanks!