Bug 478512 - sending non-UTF-8 encoding named file failed - Bonjour
sending non-UTF-8 encoding named file failed - Bonjour
Product: Fedora
Classification: Fedora
Component: pidgin (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Warren Togami
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-31 01:22 EST by ken cao
Modified: 2010-06-28 07:03 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 07:03:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
sending non-UTF-8 encoding named file, crash report (14.06 KB, text/plain)
2008-12-31 01:22 EST, ken cao
no flags Details

  None (edit)
Description ken cao 2008-12-31 01:22:17 EST
Created attachment 327993 [details]
sending non-UTF-8 encoding named file, crash report

Description of problem:
when using Boujour,
sending non-UTF-8 encoding named file may crash pidgin.
details are noted in the 'Actual results' section.

Version-Release number of selected component (if applicable):

How reproducible:
100% reproducible in my testing environment.

Steps to Reproduce:
1. login a Bonjour account
2. right click a name in the buddy list of the Bonjour account
3. select 'send file, and browse to choose a file whose name 
is non-UTF-8 encoded.
4. the expected receiver chooses to accept the file.

Actual results:
if the two users are on the some machine, root and an ordinary user,
the expected receiver will crash.
if the two users are on different machine, the operation just fail, 
no pidgin crash.

Expected results:
file being successfully transferred, or at least, pidgin shall not 

Additional info:
the attachment is the bug-report.
Comment 1 ken cao 2008-12-31 01:40:20 EST
it seems that pidgin 2.5.2-f10 works fine with pidgin 2.5.3-f11 using Bonjour
Comment 2 Warren Togami 2009-03-24 11:21:24 EDT
Can you still reproduce this?  Your crash dump is not useful because you are lacking debugging symbols.

Please read this.
Comment 3 Bug Zapper 2009-06-09 06:33:17 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 4 Bug Zapper 2010-04-27 08:39:45 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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: 
Comment 5 Bug Zapper 2010-06-28 07:03:07 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.

Note You need to log in before you can comment on or make changes to this bug.