Bug 525722

Summary: minicom crash
Product: [Fedora] Fedora Reporter: Sergei LITVINENKO <sergei.litvinenko>
Component: minicomAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jgorig, mlichvar, stsp2
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-09 13:16:47 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
strace log where minicom is crashed none

Description Sergei LITVINENKO 2009-09-25 12:09:03 UTC
Created attachment 362664 [details]
strace log where minicom is crashed

Description of problem:
If system locale is ru_RU.UTF-8, as soon as minicom try to init modem it crash
with message in backtrace *** buffer overflow detected ***:


Version-Release number of selected component (if applicable):
minicom-2.3-6.fc12.i686

How reproducible:
100%

Steps to Reproduce:
1. Use locale ru_RU.UTF-8
1. Connect mobile phone by USB
2. Setup minicom to use /dev/ttyACM0: minicom -s (serial port setup)
3. Save setting as dfl
4. Run minicom
  
Actual results:
Minicom crash with backtrace log

Expected results:
Minicom work

Additional info:
1. `export LC_ALL=C ; export LANG=C; minicom` help.
2. If I understand good, some russian messages to overflow buffer

Comment 1 Bug Zapper 2009-11-16 12:56:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Stas Sergeev 2010-01-14 09:59:16 UTC
Please try the fix in Bug 555283.

Comment 3 Jan Görig 2010-03-09 13:16:47 UTC

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