It isn't just non-critical, the output isn't just lost, it explodes the]x2go session.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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 Wed, 26 Jul 2017, Marat Khalili wrote:
Date: Wed, 26 Jul 2017 16:09:55 +0300 From: Marat Khalili <mkh@rqc.ru> To: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Compatibility between x2go deb packaged versions
If someone can explain a bit more I would appreciate. It's a common problem not limited to x2go. Anything in /etc/profile and similar places (/etc/profile.d, /etc/bashrc, ~/.bashrc etc.) should make sure the session is interactive before outputting anything non-critical to stdout or stderr.
--
With Best Regards, Marat Khalili
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user