Bug 137501

Summary: artifacts when printing text with colors
Product: [Fedora] Fedora Reporter: Ulrich Drepper <drepper>
Component: vteAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 0.12.1-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-05-27 17:27:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
just after starting vi
none
After going to the end of the line
none
after going one line down none

Description Ulrich Drepper 2004-10-28 21:33:55 UTC
Description of problem:
I have seen this only with vim but it can hardly be a problem in vim since there
is no way to produce the output which I see.  I will attach three PNGs to show
the problem.  This is on x86 but it should not matter.

Version-Release number of selected component (if applicable):
gnome-terminal-2.7.3-1

How reproducible:
always

Steps to Reproduce:
1.don't use system font in g-t, use Monospace 9.  might be the case for others,
too, but I use this
2.run vi /boot/grub/grub.conf
3.
  
Actual results:
as seen in the attached pictures

Expected results:
clean output, no double prints

Additional info:

Comment 1 Ulrich Drepper 2004-10-28 21:35:59 UTC
Created attachment 105920 [details]
just after starting vi

This is how portions of the screen look like right after starting vi.  Look at
the end of the lines.

Comment 2 Ulrich Drepper 2004-10-28 21:37:30 UTC
Created attachment 105921 [details]
After going to the end of the line

Now the cursor is at the end of the line.  The '0' now becomes readable.

Comment 3 Ulrich Drepper 2004-10-28 21:39:24 UTC
Created attachment 105922 [details]
after going one line down

Proceeding to the next line (same column), the '5' becomes now readable, the
'0' is back to its sorry state.

Comment 4 Ulrich Drepper 2006-05-27 17:27:15 UTC
I haven't seen this is quite some time.  I'll just close it with reference to
the FC5 version.