Bug 77765 - invalid characters breaks a terminal until reset terminal.
invalid characters breaks a terminal until reset terminal.
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux Beta
Classification: Retired
Component: vte (Show other bugs)
beta1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-11-13 02:42 EST by Akira TAGOH
Modified: 2007-04-18 12:48 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-13 04:41:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Akira TAGOH 2002-11-13 02:42:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
Generally EUC-JP doesn't allow Latin1. but such characters often appears onto
the terminal. when it appears unfortunately, terminal window is broken, and it
can't be shown correctly without reset the terminal.

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


How reproducible:
Always

Steps to Reproduce:
1.runs gnome-terminal with LANG=ja_JP.eucJP
2.look at Latin1 characters with something like the pager.
3.
	

Actual Results:  terminal window is broken.

Expected Results:  should ignore such characters as well as previous gnome-terminal.


Additional info:
Comment 1 Nalin Dahyabhai 2003-01-13 23:16:12 EST
By "ignore", do you mean not to acknowledge that the application sent
unrecognizable text to the terminal?  I wouldn't think that behavior was desirable.
Comment 2 Akira TAGOH 2003-01-14 01:56:41 EST
I have no idea to handle those characters with EUC-JP. do you think this problem
can be fixed like box drawing issue? if possible, it would be great.
Comment 3 Akira TAGOH 2003-08-13 04:41:25 EDT
It looks good in the current release. I couldn't reproduce it now.

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