Bug 228653 - xterm crashes when outputing weird characters
xterm crashes when outputing weird characters
Product: Fedora
Classification: Fedora
Component: xterm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Miroslav Lichvar
Depends On:
  Show dependency treegraph
Reported: 2007-02-14 01:35 EST by Rene Cunningham
Modified: 2008-08-02 19:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 15:13:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rene Cunningham 2007-02-14 01:35:49 EST
Description of problem:

Xterm closes when outputing weird characters such as ones generated from

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

How reproducible:

Steps to Reproduce:
1. cat /dev/random
Actual results:
xterm crashes. Running xterm from another xterm in the foreground produces the
following when it crashes.

xterm:  warning, error event received:
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  77 (X_ImageText16)
  Serial number of failed request:  299
  Current serial number in output stream:  761

Expected results:

Random characters

Additional info:

Also happens when viewing certain pages in lynx, when viewing ALL manpages, and
using mutt in screen.
Comment 1 Miroslav Lichvar 2007-02-14 04:09:43 EST
Unfortunately, I can't reproduce it.

Is this on a xinerama setup? Any resource settings for xterm? Which video driver
is used?
Comment 2 Thomas E. Dickey 2007-02-24 19:54:19 EST
It would help to have a non-random set of data which breaks it,
since the cause would be some specific code sequence.
Comment 3 Miroslav Lichvar 2007-04-16 09:24:11 EDT
Can you please try xterm-225-1.fc6 from FC6 updates testing repository?
Comment 4 Bug Zapper 2008-04-04 02:13:55 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 5 Bug Zapper 2008-05-06 15:13:31 EDT
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

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.