[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2011-06-04 Thread Launchpad Bug Tracker
[Expired for gwibber (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gwibber (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/605543

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2011-04-05 Thread Ken VanDine
I am reasonably sure this was fixed. Please re-open if you experience it again. ** Changed in: gwibber Status: Confirmed = Fix Released ** Changed in: gwibber Assignee: Gwibber Team (gwibber-team) = (unassigned) ** Changed in: gwibber Status: Fix Released = Incomplete --

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2011-02-25 Thread Kamus
Captain, any news about this issue? are you still facing this behaviour? ** Changed in: gwibber (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/605543

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2011-02-25 Thread Foppe Hemminga
I looked at this topic a couple of weeks ago,I haven't noticed it for some time, but I had a gap not using Gwibber for a longer period (temporary switch to KDE.) The issue looks related to some older version of Gwibber. Also at the time of this bug I did ran development versions, so that may be

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2011-02-25 Thread Captain Chaos
I haven't been seeing the behaviour since august last year, but that is because I fixed it by making the change in comment #15. I'll remove my fix to see whether the bug still occurs. One reason I might have been seeing this problem and others didn't is my locale setting. It's a bit different

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-09 Thread Captain Chaos
@Foppe That solution doesn't work for me. First it failed because the HTMLParser constructor doesn't take arguments, so it should be p = HTMLParser.HTMLParser(). But when I changed it to that I got the following error message: Gwibber Dispatcher: ERRORtwitter:receive Operation failed Gwibber

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-08 Thread Captain Chaos
I tried Foppe's suggestion, but now I get this error: Gwibber Dispatcher: ERRORtwitter:receive Operation failed Gwibber Dispatcher: DEBUGChecking message 20614540018 timestamp (2010-08-08 10:16:04.00) to see if it is newer than 2010-08-08 13:11:59.38 Gwibber Dispatcher: DEBUG

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-08 Thread Foppe Hemminga
Thanks Captain Chaos, I don't have time to look into this right now. So a couple of questions and remarks. What languages are the tweets you receive? You can print the raw data with the print statement: print data[text] or print s in function unescape (s) and view the twitter stream in

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-08 Thread Captain Chaos
The tweets are mainly in Dutch, English and Japanese. You say that before the data is parsed by htmllib.HTMLParser it must be unicode, but your modification actually turns the string into a UTF-8-encoded 8-bit string, not unicode. What's more, a print type(s) in unescape() reveals that *without*

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-08 Thread Maykel Moya
@Captain Chaos After applying Foppe's patch I got the same error you reported in #21. In #23 you said 'My fix remedies this', what fix are you referring to? -- UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data https://bugs.launchpad.net/bugs/605543

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-08 Thread Captain Chaos
@Maykel The one from comment #15. -- UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data https://bugs.launchpad.net/bugs/605543 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-08 Thread Foppe Hemminga
@Captain Chaos: Thanks for your research. I think you are correct on most issues. The most intriguing question remains: why doesn't everyone have this problem? I came up with a new solution that works with my English / Dutch tweets. 1) Change line 1 to import network, util, HTMLParser 2)

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-07 Thread Captain Chaos
I tried it, but as I already feared it lead to: Gwibber Dispatcher: DEBUGTraceback: Traceback (most recent call last): File /usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py, line 75, in perform_operation message_data =

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-07 Thread Foppe Hemminga
The 'latin1' part in my proposed code (/usr/lib/python2.6/dist- packages/gwibber/microblog/twitter.py line 64) should be 'utf8' m[text] = unescape(data[text].encode(utf8)) The rationale is as follows: htmllib.HTMLParser from function unescape in

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-07 Thread Omer Akram
Captain Chaos, can you try Foppe's suggestion to see if that works. it would be better to get it fixed on gwibber's side ;) -- UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data https://bugs.launchpad.net/bugs/605543 You received this bug notification

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-07 Thread Ryan Paul
** Changed in: gwibber Milestone: None = 3.0 -- UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data https://bugs.launchpad.net/bugs/605543 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-07 Thread Benjamin-Timm Broich
The solution from Foppe Hemminga worked fine for me! -- UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data https://bugs.launchpad.net/bugs/605543 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-06 Thread Foppe Hemminga
Hi Capt Chaos, Your idea is fine but you are editing python files where you should edit gwibber files ;) in /usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py change line 64 m[text] = unescape(data[text]) to m[text] = unescape(data[text].encode(latin1)) --

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-04 Thread Captain Chaos
Aha, a clue! The error message is 'utf8' codec can't decode byte 0xeb, and the message contained a ë. Byte 0xeb in the *ISO-8859-1* character encoding is ë! This means that it is very likely that the message is not encoded with UTF-8 at all, but with ISO-8859-1, and Gwibber for some reason tries

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-04 Thread Captain Chaos
The plot thickens. I've been looking at the code, and this happens while decoding an HTML entity tag (such as aacute;). Apparently the problem is not that the contents of the tweet are being decoded with the wrong character encoding, but that the tweet contains entity tags, and Python's htmllib is

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-04 Thread Benjamin-Timm Broich
Maybe this helps. I get a similiar error: Traceback (most recent call last): File /usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py, line 71, in perform_operation message_data = PROTOCOLS[account[service]].Client(account)(opname, **args) File

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-04 Thread Omer Akram
would any gwibber developer have a look at this please. ** Changed in: gwibber Assignee: (unassigned) = Gwibber Team (gwibber-team) ** Changed in: gwibber Status: New = Confirmed -- UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-04 Thread Captain Chaos
Victory! I managed to get Twitter working in Gwibber by changing the line 436 in /usr/lib/python2.6/sgmllib.py from: self.handle_data(replacement) to: self.handle_data(unicode(replacement,'latin-1')) I also deleted /usr/lib/python2.6/sgmllib.pyc. This is my first time

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-08-03 Thread Foppe Hemminga
# NOS Teletekst Teletekst Israëliër in VN-panel aanval Gaza http://nos.nl/l/175947/t 4:36 PM Aug 2nd via API This is the first post _not_ being shown in GWibber. The 'ë' might be a coincidence though. UnicodeDecodeError: 'utf8' codec can't decode byte 0xeb in position 0: unexpected end of

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-07-28 Thread Captain Chaos
Twitter started working in Gwibber a few days ago, but now it has stopped again. I noticed that one of the tweets currently on my twitter.com page has the word Catalonië in it. Could it be that Gwibber can't handle accented characters? And that it only works whenever your Twitter feed happens to

Re: [Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-07-28 Thread Omer Akram
no 'Catalonië' just went fine for me On Wed, Jul 28, 2010 at 4:01 PM, Captain Chaos 605...@bugs.launchpad.netwrote: Twitter started working in Gwibber a few days ago, but now it has stopped again. I noticed that one of the tweets currently on my twitter.com page has the word Catalonië in

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-07-16 Thread Captain Chaos
Anything happening on this? It's very frustrating. I went from Karmic, where Twitter worked but Facebook didn't, to Lucid, and now Facebook works but Twitter doesn't! It's amazing that a program which is a centrepiece of the Ubuntu GUI can be so buggy for so long... Please let me know if I can

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-07-15 Thread Omer Akram
** Also affects: gwibber Importance: Undecided Status: New ** Changed in: gwibber (Ubuntu) Importance: Undecided = Medium ** Changed in: gwibber (Ubuntu) Status: New = Confirmed -- UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of

[Bug 605543] Re: UnicodeDecodeError: 'utf8' codec can't decode byte 0xe1 in position 0: unexpected end of data

2010-07-15 Thread Vitali Kulikou
This bug affects me: $ gwibber-service -d -o Updating... Gwibber Dispatcher: DEBUG Setting up monitors Gwibber Dispatcher: DEBUG Monitors are up Gwibber Dispatcher: INFO Gwibber Service is reloading account credentials Gwibber Dispatcher: DEBUG Refresh interval is set to 5 Gwibber Dispatcher: