Package: x2goclient Version: 4.0.0.3
If I put an echo "testing" # exact text doesn't matter
at the top of my .bashrc, then the x2goclient crashes immediately when trying to start a session.
(The crash does not occur if I put a similar statement in .bash_login.)
I have reproduced this on the Windows client; I believe a colleague saw it on both the Windows and Linux clients.
The x2go server being used is 4.0.1.6-0~712~precise1.
tag #327 confirmed thanks
Hi Dan,
On Sa 19 Okt 2013 18:22:43 CEST, Dan Halbert wrote:
If I put an echo "testing" # exact text doesn't matter
I presume, this on the server.
at the top of my .bashrc, then the x2goclient crashes immediately
when trying to start a session.(The crash does not occur if I put a similar statement in .bash_login.)
I have reproduced this on the Windows client; I believe a colleague
saw it on both the Windows and Linux clients.The x2go server being used is 4.0.1.6-0~712~precise1.
I can confirm that the issue exists with latest X2Go Client.
I could confirm this issue on Debian wheezy or Ubuntu precise as X2Go
Server. On Ubuntu lucid, the problem does not occur.
Mike
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Processing commands for control@bugs.x2go.org:
tag #327 confirmed Bug #327 [x2goclient] x2go client crashes if .bashrc prints anything Added tag(s) confirmed. thanks Stopping processing here.
Please contact me if you need assistance.
327: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=327 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems
If I put an
echo "testing" # exact text doesn't matter
I presume, this on the server. Right, this is on the server. With the Windows client there is no .bashrc anyway. I confirmed with my colleague that he saw this on both
On 10/29/2013 4:36 AM, Mike Gabriel wrote: the Windows and Ubuntu Precise clients.
Which windowing system chosen on the server does not seem to matter either. I saw it with UNITY and with just "Terminal".
I could confirm this issue on Debian wheezy or Ubuntu precise as X2Go Server. On Ubuntu lucid, the problem does not occur. That's interesting. The reason for putting in the echo's was to debug a completely unrelated problem about which shell init got run when we were running some batch jobs. I had instrumented the init files before without difficulty. Thanks for looking at this.
clone #327 -1 tag #327 wontfix retitle -1 users can inject data into X2Go Client using .bashrc severity -1 grave
Hi Dan,
On Di 29 Okt 2013 12:55:05 CET, Dan Halbert wrote:
On 10/29/2013 4:36 AM, Mike Gabriel wrote:
If I put an
echo "testing" # exact text doesn't matter
I presume, this on the server. Right, this is on the server. With the Windows client there is no
.bashrc anyway. I confirmed with my colleague that he saw this on
both the Windows and Ubuntu Precise clients.Which windowing system chosen on the server does not seem to matter
either. I saw it with UNITY and with just "Terminal".I could confirm this issue on Debian wheezy or Ubuntu precise as
X2Go Server. On Ubuntu lucid, the problem does not occur. That's interesting. The reason for putting in the echo's was to
debug a completely unrelated problem about which shell init got run
when we were running some batch jobs. I had instrumented the init
files before without difficulty. Thanks for looking at this.
I have looked at this in depth this morning. Indeed an echoing .bashrc
file breaks X2Go. But it also breaks everything else around SSH, esp.
scp [1, 2].
The first link [1] also provides a solution that I want to quote here:
""" (file: ~/.bashrc) [... normal .bashrc stuff ...]
if [[ $- =~ "i" ]]; then echo "SPEAK OUT LOUD!!!" fi """
The i-flag in $- checks if the shell is interactive or not. With X2Go,
this flag will not get set.
Greets, Mike
[1]
http://stackoverflow.com/questions/12440287/scp-doesnt-work-when-echo-in-bas...
[2] https://bugzilla.redhat.com/show_bug.cgi?id=20527
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
Processing commands for control@bugs.x2go.org:
clone #327 -1 Bug #327 [x2goclient] x2go client crashes if .bashrc prints anything Bug 327 cloned as bug 333 tag #327 wontfix Bug #327 [x2goclient] x2go client crashes if .bashrc prints anything Added tag(s) wontfix. retitle -1 users can inject data into X2Go Client using .bashrc Bug #333 [x2goclient] x2go client crashes if .bashrc prints anything Changed Bug title to 'users can inject data into X2Go Client using .bashrc' from 'x2go client crashes if .bashrc prints anything' severity -1 grave Bug #333 [x2goclient] users can inject data into X2Go Client using .bashrc Severity set to 'grave' from 'normal' Hi Dan, Unknown command or malformed arguments to command. On Di 29 Okt 2013 12:55:05 CET, Dan Halbert wrote: Unknown command or malformed arguments to command.
On 10/29/2013 4:36 AM, Mike Gabriel wrote: Unknown command or malformed arguments to command.
If I put an Unknown command or malformed arguments to command.
echo "testing" # exact text doesn't matter Unknown command or malformed arguments to command. Too many unknown commands, stopping here.
Please contact me if you need assistance.
327: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=327 333: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=333 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems
-
Dan Halbert -
Mike Gabriel -
owner＠bugs.x2go.org