Re: enabling remote X Window sessions
On 08/21/2014 11:07 AM, Buchs, Kevin J. wrote:
Brian,
Thanks. I was heading in the direction of doing something like you
suggested (though I am not sure how to stop gdm and not log myself out),
On my machine, when I start the sytem, I end up at a graphical login
slim, like gdm. If I keypress Ctrl-Alt-F1, I am taking to tty1 for a
console login.
If I login there, I can stop slim (and presumably gdm) and startx from
the command line. (Not a systemd complaint here.) I used to be able to
type something like 'sudo /etc/init.d/gdm3 stop', but I don't know if
that way works anymore.
but I thought there has to be a better way. Though it may be the case
that I have other X communication problems, based on ps (showing the
command arguments), I am sure that Xorg is still running with the
argument that disables listening for TCP/IP traffic and I am sure that
Xorg will behave as it is instructed.
I'm far from an expert here, but I think when gdm starts, it is starting
X, so if you login from gdm, I think X will be started with TCP
listening disabled. I thought maybe that if you started X from a command
line with startx (bypassing gdm), you could see if that allowed you to
make the remote connection you wish.
I don't know much about gdm, so I'm not helpful there.
Good luck.
Kevin Buchs Research Computer Services Phone: 507-538-5459
Mayo Clinic 200 1st. St SW Rochester, MN 55905
http://mayoclinic.org http://facebook.com/MayoClinic
http://youtube.com/MayoClinic http://twitter.com/MayoClinic
On 08/21/2014 12:57 PM, Brian Flaherty wrote:
This might not be a good lead, but can you stop gdm3 on your machine,
log in to a console, start X with startx and see if it works? Maybe
there are startx options to allow TCP listening? If this works, then
deal with gdm. If this doesn't work, does it mean the problem is
elsewhere?
Reply to: