Bug 760421

Summary: [abrt] telepathy-butterfly-0.5.15-3.fc16: text.py:169:_signal_text_received:UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 0: ordinal not in range(128)
Product: [Fedora] Fedora Reporter: Yang Chi <yangchi.cn>
Component: telepathy-butterflyAssignee: Brian Pepple <bdpepple>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: bdpepple, sander
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:c957bbb8caec02ef107228656896815533071852
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 09:21:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: smolt_data
none
File: backtrace none

Description Yang Chi 2011-12-06 06:26:34 UTC 
libreport version: 2.0.7
abrt_version:   2.0.6
cmdline:        /usr/bin/python /usr/libexec/telepathy-butterfly
event_log:      2011-12-06-01:23:42> Smolt profile successfully saved
executable:     /usr/libexec/telepathy-butterfly
kernel:         3.1.2-1.fc16.i686
reason:         text.py:169:_signal_text_received:UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 0: ordinal not in range(128)
time:           Tue 06 Dec 2011 01:01:30 AM EST
uid:            1000
username:       yang

backtrace:      Text file, 2089 bytes
smolt_data:     Text file, 3299 bytes

comment:
:Empathy got connected won both MSN and Gmail.
:Then wireless network lost connection.
:After connected back to the network, this shows up. And I can send messages on MSN, but can't receive anything from the friend I chatted to.
Comment 1 Yang Chi 2011-12-06 06:26:36 UTC 
Created attachment 541223 [details]
File: smolt_data
Comment 2 Yang Chi 2011-12-06 06:26:38 UTC 
Created attachment 541224 [details]
File: backtrace
Comment 3 Fedora End Of Life 2013-01-16 10:35:03 UTC 
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 4 Fedora End Of Life 2013-02-13 09:21:51 UTC 
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.