Starting X remotely on the remote host
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
0
I want to remotely start xserver on the remote machine.
If I type "startx" directly on the host machine (i.e. using physical keyboard), the xserver starts as expected. However, when I try to do that over ssh with the same user this does not work.
I get the following server error:
(EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied)
sudo startx still works even remotely.
What is preventing xserver to start on remote connections? And how to go around this?
ssh xorg
asked Mar 25 at 13:36
smihaelsmihael
1408
add a comment |
0
I want to remotely start xserver on the remote machine.
If I type "startx" directly on the host machine (i.e. using physical keyboard), the xserver starts as expected. However, when I try to do that over ssh with the same user this does not work.
I get the following server error:
(EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied)
sudo startx still works even remotely.
What is preventing xserver to start on remote connections? And how to go around this?
ssh xorg
asked Mar 25 at 13:36
smihaelsmihael
1408
i think it's simply the two things are mutually incompatible. ssh has text-only support no remote desktop support. startx is probably trying to send somthing over the connection that a text-only pipe cannot support.
– tatsu
Mar 25 at 14:37
I'd use input methods of the physical host then. I just want to have a possibility to remotely start X. The only reasonable explanation would be that remote user can't trigger access to host's input/output devices on kernel level.
– smihael
Mar 25 at 15:11
add a comment |
0
0
0
I want to remotely start xserver on the remote machine.
If I type "startx" directly on the host machine (i.e. using physical keyboard), the xserver starts as expected. However, when I try to do that over ssh with the same user this does not work.
I get the following server error:
(EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied)
sudo startx still works even remotely.
What is preventing xserver to start on remote connections? And how to go around this?
ssh xorg
asked Mar 25 at 13:36
smihaelsmihael
1408
I want to remotely start xserver on the remote machine.
If I type "startx" directly on the host machine (i.e. using physical keyboard), the xserver starts as expected. However, when I try to do that over ssh with the same user this does not work.
I get the following server error:
(EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied)
sudo startx still works even remotely.
What is preventing xserver to start on remote connections? And how to go around this?
ssh xorg
ssh xorg
asked Mar 25 at 13:36
smihaelsmihael
1408
asked Mar 25 at 13:36
smihaelsmihael
1408
asked Mar 25 at 13:36
smihaelsmihael
1408
asked Mar 25 at 13:36
smihaelsmihael
1408
asked Mar 25 at 13:36
smihaelsmihael
1408
1408
i think it's simply the two things are mutually incompatible. ssh has text-only support no remote desktop support. startx is probably trying to send somthing over the connection that a text-only pipe cannot support.
– tatsu
Mar 25 at 14:37
I'd use input methods of the physical host then. I just want to have a possibility to remotely start X. The only reasonable explanation would be that remote user can't trigger access to host's input/output devices on kernel level.
– smihael
Mar 25 at 15:11
add a comment |
i think it's simply the two things are mutually incompatible. ssh has text-only support no remote desktop support. startx is probably trying to send somthing over the connection that a text-only pipe cannot support.
– tatsu
Mar 25 at 14:37
I'd use input methods of the physical host then. I just want to have a possibility to remotely start X. The only reasonable explanation would be that remote user can't trigger access to host's input/output devices on kernel level.
– smihael
Mar 25 at 15:11
i think it's simply the two things are mutually incompatible. ssh has text-only support no remote desktop support. startx is probably trying to send somthing over the connection that a text-only pipe cannot support.
– tatsu
Mar 25 at 14:37
i think it's simply the two things are mutually incompatible. ssh has text-only support no remote desktop support. startx is probably trying to send somthing over the connection that a text-only pipe cannot support.
– tatsu
Mar 25 at 14:37
I'd use input methods of the physical host then. I just want to have a possibility to remotely start X. The only reasonable explanation would be that remote user can't trigger access to host's input/output devices on kernel level.
– smihael
Mar 25 at 15:11
I'd use input methods of the physical host then. I just want to have a possibility to remotely start X. The only reasonable explanation would be that remote user can't trigger access to host's input/output devices on kernel level.
– smihael
Mar 25 at 15:11
add a comment |
1 Answer
1
active
oldest
votes
0
Read man ssh, and use either the -X or -Y options.
https://manpages.ubuntu.com/manpages/bionic/en/man1/ssh.1.html
answered Mar 25 at 17:37
waltinatorwaltinator
23k74169
-X Enables X11 forwarding. This can also be specified on a per-host basis in a configuration file. -Y Enables trusted X11 forwarding. Trusted X11 forwardings are not subjected to the X11 SECURITY extension controls.
– saleetzo
Mar 25 at 17:50
This does not solve my problem. I do not want to forward X. I only want to remotely turn on X via ssh. From that point on, X server should run locally on the host machine. My workaround is currently to start one of display managers as root and then login.
– smihael
Mar 26 at 8:16
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1128534%2fstarting-x-remotely-on-the-remote-host%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
Read man ssh, and use either the -X or -Y options.
https://manpages.ubuntu.com/manpages/bionic/en/man1/ssh.1.html
answered Mar 25 at 17:37
waltinatorwaltinator
23k74169
-X Enables X11 forwarding. This can also be specified on a per-host basis in a configuration file. -Y Enables trusted X11 forwarding. Trusted X11 forwardings are not subjected to the X11 SECURITY extension controls.
– saleetzo
Mar 25 at 17:50
This does not solve my problem. I do not want to forward X. I only want to remotely turn on X via ssh. From that point on, X server should run locally on the host machine. My workaround is currently to start one of display managers as root and then login.
– smihael
Mar 26 at 8:16
add a comment |
0
Read man ssh, and use either the -X or -Y options.
https://manpages.ubuntu.com/manpages/bionic/en/man1/ssh.1.html
answered Mar 25 at 17:37
waltinatorwaltinator
23k74169
-X Enables X11 forwarding. This can also be specified on a per-host basis in a configuration file. -Y Enables trusted X11 forwarding. Trusted X11 forwardings are not subjected to the X11 SECURITY extension controls.
– saleetzo
Mar 25 at 17:50
This does not solve my problem. I do not want to forward X. I only want to remotely turn on X via ssh. From that point on, X server should run locally on the host machine. My workaround is currently to start one of display managers as root and then login.
– smihael
Mar 26 at 8:16
add a comment |
0
0
0
Read man ssh, and use either the -X or -Y options.
https://manpages.ubuntu.com/manpages/bionic/en/man1/ssh.1.html
answered Mar 25 at 17:37
waltinatorwaltinator
23k74169
Read man ssh, and use either the -X or -Y options.
https://manpages.ubuntu.com/manpages/bionic/en/man1/ssh.1.html
answered Mar 25 at 17:37
waltinatorwaltinator
23k74169
answered Mar 25 at 17:37
waltinatorwaltinator
23k74169
answered Mar 25 at 17:37
waltinatorwaltinator
23k74169
answered Mar 25 at 17:37
waltinatorwaltinator
23k74169
23k74169
-X Enables X11 forwarding. This can also be specified on a per-host basis in a configuration file. -Y Enables trusted X11 forwarding. Trusted X11 forwardings are not subjected to the X11 SECURITY extension controls.
– saleetzo
Mar 25 at 17:50
This does not solve my problem. I do not want to forward X. I only want to remotely turn on X via ssh. From that point on, X server should run locally on the host machine. My workaround is currently to start one of display managers as root and then login.
– smihael
Mar 26 at 8:16
add a comment |
-X Enables X11 forwarding. This can also be specified on a per-host basis in a configuration file. -Y Enables trusted X11 forwarding. Trusted X11 forwardings are not subjected to the X11 SECURITY extension controls.
– saleetzo
Mar 25 at 17:50
This does not solve my problem. I do not want to forward X. I only want to remotely turn on X via ssh. From that point on, X server should run locally on the host machine. My workaround is currently to start one of display managers as root and then login.
– smihael
Mar 26 at 8:16
-X Enables X11 forwarding. This can also be specified on a per-host basis in a configuration file. -Y Enables trusted X11 forwarding. Trusted X11 forwardings are not subjected to the X11 SECURITY extension controls.
– saleetzo
Mar 25 at 17:50
-X Enables X11 forwarding. This can also be specified on a per-host basis in a configuration file. -Y Enables trusted X11 forwarding. Trusted X11 forwardings are not subjected to the X11 SECURITY extension controls.
– saleetzo
Mar 25 at 17:50
This does not solve my problem. I do not want to forward X. I only want to remotely turn on X via ssh. From that point on, X server should run locally on the host machine. My workaround is currently to start one of display managers as root and then login.
– smihael
Mar 26 at 8:16
This does not solve my problem. I do not want to forward X. I only want to remotely turn on X via ssh. From that point on, X server should run locally on the host machine. My workaround is currently to start one of display managers as root and then login.
– smihael
Mar 26 at 8:16
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1128534%2fstarting-x-remotely-on-the-remote-host%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
i think it's simply the two things are mutually incompatible. ssh has text-only support no remote desktop support. startx is probably trying to send somthing over the connection that a text-only pipe cannot support.
– tatsu
Mar 25 at 14:37
I'd use input methods of the physical host then. I just want to have a possibility to remotely start X. The only reasonable explanation would be that remote user can't trigger access to host's input/output devices on kernel level.
– smihael
Mar 25 at 15:11