ssh -X to open a file manager
2
I have to machines running Ubuntu 18.10
When ssh -X to another computer
ssh -X assistant@pc.local
firefox and google-chrome could be opened at the current machine with firefox
firefox
google-chrome
However, if tried to open the files manager with
xdg-open .
#or
nautilus .
the file manager is launched from the desktop of remote machine rather than the current.
ssh x11-forwarding
asked Jan 14 at 5:50
AliceAlice
405110
add a comment |
2
I have to machines running Ubuntu 18.10
When ssh -X to another computer
ssh -X assistant@pc.local
firefox and google-chrome could be opened at the current machine with firefox
firefox
google-chrome
However, if tried to open the files manager with
xdg-open .
#or
nautilus .
the file manager is launched from the desktop of remote machine rather than the current.
ssh x11-forwarding
asked Jan 14 at 5:50
AliceAlice
405110
add a comment |
2
2
2
I have to machines running Ubuntu 18.10
When ssh -X to another computer
ssh -X assistant@pc.local
firefox and google-chrome could be opened at the current machine with firefox
firefox
google-chrome
However, if tried to open the files manager with
xdg-open .
#or
nautilus .
the file manager is launched from the desktop of remote machine rather than the current.
ssh x11-forwarding
asked Jan 14 at 5:50
AliceAlice
405110
I have to machines running Ubuntu 18.10
When ssh -X to another computer
ssh -X assistant@pc.local
firefox and google-chrome could be opened at the current machine with firefox
firefox
google-chrome
However, if tried to open the files manager with
xdg-open .
#or
nautilus .
the file manager is launched from the desktop of remote machine rather than the current.
ssh x11-forwarding
ssh x11-forwarding
asked Jan 14 at 5:50
AliceAlice
405110
asked Jan 14 at 5:50
AliceAlice
405110
asked Jan 14 at 5:50
AliceAlice
405110
asked Jan 14 at 5:50
AliceAlice
405110
asked Jan 14 at 5:50
AliceAlice
405110
405110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
3
You need the --new-window option for Nautilus:
ssh -X remote-machine nautilus --new-window
answered Jan 14 at 6:37
bitinerantbitinerant
1114
1
Otherwise you should kill all Nautilus instances on the remote machine before launch it "locally".
– pa4080
Jan 14 at 7:09
In cases like this, we don't want to killnautilusin the remote computer. Otherwise this would be an attractive solution, but it does not work for me in 18.04.1 LTS (the remote computer, the server, is running standard Ubuntu 18.04.1 LTS). Thenautiluswindow is still opened on the remote computer's desktop. Does it work with Ubuntu 18.10?
– sudodus
Jan 14 at 7:21
1
@sudodus - Before I posted the answer, I tested it between 2 Ubuntu 18.04 laptops and it worked well. For the purposes of debugging, you could try pa4080's suggestion and kill Nautilus first. Also, check your~/.ssh/configfile options which may cause this to not work for you.
– bitinerant
Jan 14 at 7:28
Good, it works for you between 2 Ubuntu 18.04 laptops :-) I have not added anything special into my~/.ssh/configbut still it is failing for me, whilepcmanfmworks without any problems. Anyway, now the OP, @Alice, has two options. If your solution works for her, I will delete my answer, because she wants to runnautilus.
– sudodus
Jan 14 at 7:34
@Alice, I tested with a live session of Ubuntu 18.10 as the remote system, server. I installedopenssh-serverand created a (non-blank) password, which made it possible to log in viassh -X, and this way I managed to get thenautiluswindow in my local desktop (in the client computer). So you will probably succeed according to this answer :-)
– sudodus
Jan 14 at 8:10
|
show 2 more comments
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%2f1109531%2fssh-x-to-open-a-file-manager%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
3
You need the --new-window option for Nautilus:
ssh -X remote-machine nautilus --new-window
answered Jan 14 at 6:37
bitinerantbitinerant
1114
1
Otherwise you should kill all Nautilus instances on the remote machine before launch it "locally".
– pa4080
Jan 14 at 7:09
In cases like this, we don't want to killnautilusin the remote computer. Otherwise this would be an attractive solution, but it does not work for me in 18.04.1 LTS (the remote computer, the server, is running standard Ubuntu 18.04.1 LTS). Thenautiluswindow is still opened on the remote computer's desktop. Does it work with Ubuntu 18.10?
– sudodus
Jan 14 at 7:21
1
@sudodus - Before I posted the answer, I tested it between 2 Ubuntu 18.04 laptops and it worked well. For the purposes of debugging, you could try pa4080's suggestion and kill Nautilus first. Also, check your~/.ssh/configfile options which may cause this to not work for you.
– bitinerant
Jan 14 at 7:28
Good, it works for you between 2 Ubuntu 18.04 laptops :-) I have not added anything special into my~/.ssh/configbut still it is failing for me, whilepcmanfmworks without any problems. Anyway, now the OP, @Alice, has two options. If your solution works for her, I will delete my answer, because she wants to runnautilus.
– sudodus
Jan 14 at 7:34
@Alice, I tested with a live session of Ubuntu 18.10 as the remote system, server. I installedopenssh-serverand created a (non-blank) password, which made it possible to log in viassh -X, and this way I managed to get thenautiluswindow in my local desktop (in the client computer). So you will probably succeed according to this answer :-)
– sudodus
Jan 14 at 8:10
|
show 2 more comments
3
You need the --new-window option for Nautilus:
ssh -X remote-machine nautilus --new-window
answered Jan 14 at 6:37
bitinerantbitinerant
1114
1
Otherwise you should kill all Nautilus instances on the remote machine before launch it "locally".
– pa4080
Jan 14 at 7:09
In cases like this, we don't want to killnautilusin the remote computer. Otherwise this would be an attractive solution, but it does not work for me in 18.04.1 LTS (the remote computer, the server, is running standard Ubuntu 18.04.1 LTS). Thenautiluswindow is still opened on the remote computer's desktop. Does it work with Ubuntu 18.10?
– sudodus
Jan 14 at 7:21
1
@sudodus - Before I posted the answer, I tested it between 2 Ubuntu 18.04 laptops and it worked well. For the purposes of debugging, you could try pa4080's suggestion and kill Nautilus first. Also, check your~/.ssh/configfile options which may cause this to not work for you.
– bitinerant
Jan 14 at 7:28
Good, it works for you between 2 Ubuntu 18.04 laptops :-) I have not added anything special into my~/.ssh/configbut still it is failing for me, whilepcmanfmworks without any problems. Anyway, now the OP, @Alice, has two options. If your solution works for her, I will delete my answer, because she wants to runnautilus.
– sudodus
Jan 14 at 7:34
@Alice, I tested with a live session of Ubuntu 18.10 as the remote system, server. I installedopenssh-serverand created a (non-blank) password, which made it possible to log in viassh -X, and this way I managed to get thenautiluswindow in my local desktop (in the client computer). So you will probably succeed according to this answer :-)
– sudodus
Jan 14 at 8:10
|
show 2 more comments
3
3
3
You need the --new-window option for Nautilus:
ssh -X remote-machine nautilus --new-window
answered Jan 14 at 6:37
bitinerantbitinerant
1114
You need the --new-window option for Nautilus:
ssh -X remote-machine nautilus --new-window
answered Jan 14 at 6:37
bitinerantbitinerant
1114
answered Jan 14 at 6:37
bitinerantbitinerant
1114
answered Jan 14 at 6:37
bitinerantbitinerant
1114
answered Jan 14 at 6:37
bitinerantbitinerant
1114
1114
1
Otherwise you should kill all Nautilus instances on the remote machine before launch it "locally".
– pa4080
Jan 14 at 7:09
In cases like this, we don't want to killnautilusin the remote computer. Otherwise this would be an attractive solution, but it does not work for me in 18.04.1 LTS (the remote computer, the server, is running standard Ubuntu 18.04.1 LTS). Thenautiluswindow is still opened on the remote computer's desktop. Does it work with Ubuntu 18.10?
– sudodus
Jan 14 at 7:21
1
@sudodus - Before I posted the answer, I tested it between 2 Ubuntu 18.04 laptops and it worked well. For the purposes of debugging, you could try pa4080's suggestion and kill Nautilus first. Also, check your~/.ssh/configfile options which may cause this to not work for you.
– bitinerant
Jan 14 at 7:28
Good, it works for you between 2 Ubuntu 18.04 laptops :-) I have not added anything special into my~/.ssh/configbut still it is failing for me, whilepcmanfmworks without any problems. Anyway, now the OP, @Alice, has two options. If your solution works for her, I will delete my answer, because she wants to runnautilus.
– sudodus
Jan 14 at 7:34
@Alice, I tested with a live session of Ubuntu 18.10 as the remote system, server. I installedopenssh-serverand created a (non-blank) password, which made it possible to log in viassh -X, and this way I managed to get thenautiluswindow in my local desktop (in the client computer). So you will probably succeed according to this answer :-)
– sudodus
Jan 14 at 8:10
|
show 2 more comments
1
Otherwise you should kill all Nautilus instances on the remote machine before launch it "locally".
– pa4080
Jan 14 at 7:09
In cases like this, we don't want to killnautilusin the remote computer. Otherwise this would be an attractive solution, but it does not work for me in 18.04.1 LTS (the remote computer, the server, is running standard Ubuntu 18.04.1 LTS). Thenautiluswindow is still opened on the remote computer's desktop. Does it work with Ubuntu 18.10?
– sudodus
Jan 14 at 7:21
1
@sudodus - Before I posted the answer, I tested it between 2 Ubuntu 18.04 laptops and it worked well. For the purposes of debugging, you could try pa4080's suggestion and kill Nautilus first. Also, check your~/.ssh/configfile options which may cause this to not work for you.
– bitinerant
Jan 14 at 7:28
Good, it works for you between 2 Ubuntu 18.04 laptops :-) I have not added anything special into my~/.ssh/configbut still it is failing for me, whilepcmanfmworks without any problems. Anyway, now the OP, @Alice, has two options. If your solution works for her, I will delete my answer, because she wants to runnautilus.
– sudodus
Jan 14 at 7:34
@Alice, I tested with a live session of Ubuntu 18.10 as the remote system, server. I installedopenssh-serverand created a (non-blank) password, which made it possible to log in viassh -X, and this way I managed to get thenautiluswindow in my local desktop (in the client computer). So you will probably succeed according to this answer :-)
– sudodus
Jan 14 at 8:10
1
1
Otherwise you should kill all Nautilus instances on the remote machine before launch it "locally".
– pa4080
Jan 14 at 7:09
Otherwise you should kill all Nautilus instances on the remote machine before launch it "locally".
– pa4080
Jan 14 at 7:09
In cases like this, we don't want to kill
nautilus in the remote computer. Otherwise this would be an attractive solution, but it does not work for me in 18.04.1 LTS (the remote computer, the server, is running standard Ubuntu 18.04.1 LTS). The nautiluswindow is still opened on the remote computer's desktop. Does it work with Ubuntu 18.10?– sudodus
Jan 14 at 7:21
In cases like this, we don't want to kill
nautilus in the remote computer. Otherwise this would be an attractive solution, but it does not work for me in 18.04.1 LTS (the remote computer, the server, is running standard Ubuntu 18.04.1 LTS). The nautiluswindow is still opened on the remote computer's desktop. Does it work with Ubuntu 18.10?– sudodus
Jan 14 at 7:21
1
1
@sudodus - Before I posted the answer, I tested it between 2 Ubuntu 18.04 laptops and it worked well. For the purposes of debugging, you could try pa4080's suggestion and kill Nautilus first. Also, check your
~/.ssh/config file options which may cause this to not work for you.– bitinerant
Jan 14 at 7:28
@sudodus - Before I posted the answer, I tested it between 2 Ubuntu 18.04 laptops and it worked well. For the purposes of debugging, you could try pa4080's suggestion and kill Nautilus first. Also, check your
~/.ssh/config file options which may cause this to not work for you.– bitinerant
Jan 14 at 7:28
Good, it works for you between 2 Ubuntu 18.04 laptops :-) I have not added anything special into my
~/.ssh/config but still it is failing for me, while pcmanfm works without any problems. Anyway, now the OP, @Alice, has two options. If your solution works for her, I will delete my answer, because she wants to run nautilus.– sudodus
Jan 14 at 7:34
Good, it works for you between 2 Ubuntu 18.04 laptops :-) I have not added anything special into my
~/.ssh/config but still it is failing for me, while pcmanfm works without any problems. Anyway, now the OP, @Alice, has two options. If your solution works for her, I will delete my answer, because she wants to run nautilus.– sudodus
Jan 14 at 7:34
@Alice, I tested with a live session of Ubuntu 18.10 as the remote system, server. I installed
openssh-server and created a (non-blank) password, which made it possible to log in via ssh -X, and this way I managed to get the nautilus window in my local desktop (in the client computer). So you will probably succeed according to this answer :-)– sudodus
Jan 14 at 8:10
@Alice, I tested with a live session of Ubuntu 18.10 as the remote system, server. I installed
openssh-server and created a (non-blank) password, which made it possible to log in via ssh -X, and this way I managed to get the nautilus window in my local desktop (in the client computer). So you will probably succeed according to this answer :-)– sudodus
Jan 14 at 8:10
|
show 2 more comments
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%2f1109531%2fssh-x-to-open-a-file-manager%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
