After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 675174 - Gnome-Terminal does not properly handle random data printed to terminal screen
Gnome-Terminal does not properly handle random data printed to terminal screen
Status: RESOLVED DUPLICATE of bug 593424
Product: gnome-terminal
Classification: Core
Component: general
2.31.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-04-30 17:58 UTC by jef
Modified: 2012-04-30 20:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Red Hat terminal error screen shots (196.22 KB, application/x-gzip)
2012-04-30 17:58 UTC, jef
Details

Description jef 2012-04-30 17:58:07 UTC
Created attachment 213126 [details]
Red Hat terminal error screen shots

On Red Hat 6.2, using the Gnome-Terminal 2.31.3, one can create an error in the way the terminal processes processes text. Do the following:

CLOSE all open Gnome-Terminals
Start a Gnome-Terminal GUI
In the terminal, run "dd if=/dev/urandom bs=1M count=1"
Sometime during the char dump a "Font" dialog box(s) will pop-up.
If you do not get an error close all Gnome-Terminals and try again.


I can repeat and get an error(s) every time. I did a dump of a 1M dd dump and determined that this char string "75DCB4" is A trigger.

Attached are screen shots.

jef
Comment 1 Christian Persch 2012-04-30 18:33:08 UTC
(In reply to comment #0)
> In the terminal, run "dd if=/dev/urandom bs=1M count=1"
> Sometime during the char dump a "Font" dialog box(s) will pop-up.
> If you do not get an error close all Gnome-Terminals and try again.

That's not exactly an 'error', it's just telling you it needs more fonts to display the character. Bug 593424 is about disabling this feature for the terminal.
Comment 2 jef 2012-04-30 19:49:40 UTC
Hello,

Really, if this is a feature then why does the KDE terminal not exhibit this same behavior. 

You should run the dd command with 100M and see how many fonts it wants to load. Or, take the three char error string I provided and trigger an error. Now select install the font in the font dialog box. See what happens?

IS THIS ALL NORMAL.

Please feel free to handle this error as you see fit. I will play with it a while to see if I can do some "damage". 

Thanks,

jef
Comment 3 André Klapper 2012-04-30 20:25:38 UTC
2.31.x is an unstable ancient development version. Feel free to file a bug report in the bugtracker of your distribution if they really support this version. Upstream GNOME does not anymore.
Comment 4 Christian Persch 2012-04-30 20:31:15 UTC
gnome-packagekit font install integration hasn't improved since, so this is still valid, and a dup of bug 593424 .

*** This bug has been marked as a duplicate of bug 593424 ***
Comment 5 jef 2012-04-30 20:47:48 UTC
Here is the strace output with 1M dd dev/urandom bs=1M count=1:
----------

[root@localhost ~]# strace -o terminal-trace.txt gnome-terminal
(gnome-terminal:2900): PkGtkModule-DEBUG: InstallFontconfigResources method invoked                                                                             

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\u0012'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'z'.
(gnome-terminal:2900): PkGtkModule-DEBUG: InstallFontconfigResources method invoked                                                                             
(gnome-terminal:2900): PkGtkModule-DEBUG: InstallFontconfigResources method invoked                                                                             

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'h'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'I'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xf9'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\x84'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xce'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map ':'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xad'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '^'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'n'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\u0012'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\u001f'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\x9b'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'S'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xf6'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'v'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\u000d'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'N'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\u0008'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'g'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xfa'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xf8'.
(gnome-terminal:2900): PkGtkModule-DEBUG: InstallFontconfigResources method invoked                                                                             

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\u001c'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xa4'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'P'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '%'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'h'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xf1'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\x86'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xef'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xe0'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\u0007'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xab'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xc5'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xbd'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\u000c'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\u001f'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\x8e'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xf8'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xe7'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'W'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xf1'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map 'a'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\x96'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map ' '.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '%'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xfd'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\x8a'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xef'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xae'.

(gnome-terminal:2900): Vte-WARNING **: Attempt to set invalid NRC map '\xcf'.

--------------
Comment 6 jef 2012-04-30 20:50:27 UTC
I wonder why this bug still exists for 3+ years. Red hat still uses this in the default gnome package. It seems that they ARE waiting for you to fix the issue. I am not an Apple or Microsoft fan; but, they are ONE entity to be in charge of fixes, when needed.

Thanks

jef