Bug 184596
| Summary: | artifacts when running with TERM=xterm and ispell | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | ritz <rkhadgar> | ||||||||
| Component: | vte | Assignee: | Behdad Esfahbod <behdad> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | |||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 4.0 | CC: | jdreese, linux_support, marcobillpeter, rstrode | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | RHBA-2007-0219 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2007-05-01 17:15:14 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: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 176344 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
ritz
2006-03-10 04:11:17 UTC
Detailed notes have already been entered into Red Hat Technical Support service request #829264. Is it necessary to reproduce them here? Shouldn't you be setting TERM=xterm and not TERM=XTERM? The notes entered by rkhadgar are inaccurate; we were experiencing this bug with TERM=xterm, which is the default setting of TERM in a gnome-terminal under RHELv4. I have logged extensive notes on Red Hat Technical Support service request #829264. Is it necessary to reproduce them here? I have made a note of TERM=xterm, and informed engineering regarding the same. Unfortunately, my reply is private. Is there a way I can see the details? Created attachment 134490 [details]
spellcheck.txt file attached
test file
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request. Could someone please indicate why this request was declined? This issue is a significant inconvenience to our users who spell check files in gnome-terminal. I'm looking into it. Created attachment 135875 [details]
fix
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. (In reply to comment #37) > ahy updates w.r.t. a patch ? I've already attached a patch. Waiting for QA to confirm that this fixes the bug. > This event sent from IssueTracker by rkhadgar > issue 90232 If this is the patch attached to this bugzilla, it still borks out. I tested again with vte-0.11.11-8.el4, and it behaves just like xterm does. Previously it used to leave artifacts instead of scrolling text up. Please attach a screenshot of the broken rendering in vte-0.11.11-8.el4, and the correct rendering of the same situation in xterm. (In reply to comment #46) > Here's what I saw. > > > This event sent from IssueTracker by alanm > issue 90232 > > it_file 80490 If I understand this correctly, this is only the xterm shot. PLEASE give me all the information I asked for in comment #45, so I can figure out what's going on. Created attachment 146231 [details]
gnome-terminal screenshot.
and the warnings written to the terminal when you launch gnome-terminal from inside another terminal? This bug is not fixed yet. Created attachment 148416 [details]
vte bug's screenshot along with xterm
this screenshot demonstrates vte's bug.
additionally, gnome-terminal does not print any message when run from xterm.
Should be really fixed this time, in vte-0.11.11-10.el4. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0219.html |