xfce x-terminal emulator: TERM environment variable not set

[DrJohn]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In a fresh install of Mythbuntu 10.10, running Accessories, Terminal
(xfce x-terminal emulator):

Code:

> echo $TERM
dumb
>

This results in apps that need to know what's available (top for
example) reporting "TERM environment variable not set" and halting.

Code:

> export TERM=xterm

fixes this temporarily. This was seen earlier for Terminator, bug
#621606, and fixed, but apparently not here.

Checked in Mythbuntu 10.04: $TERM is set to 'xterm'

 affects mythbuntu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMsnesAAoJEFJ3a0HNXtk26bMIAIiCvFK+/eU3jQDOiKO3bHUI
/q7p5mYRTFrlLDAD21gHMZzzZCxMev7H6dpnp9VYDRj12WNAGbOozq5ITwp699Nx
K/ZoZQmx3gsCymEt/7NnnacgUxyDUAGW/Nh+VN5QG1SQl/jBhFFe35zPsUCmTvyn
o0mH9D3hkkKkVrvpJzjcb/zSbQUQPxE9xoHS+LjhRysizh/UhbA8tBozYlCPKqMT
ds3epH7I1dx6H4RXYtiPXe1m2lsFHfZNqG2rBUDl/opuZd9ay66/EkPT3bCVKM9/
gpDBlZmeXD18rExg3Ayp7vtvGKerhjhVd6uMno7pnfeQufT4qlGPLnp+lYPMadM=
=AYru
-----END PGP SIGNATURE-----

[Mario Limonciello (superm1)]

Thanks for reporting this bug as well as linking that bug that it was seen in with Terminator. Their solution required code changes directly to Terminator's code for libvte changes, so I suspect something similar will be required for xfce4-terminal to be fixed.

I'm going to add a bug task for the source package xfce4-terminal so it can get fixed there.

[Mario Limonciello (superm1)]

After investigating a little bit more, it appears that there is actually a proposed fix already in maverick-proposed for an SRU candidate. I'll mark this bug as a duplicate so you can track it's progress.

[Micah Gersten (micahg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 621927, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.