TERM is not set in guake since I upgraded to Maverick

Bug #644476 reported by Alejandro Díaz-Caro on 2010-09-21
This bug affects 6 people
Affects Status Importance Assigned to Milestone
guake (Ubuntu)

Bug Description

Binary package hint: guake

A command is worth a thousand words:

janus@katu ~ $ clear
TERM environment variable not set.
janus@katu ~ $ echo $TERM

It happens only in guake, I tryied xterm and gnome-terminal and both sets the TERM variable to xterm, so "clear" works.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: guake 0.4.2-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CheckboxSubmission: dde7aa8fd900cd9d547f3e5c1a1a7547
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Tue Sep 21 17:52:07 2010
ExecutablePath: /usr/lib/guake/guake.py
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
SourcePackage: guake

Alejandro Díaz-Caro (janus) wrote :
Firas Kraïem (firas) wrote :

Already reported upstream.


Phil Bayfield (philio) wrote :

This is a new bug introduced in the last couple of days, my guake was working fine yesterday but is broken after updating this morning.

Adam (adam-jackman) wrote :

Guake seems to need TERM set in the .bash_profile.

cat .bash_profile and see if it exists, a clean install doesn't have one

$ cat .bash_profile
cat: .bash_profile: No such file or directory

If the result is as above run the following

echo -e "TERM=linux\nexport TERM" > .bash_profile

This will create the .bash_profile with the correct settings, then either log out and in again or run the following to kill and re-load guake:

pkill -f "/usr/lib/guake/guake.py"

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.