Hi x2go users,
After recent update to x2goclient 4.0.5.0-2.fc22 I'm unable to connect to my x2go server.
Error message: Connection failed. setterm: $TERM is not defined.
Steps to reproduce:
- Upgrade x2goclient to 4.0.5.0-2.fc22
- Just try to connect to x2go server
When I downgrade back to 4.0.3.2-1.fc22 everything is fine. Any ideas? I thought about opening a defect, but maybe it's something wrong with the setup of my server?
- The client machine's OS: Fedora 22 x86_64
- The client machine's version of X2GoClient: 4.0.5.0-2.fc22
- The server's OS: Arch Linux
- The server's version of the x2goserver package: 4.0.1.19-2
- The server's version of the x2goserver-xsession package: No such package installed or found in repos
- The server's version of the nxagent package: 3.5.0.32-1
- The server's version of any other relevant packages: None
- Any relevant settings in X2GoServer: None
Long log from x2goclient --debug can be found here: http://pastie.org/10425302
Best regards
Maciej Sitarz
I found what caused the problem.
$ ssh MY_IP 'bash -l -c "echo TERM=$TERM"' setterm: $TERM is not defined. BASH_PROFILE BASHRC TERM=dumb
setterm was only used in /etc/profile.d/disable-beep.sh: $ cat /etc/profile.d/disable-beep.sh setterm -blength 0
I removed that and it now works.
Best regards
Maciej Sitarz
In your .profile:
export TERM="vt102" or whatever terminal definition you prefer touse, "ansi", etc.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Thu, 17 Sep 2015, Maciej Sitarz wrote:
Date: Thu, 17 Sep 2015 10:02:55 +0200 From: Maciej Sitarz <macieksitarz@wp.pl> To: x2go-user@lists.x2go.org Subject: [X2Go-User] x2goclient connection fails with 'setterm: $TERM is not defined'
Hi x2go users,
After recent update to x2goclient 4.0.5.0-2.fc22 I'm unable to connect to my x2go server.
Error message: Connection failed. setterm: $TERM is not defined.
Steps to reproduce:
- Upgrade x2goclient to 4.0.5.0-2.fc22
- Just try to connect to x2go server
When I downgrade back to 4.0.3.2-1.fc22 everything is fine. Any ideas? I thought about opening a defect, but maybe it's something wrong with the setup of my server?
- The client machine's OS: Fedora 22 x86_64
- The client machine's version of X2GoClient: 4.0.5.0-2.fc22
- The server's OS: Arch Linux
- The server's version of the x2goserver package: 4.0.1.19-2
- The server's version of the x2goserver-xsession package: No such package installed or found in repos
- The server's version of the nxagent package: 3.5.0.32-1
- The server's version of any other relevant packages: None
- Any relevant settings in X2GoServer: None
Long log from x2goclient --debug can be found here: http://pastie.org/10425302
Best regards
Maciej Sitarz
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
W dniu 17.09.2015 o 11:06, Robert Dinse pisze:
In your .profile: export TERM="vt102" or whatever terminal definition you prefer touse, "ansi", etc.
The problem was that the /etc/profile.d configs are loaded before ~/.bashrc and ~/.bash_profile.
According to man bash ~/.profile is loaded after them: " When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior."
So adding TERM setting to /etc/profile should also help.
Thank you
-- Maciej Sitarz
The .bashrc shouldn't unset TERM but it is probably a better place toput it since non-login terminals will pick up the variable there as well in case it isn't exported from the parent process.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Thu, 17 Sep 2015, Maciej Sitarz wrote:
Date: Thu, 17 Sep 2015 11:14:22 +0200 From: Maciej Sitarz <macieksitarz@wp.pl> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] x2goclient connection fails with 'setterm: $TERM is not defined'
W dniu 17.09.2015 o 11:06, Robert Dinse pisze:
In your .profile: export TERM="vt102" or whatever terminal definition you prefer touse, "ansi", etc.
The problem was that the /etc/profile.d configs are loaded before ~/.bashrc and ~/.bash_profile.
According to man bash ~/.profile is loaded after them: " When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior."
So adding TERM setting to /etc/profile should also help.
Thank you
-- Maciej Sitarz
-
Maciej Sitarz -
Robert Dinse