Red Hat Bugzilla – Bug 214713
strange characters on configure console when autogen.sh is run
Last modified: 2009-06-11 18:51:53 EDT
Description of problem:
Strange characters appear on configure console with the output of autogen.sh.
See the attached screenshot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Check out a GNOME project.
2. Make the configure command run 'autogen.sh' instead of 'configure'
3. Notice the strange characters on the console.
Created attachment 140725 [details]
strange characters printed with output of autogen.sh
Jeff, can you duplicate this?
Yes. The gnome-autogen.sh file uses terminal boldface and terminal normal
control sequences calculated by tput. The upstream Eclipse console doesn't know
how to translate these sequences so they appear as garbage. IMO, the
gnome-autogen.sh shouldn't be doing this, but the fact is, they do.
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
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
Jeff: I've seen an upstream bug about the console not accepting control
characters. You should find it and reference it here and then close this as
upstream. Looking for "\b" at bugs.eclipse.org/bugs should help, I think.
changing version to 'rawhide' to keep this bug from EOL closure
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
This should perhaps be marked a duplicate of the upstream "console can't deal with control characters" bug. Jeff?
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. 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 WONTFIX if it remains open with a Fedora
'version' of '9'.
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 prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Jeff, please mark this as a duplicate of the upstream "console can't deal with control characters" bug or do some other triage.
Closing this as upstream bug.