From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040608
Description of problem:
I noticed this (presumably quite rare and subtle) bug when doing
in the terminal emulator "screen", running in gnome-terminal.
Basically sometimes when you output a particular character sequence
gnome-terminal spuriously adds an indent. I have verified that it's
not a screen bug by stracing screen using
strace -s 65536 -o screen.strace -e trace=write -p $PID_OF_ACTIVE_SCREEN
and the output is identical when the bug occurs and when the bug does
not occur (remember, it's pretty random). So it can't possibly be a
Note that this seems to be a timing-influenced bug (thread bug
perhaps?) so it might not occur on a faster machine. My machine is an
Athlon XP 1800. (Indeed the only reason why screen triggers this might
be that screen slows the catting down a little.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Download attached test file
2. Start gnome-terminal
3. Start screen
4. Type "cat bug"
5. As the bug is intermittent, you may need to try again a few times
before you see it.
Actual Results: The xinetd line is indented, like this:
Expected Results: ├─sshd(2154)
(At first I thought that someone had hacked my box and was (bizarrely)
using my machine as an xinetd server. Look at the bogus output above -
you can see why I was worried!)
Created attachment 101034 [details]
Oops, looks like bugzilla has foobared my actual and expected results.
I'll attach a screenshot. The first cat (partially offscreen) is
buggy, the second cat has worked.
Created attachment 101035 [details]
screenshot of bug occurring
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.
This bug is being closed because it has been in the NEEDINFO state for a long
time now. Feel free to reopen the bug report if the problem still happens for
you and you can provide any information that was requested.