Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDennis Schridde
2012-03-15 18:32:42 UTC
Description of problem:
It appears to me that bug #639280 against Fedora 14 appears also
in Scientific Linux 6.2: E.g. in Guake $TERM is "dumb" instead of "xterm".
Version-Release number of selected component (if applicable):
vte-0.25.1-7.el6.x86_64
How reproducible:
Type "echo $TERM" in Guake installed in SL 6.2.
Actual results:
Output is "dumb"
Expected results:
Output should be "xterm"
I initially mentioned this on the scientific-linux-users mailinglist and two others tried and could not reproduce.
Vladimir Mosgalin wrote:
---
I, too, have no problems - I'm using vte-based roxterm. Always had
"xterm" TERM in SL 6.1 and 6.2.
I checked other vte-based terminal emulator that I used in the past,
sakura; it works just fine out of the box, too.
There are tons of vte-based terminals out there, and from that bug it's
hard to say how many people are affected: the problem, if present, seems
to be confirmed for just a few of them. So maybe most of people never
notice if this bug is present at all.
---
(In reply to comment #3)
> Isn't this a duplicate of #754557 ?
Yes.
Bugzilla seems broken to me - I cannot mark this bug as a dupe and neither can I close it... Can someone else please do that?
(In reply to comment #5)
> below "additional comments", you should haev a 'Mark as Duplicate" link.
Yes. Clicking it removes the link and adds a "#" in the URL field, but nothing else happens. Also notable is that the "Status: ..." line below the comment field and left to "Save Changes" shows "NEW" just as a text (i.e. no drop down field) and selecting any resolution from the drop down field next to the status just does nothing. I assume something broke the JavaScript fancyness.