Bug 608162

Summary: [abrt] crash in telepathy-butterfly-0.5.11-1.fc13: text.py:170:_signal_text_received:UnicodeDecodeError: 'ascii' codec can't decode byte 0xd9 in position 0: ordinal not in range(128)
Product: [Fedora] Fedora Reporter: islam fouda <islamfouda>
Component: telepathy-butterflyAssignee: Brian Pepple <bdpepple>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: akneto, andre_makishi, asterix314, bdpepple, benjavalero, claudiorodrigo, donkishoot, engine.games, engle_mars, jackonweb, luigi.cardeles, m_pupil, roumano, sander, tvilarim, volans2000, xoxxyy, yyetim, zaterio
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:45c042b9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-24 19:44:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description islam fouda 2010-06-25 20:43:44 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/libexec/telepathy-butterfly
component: telepathy-butterfly
executable: /usr/libexec/telepathy-butterfly
kernel: 2.6.33.5-124.fc13.i686.PAE
package: telepathy-butterfly-0.5.11-1.fc13
reason: text.py:170:_signal_text_received:UnicodeDecodeError: 'ascii' codec can't decode byte 0xd9 in position 0: ordinal not in range(128)
release: Fedora release 13 (Goddard)
Comment 1 islam fouda 2010-06-25 20:43:52 UTC 
Created attachment 426986 [details]
File: backtrace
Comment 2 Robert Zhang 2010-06-28 02:08:19 UTC 
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.open empathy
2.empathy reports a few messages that were sent to me while i was offline.
3.a few seconds later crash!
Comment 3 Volans 2010-07-04 20:12:44 UTC 
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Crash occured when I signed in and got an offline message from MSN.
2.
3.
Comment 4 zaterio 2010-07-05 00:34:57 UTC 
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Just Open Empathy (MSN)
2.
3.
Comment 5 Roumano 2010-07-05 10:46:56 UTC 
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. do nothing
2.
3.
Comment 6 yyetim 2010-07-05 19:23:44 UTC 
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Created MSN account
2. Receveived an offline message
3.
Comment 7 jackonweb 2010-07-09 01:38:32 UTC 
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.ABRT pop-up after a new message received
2.
3.
Comment 8 akneto 2010-07-11 14:14:40 UTC 
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Just tried to connect to MSN network with empathy!
2.
3.
Comment 9 Kai.Fan 2010-07-20 16:02:07 UTC 
Package: telepathy-butterfly-0.5.11-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. startup empathy
2. got an offline message
3.
Comment 10 Benjamín Valero Espinosa 2010-07-24 18:52:40 UTC 
Looking the backtrace, it seems that the problem happens when the text of the message has non-Latin characters.

I have found an upstream bug with a similar problem (in the same block of code)

https://bugs.freedesktop.org/show_bug.cgi?id=28747

where I give a possible fix.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 11 Brian Pepple 2010-07-24 19:44:05 UTC 

*** This bug has been marked as a duplicate of bug 606615 ***