| 1 |
On Sun, 7 Feb 2021 12:10:50 -0700, thelma@×××××××××××.com wrote: |
| 2 |
|
| 3 |
> On 2/7/21 4:09 AM, Neil Bothwick wrote: |
| 4 |
> > On Sun, 7 Feb 2021 01:28:39 -0700, thelma@×××××××××××.com wrote: |
| 5 |
> > |
| 6 |
> >> I disable "slim" login manager and try not to use any display manger |
| 7 |
> >> (for simplicity). I start X from: |
| 8 |
> >> |
| 9 |
> >> ~/.bash_profile |
| 10 |
> >> exec startx -- vt1 |
| 11 |
> >> |
| 12 |
> >> but now when I try to ssh as user, I get: |
| 13 |
> >> |
| 14 |
> >> (==) Using system config directory "/usr/share/X11/xorg.conf.d" |
| 15 |
> >> (EE) |
| 16 |
> >> Fatal server error: |
| 17 |
> >> (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission |
| 18 |
> >> denied) |
| 19 |
> > |
| 20 |
> > Of course you are, because you are still trying to start X. If you |
| 21 |
> > must start X from .bash_profile, you need something like |
| 22 |
> > |
| 23 |
> > [ -z "$SSH_TTY" ] && startx ... |
| 24 |
> > |
| 25 |
> > to only start it when not using SSH. |
| 26 |
> |
| 27 |
> What do you suggest? |
| 28 |
> I was planning to get away from "slim" as I think it is getting more |
| 29 |
> unstable; I just need a simple system to start X, log-in over ssh and |
| 30 |
> use x2go session. |
| 31 |
|
| 32 |
Why do you need to start X, doesn't x2go run its own X session? You are |
| 33 |
trying to start X in an SSH session, which is what gives your error. The |
| 34 |
line I suggested runs startx only if you are not logging in via SSH. No |
| 35 |
display manager is involved. |
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
Neil Bothwick |
| 40 |
|
| 41 |
If you got the words it does not mean you got the knowledge. |
Archives