The source of the stty turned out to be in my own .bashrc, don't knowhow I managed to miss it or why it did not stop x2go from working on any other distribution (centos 6/7, SL 6/7, debian, mint, ubuntu), all of those distributions worked in spite of it. Also don't know why .bashrc was sourced when my normal login shell is ksh.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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.
Am 26.01.2017 um 05:56 schrieb Robert Dinse:
The source of the stty turned out to be in my own .bashrc, don't knowhow I managed to miss it or why it did not stop x2go from working on any other distribution (centos 6/7, SL 6/7, debian, mint, ubuntu), all of those distributions worked in spite of it. Also don't know why .bashrc was sourced when my normal login shell is ksh.
Maybe it's because OpenSuse insists on sourcing that file regardless of the login shell used? While it would be a stupid thing to do, the same goes for using systemd, and yet you see how many distributions are switched over to it. :->
Anyways, would you mind letting the list know what command was the culprit, so others can learn from your mistake?
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
Am 26.01.2017 um 09:09 schrieb Stefan Baur:
Maybe it's because OpenSuse insists on sourcing that file regardless of the login shell used? While it would be a stupid thing to do, the same goes for using systemd, and yet you see how many distributions are switched over to it. :->
s/are/have/
ENOTENOUGHCAFFEINE, ETOOEARLYINTHEMORNINGFORCOHERENTENGLISH
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
Yes said in the original message, there was an unguarded stty command in my .bashrc, specifically, stty erase '^?'.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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, 26 Jan 2017, Stefan Baur wrote:
Date: Thu, 26 Jan 2017 09:09:16 +0100 From: Stefan Baur <X2Go-ML-1@baur-itcs.de> To: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] OpenSuse
Am 26.01.2017 um 05:56 schrieb Robert Dinse:
The source of the stty turned out to be in my own .bashrc, don't knowhow I managed to miss it or why it did not stop x2go from working on any other distribution (centos 6/7, SL 6/7, debian, mint, ubuntu), all of those distributions worked in spite of it. Also don't know why .bashrc was sourced when my normal login shell is ksh.
Maybe it's because OpenSuse insists on sourcing that file regardless of the login shell used? While it would be a stupid thing to do, the same goes for using systemd, and yet you see how many distributions are switched over to it. :->
Anyways, would you mind letting the list know what command was the culprit, so others can learn from your mistake?
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
Am 26.01.2017 um 09:57 schrieb Robert Dinse:
Yes said in the original message, there was an unguarded sttycommand in my .bashrc, specifically, stty erase '^?'.
So what remains is the question why .bashrc is being sourced on OpenSuse
- for ksh
- in a non-interactive session equivalent to 'bash -l -c "echo foo"'
Re: 1), I would take that up with the OpenSuse folks if I were you.
Re: 2), I'm not sure if that is expected bash behavior or not. Mihai might know this from the top of his head, while I would have to go dig through the specs. If it's not expected behavior, then the question is if it's happening due to something you changed (like manually sourcing that file from another file that gets sourced), or if it is a bug with OpenSuse as well.
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On 26.01.2017 03:25 PM, Stefan Baur wrote:
So what remains is the question why .bashrc is being sourced on OpenSuse
- for ksh
- in a non-interactive session equivalent to 'bash -l -c "echo foo"'
Re: 1), I would take that up with the OpenSuse folks if I were you.
X2Go Client 4.0.5.1+ (hope I'm correct on the version) explicitly runs bash -l -c '...', so that's why ~/.bashrc is executed.
Re: 2), I'm not sure if that is expected bash behavior or not. Mihai might know this from the top of his head, while I would have to go dig through the specs. If it's not expected behavior, then the question is if it's happening due to something you changed (like manually sourcing that file from another file that gets sourced), or if it is a bug with OpenSuse as well.
Yes, it is expected behavior. Running ~/.bashrc is only bypassed when calling bash as a non-interactive, non-login shell. We explicitly spawn a login shell, though.
A good diagram regarding this rather complicated matter: http://blog.flowblok.id.au/static/images/shell-startup-actual.png
Mihai
I have servers running Centos 6/7, Scientific Linux 6/7, Fedora 25,Debian, Mint, Ubuntu, and Opensuse, of all of these only Opensuse shows this behavior, and Opensuse 13.2 did not, this only happened after upgrading to Leap 42.1.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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, 26 Jan 2017, Stefan Baur wrote:
Date: Thu, 26 Jan 2017 15:25:52 +0100 From: Stefan Baur <X2Go-ML-1@baur-itcs.de> To: Robert Dinse <nanook@eskimo.com> Cc: x2go-user@lists.x2go.org, Mihai Moldovan <ionic@ionic.de> Subject: Re: [X2Go-User] OpenSuse
Am 26.01.2017 um 09:57 schrieb Robert Dinse:
Yes said in the original message, there was an unguarded sttycommand in my .bashrc, specifically, stty erase '^?'.
So what remains is the question why .bashrc is being sourced on OpenSuse
- for ksh
- in a non-interactive session equivalent to 'bash -l -c "echo foo"'
Re: 1), I would take that up with the OpenSuse folks if I were you.
Re: 2), I'm not sure if that is expected bash behavior or not. Mihai might know this from the top of his head, while I would have to go dig through the specs. If it's not expected behavior, then the question is if it's happening due to something you changed (like manually sourcing that file from another file that gets sourced), or if it is a bug with OpenSuse as well.
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On 26.01.2017 10:04 PM, Robert Dinse wrote:
I have servers running Centos 6/7, Scientific Linux 6/7, Fedora 25,Debian, Mint, Ubuntu, and Opensuse, of all of these only Opensuse shows this behavior, and Opensuse 13.2 did not, this only happened after upgrading to Leap 42.1.
That's the real mystery, yeah. Are you sure that the client version is the same on all boxes?
We only started calling bash a login shell with 4.0.5.1 IIRC.
Mihai
These machines are the servers, the client in all cases is on Ubuntu14.10, and I've got the 4.0.5.0 version installed rather than 4.1.0.0 because the latter explodes rather than starts.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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, 26 Jan 2017, Mihai Moldovan wrote:
Date: Thu, 26 Jan 2017 22:06:32 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com>, Stefan Baur <X2Go-ML-1@baur-itcs.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] OpenSuse
On 26.01.2017 10:04 PM, Robert Dinse wrote:
I have servers running Centos 6/7, Scientific Linux 6/7, Fedora 25,Debian, Mint, Ubuntu, and Opensuse, of all of these only Opensuse shows this behavior, and Opensuse 13.2 did not, this only happened after upgrading to Leap 42.1.
That's the real mystery, yeah. Are you sure that the client version is the same on all boxes?
We only started calling bash a login shell with 4.0.5.1 IIRC.
Mihai
Am 26.01.2017 um 22:07 schrieb Robert Dinse:
... and I've got the 4.0.5.0 version installed rather than 4.1.0.0 because the latter explodes rather than starts.
That's the "4.1.0.0 isn't a release build yet" booby trap. To keep it from exploding, you need to start it with parameter: --cut-the-red-wire-not-the-blue-one
Kidding aside, 4.1.0.0 is currently only available as a nightly build ("heuler" repo), and, as Mihai explained over in <http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1140#23>, the package you pulled in from there was broken, and a fixed one will appear soon.
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
On 26.01.2017 10:07 PM, Robert Dinse wrote:
These machines are the servers, the client in all cases is on Ubuntu14.10, and I've got the 4.0.5.0 version installed rather than 4.1.0.0 because the latter explodes rather than starts.
The nightly 4.1.0.0 version should work now.
Still - the point here is that the bash login shell change came in 4.0.5.1, so if you used 4.0.5.0 on other machines, you naturally won't hit the issue (until these machines are upgraded to something higher than 4.0.5.0.)
Mihai
Re-installed 4.1.0.0 under Ubuntu 14.10 (x2goclient) and it mostly worksnow. I have one server that when I connect to it I get a tiny display on my end, not the big display with a tiny window that I got before with the xrandr issue. I have other servers running the same os (Ubuntu) with Mate that do not exhibit this problem.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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, 26 Jan 2017, Mihai Moldovan wrote:
Date: Thu, 26 Jan 2017 22:15:57 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com> Cc: Stefan Baur <X2Go-ML-1@baur-itcs.de>, x2go-user@lists.x2go.org Subject: Re: [X2Go-User] OpenSuse
On 26.01.2017 10:07 PM, Robert Dinse wrote:
These machines are the servers, the client in all cases is on Ubuntu14.10, and I've got the 4.0.5.0 version installed rather than 4.1.0.0 because the latter explodes rather than starts.
The nightly 4.1.0.0 version should work now.
Still - the point here is that the bash login shell change came in 4.0.5.1, so if you used 4.0.5.0 on other machines, you naturally won't hit the issue (until these machines are upgraded to something higher than 4.0.5.0.)
Mihai
Excuse me, typo in this email, Ubuntu 16.10 not 14.10.-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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, 26 Jan 2017, Robert Dinse wrote:
Date: Thu, 26 Jan 2017 13:07:47 -0800 (PST) From: Robert Dinse <nanook@eskimo.com> To: Mihai Moldovan <ionic@ionic.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] OpenSuse
These machines are the servers, the client in all cases is on Ubuntu14.10, and I've got the 4.0.5.0 version installed rather than 4.1.0.0 because the latter explodes rather than starts.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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, 26 Jan 2017, Mihai Moldovan wrote:
Date: Thu, 26 Jan 2017 22:06:32 +0100 From: Mihai Moldovan <ionic@ionic.de> To: Robert Dinse <nanook@eskimo.com>, Stefan Baur <X2Go-ML-1@baur-itcs.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] OpenSuse
On 26.01.2017 10:04 PM, Robert Dinse wrote:
I have servers running Centos 6/7, Scientific Linux 6/7, Fedora 25,Debian, Mint, Ubuntu, and Opensuse, of all of these only Opensuse shows this behavior, and Opensuse 13.2 did not, this only happened after upgrading to Leap 42.1.
That's the real mystery, yeah. Are you sure that the client version is the same on all boxes?
We only started calling bash a login shell with 4.0.5.1 IIRC.
Mihai
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
-
Mihai Moldovan -
Robert Dinse -
Stefan Baur