[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
*** This bug is a duplicate of bug 621927 *** https://bugs.launchpad.net/bugs/621927 Since my own scripts worked in Lucid and this error also occours on my fresh server, I don't think that they are the root of the problem. But here are the rc files from my laptop at first. I can post those from my server too, if you'd like. -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
*** This bug is a duplicate of bug 621927 *** https://bugs.launchpad.net/bugs/621927 ** Attachment added: skel.bashrc https://bugs.edge.launchpad.net/ubuntu/+source/xterm/+bug/652160/+attachment/1677740/+files/skel.bashrc -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
*** This bug is a duplicate of bug 621927 *** https://bugs.launchpad.net/bugs/621927 ** Attachment added: bash.bashrc https://bugs.edge.launchpad.net/ubuntu/+source/xterm/+bug/652160/+attachment/1677742/+files/bash.bashrc -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
*** This bug is a duplicate of bug 621927 *** https://bugs.launchpad.net/bugs/621927 ** This bug has been marked a duplicate of bug 621927 Embedded Terminal Emulator isn't giving a TERM variable * You can subscribe to bug 621927 by following this link: https://bugs.launchpad.net/ubuntu/+source/guake/+bug/621927/+subscribe -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
I will check those files in /etc. But this bug showed up after upgrading to Maverick via a fresh install on my laptop - but kept the home dir. And on my server there was a complete fresh install with no prior home. -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
On Mon, 4 Oct 2010, Daniel Holm wrote: I will check those files in /etc. But this bug showed up after upgrading to Maverick via a fresh install on my laptop - but kept the home dir. And on my server there was a complete fresh install with no prior home. This appears to be a bug in vte which affects all of its users except for gnome-terminal. https://bugzilla.redhat.com/show_bug.cgi?id=639280 (it only surfaced in one of my queries today) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
** Bug watch added: Red Hat Bugzilla #639280 https://bugzilla.redhat.com/show_bug.cgi?id=639280 -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
Yes. It is bash. What do you want me to do? -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
yOn Fri, 1 Oct 2010, Daniel Holm wrote: Yes. It is bash. What do you want me to do? I'm curious if there's something in its initialization scripts which is doing an unset on TERM, or exporting it to some odd value. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
echo $TERM shows 'null'. Where can I find these init scripts? -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
On Fri, 1 Oct 2010, Daniel Holm wrote: echo $TERM shows 'null'. Where can I find these init scripts? As a start, I'd look at the rc files that dpkg -L bash lists, e.g., /etc/skel/.bashrc /etc/bash.bashrc and also your own scripts. You might also get a list of files using strace, e.g., strace -fo foo, and looking for open-calls. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
** Attachment added: .proc.driver.nvidia.cards.0.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658086/+files/.proc.driver.nvidia.cards.0.txt ** Attachment added: .proc.driver.nvidia.registry.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658087/+files/.proc.driver.nvidia.registry.txt ** Attachment added: BootDmesg.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658088/+files/BootDmesg.txt ** Attachment added: CurrentDmesg.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658089/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658090/+files/Dependencies.txt ** Attachment added: Lspci.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658091/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658092/+files/Lsusb.txt ** Attachment added: PciDisplay.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658093/+files/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658094/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658095/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658096/+files/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658097/+files/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658098/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658099/+files/UdevLog.txt ** Attachment added: XorgConf.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658100/+files/XorgConf.txt ** Attachment added: XorgLog.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658101/+files/XorgLog.txt ** Attachment added: XorgLogOld.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658102/+files/XorgLogOld.txt ** Attachment added: Xrandr.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658103/+files/Xrandr.txt ** Attachment added: glxinfo.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658104/+files/glxinfo.txt ** Attachment added: nvidia-settings.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658105/+files/nvidia-settings.txt ** Attachment added: peripherals.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658106/+files/peripherals.txt ** Attachment added: setxkbmap.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658107/+files/setxkbmap.txt ** Attachment added: xdpyinfo.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658108/+files/xdpyinfo.txt ** Attachment added: xkbcomp.txt https://bugs.edge.launchpad.net/bugs/652160/+attachment/1658109/+files/xkbcomp.txt -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
It's more likely to be a problem with your shell environment than xterm. -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
Yeah, probably. But I didn't know what else? -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 652160] Re: TERM environment variable not set.
I don't see the shell mentioned (assuming bash). It's not a problem with the terminal database, otherwise you'd not succeed in using the exported $TERM. So I'm assuming some scripting error in the shell's initialization is clearing the variable. -- TERM environment variable not set. https://bugs.launchpad.net/bugs/652160 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
