After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 343212 - Can't execute over SSH.
Can't execute over SSH.
Status: RESOLVED WONTFIX
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.23.x
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-28 17:08 UTC by Sebastien Bacher
Modified: 2012-08-25 16:26 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Sebastien Bacher 2006-05-28 17:08:15 UTC 
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/44441

"Currently, nautilus is not capable of executing files or determining permissions over the network
...
>Thanks for your bug. What version of Ubuntu do you use? The permission issue is similar to bug #33211 and supposed to be fixed with dapper. Please also describe one issue by bug 
...
Sorry about that, I thought the two bugs were related but they are not.

The permission bug is fixed.

Execution is still impossible via ssh.
...
> That's a feature request then. Would you expect it run the program on the server or on your local box?
...
Here is my expected results:
I open a executable script and nautilus asks me "Do you want to run "sweetbackup.py", or display its contents?" with the options of Run in Terminal, Display, Cancel, or Run.
If I opened an binary that uses X, I would like to see the program be run using X forwarding (if available on server)"
Comment 1 William Jon McCann 2012-08-25 16:26:50 UTC 
This strikes me as a pretty bad idea. Programs are defined with respect to the system they are installed on. They aren't executable outside of that system. Doing something like starting a session and trying to forward it to the remote one seems like something that the file manager should have no role in. Given that we don't intend for the file manager to be an application launcher per se I think this is a won't fix.