Bug 1369777 - gnome-terminal freezes whole gnome session while sending special characters to stdout
Summary: gnome-terminal freezes whole gnome session while sending special characters t...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: 25
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-24 11:44 UTC by Ingvar Hagelund
Modified: 2017-12-12 10:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:24:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ingvar Hagelund 2016-08-24 11:44:36 UTC
Description of problem:
Sending special characters to stdout in gnome-terminal makes whole gnome session freeze

Version-Release number of selected component (if applicable):
gnome-session-3.20.2-1.fc24.x86_64

How reproducible:
Always

Steps to Reproduce:

1. Generate for instance 2,000,000 characters of type 0707, and send them to stdout. This may be done like this:

$ cat <<EOF > gen_char.c

#include <stdio.h>
int main() {
  for ( int i=0; i<2000000; i++ ) {
    printf("%c", 0x707);
  }
  return 0;
}

EOF

$ cc -o gen_char gen_char.c

$ ./gen_char | hexdump
0000000 0707 0707 0707 0707 0707 0707 0707 0707
*
01e8480

2. Run the program in gnome-terminal under a normal gnome3 session

$ ./gen_char

3. Watch the gnome session freeze for something like 10-30s, depending on the speed of your computer

Actual results:
gnome3 session freezes while sending special characters to stdout in gnome-terminal

Expected results:
Normal behaviour. Compare with doing the same in xterm

Additional info:
The system as such is not affected. It is only the gnome session that freezes temporarily.

Comment 1 Fedora End Of Life 2017-07-25 22:37:15 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora  'version'
of '24'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.

Comment 2 Ingvar Hagelund 2017-07-26 08:02:57 UTC
Reproduced in fedora 25, gnome-terminal-3.22.1-5.fc25.x86_64 and gnome-session-3.22.3-1.fc25.x86_64.

Ingvar

Comment 3 Ingvar Hagelund 2017-07-26 08:08:31 UTC
I might add that there exist more or less broken tools out there that produces these kind of special characters, making a session freeze, like (non-free) server raid tools. This is how I discovered this (though I can't remember which tool it was).

Ingvar

Comment 4 Ingvar Hagelund 2017-07-26 08:47:30 UTC
If anyone is interested, I found the actual tool that trigged this. It was hpasmcli in older versions. Trigged like this:

# echo -e "show fans\nexit\n" | hpasmcli

Older versions (like hp-health-10.00-1688.34) would produce streams of character 0x707, practically hanging gnome-session. This is fixed in later versions (at least hp-health-10.60-1833.33, and perhaps earlier).

While this trigger is fixed, the general problem still exists. A stream of special characters, like 0x707, sent to gnome-terminal, will make gnome-session freeze.

Ingvar

Comment 5 Fedora End Of Life 2017-11-16 18:59:01 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora  'version'
of '25'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.

Comment 6 Egmont Koblinger 2017-11-25 09:50:57 UTC
Filed VTE feature request for rate limiting: https://bugzilla.gnome.org/show_bug.cgi?id=790815.

Comment 7 Ingvar Hagelund 2017-12-08 09:57:59 UTC
I think this actually is a variant of bz #1466654. I am not longer able to reproduce this on fedora 26.

Ingvar

Comment 8 Fedora End Of Life 2017-12-12 10:24:36 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.