Bug 813868

Summary: <backspace> echoes as "0008 in a box"
Product: [Fedora] Fedora Reporter: John Reiser <jreiser>
Component: gnome-terminalAssignee: Matthias Clasen <mclasen>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: gustavold, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: powerpc   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-26 11:32:02 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
syslog (/var/log/messages)
$HOME/.xsession-errors none

Description John Reiser 2012-04-18 11:54:11 EDT
Created attachment 578402 [details]

Description of problem: In gnome-terminal (bash command line), a <backspace> echoes as "0008 in a box" instead of visually erasing the previous character.  Typing "date\b\r" gives "dat: not found", so the 'e' was removed from the string that was delivered to the shell; but the display shows five characters: "date" followed by "0008 in a box".  This happens running gnome-terminal under both Gnome3 session (fallback mode) and Xfce session.  The Xfce Terminal app behaves correctly (<backspace> visually erases the previous character) under both Gnome3 session and Xfce session.

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

How reproducible: every time

Steps to Reproduce:
1. type "date\b\r" as the first input to a gnome-terminal.
Actual results: Displays as "date" followed by "0008 in a box".  bash complains "dat: not found."

Expected results: Displays as "dat" (without the 'e' and without the "0008 in a box"), followed by bash complaint "dat: not found".

Additional info: Font is monospace 9.  Box is Apple Macintosh Mini G4 PowerPC, which is big-endian.

 lspci says:
0000:00:10.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200] (rev 01)
0000:00:10.0 0300: 1002:5962 (rev 01)
Comment 1 John Reiser 2012-04-18 11:55:52 EDT
Created attachment 578403 [details]
syslog (/var/log/messages)
Comment 2 John Reiser 2012-04-18 12:42:04 EDT
Created attachment 578407 [details]
Comment 3 John Reiser 2012-04-18 12:45:47 EDT
Comment 4 Matthias Clasen 2012-05-08 09:12:38 EDT
I have had no luck reproducing this. Useful pieces of information would include:

your locale settings: env | grep LANG\\\|LC

gnome-terminals charset encoding: gconftool-2 --get /apps/gnome-terminal/global/active_encodings

the font: gconftool-2 --get /apps/gnome-terminal/profiles/Default/font
Comment 5 John Reiser 2012-05-08 11:05:01 EDT
$ env | grep LANG\\\|LC
$ gconftool-2 --get
No value set for `/apps/gnome-terminal/global/active_encodings'
$ gconftool-2 --get /apps/gnome-terminal/profiles/Default/font
Monospace 12

Note again that this is PowerPC (Apple Macintosh Mini "G4"), which is big-endian.
Comment 6 Matthias Clasen 2012-05-15 16:15:41 EDT
It sounds plausible that an endianness bug might be responsible, but I don't really have any good idea where to look for it...
Comment 7 Gustavo Luiz Duarte 2012-06-26 09:46:31 EDT
This issue is caused by a broken glib2. It is fixed on the latest glib2 available from updates (glib2-2.32.3-1.fc17).
For the record, the glib2 bug is caused by endian issue on GResource API. Upstream bugz: https://bugzilla.gnome.org/show_bug.cgi?id=673409

Please update to glib2-2.32.3-1.fc17 to verify the fix.
Comment 8 Matthias Clasen 2012-06-26 11:03:21 EDT
ah, thanks for tracking that down
Comment 9 John Reiser 2012-06-26 11:32:02 EDT
Confirmed fixed in glib2-2.32.3-1.fc17.ppc (self-built from .src.rpm).