Bug 754557

Summary: vte not setting TERM variable for terminal emulators other than gnome-terminal
Product: Red Hat Enterprise Linux 6 Reporter: Aron Parsons <parsonsa>
Component: vteAssignee: Debarshi Ray <debarshir>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1CC: aronparsons, behdad, dennis, heri, kevin, lud.janvier, nathan, pingou, rvcsaba, simon, tlavigne, tomspur, walters
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: AcceptedNTH
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 639280 Environment:
Last Closed: 2017-12-06 12:30:36 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
vte-fix-from-upstream none

Description Aron Parsons 2011-11-16 20:27:57 UTC
+++ This bug was initially created as a clone of Bug #639280 +++

vte-0.25.1-6.el6 is encountering this same issue where the TERM variable is not being set by terminal emulators using vte.

The bug was fixed upstream in 0.26.

References:
https://bugzilla.gnome.org/show_bug.cgi?id=631589
https://bugzilla.redhat.com/show_bug.cgi?id=639280

Comment 2 Adam Williamson 2011-11-16 20:50:50 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 RHEL Program Management 2011-11-16 20:58:46 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 4 Aron Parsons 2011-11-16 21:42:11 UTC
Created attachment 534101 [details]
vte-fix-from-upstream

Upstream commits:
0574bcfbd5c5925458ecdea0e6bbac6d65e30efc
e5fd6c3cda63cad2e3d7af8728a168b90eb009dc 

The attached patch includes these and applies cleanly against vte-0.25.1-6.el6.

Comment 5 Tomáš Bžatek 2012-06-04 12:29:29 UTC
*** Bug 803845 has been marked as a duplicate of this bug. ***

Comment 7 RHEL Program Management 2012-07-10 07:59:56 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 8 RHEL Program Management 2012-07-11 02:03:32 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 9 RHEL Program Management 2012-09-07 05:27:36 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 11 Jan Kurik 2017-12-06 12:30:36 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/