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 130703 - Executable files are run in $HOME instead of the current directory
Executable files are run in $HOME instead of the current directory
Status: RESOLVED DUPLICATE of bug 110407
Product: nautilus
Classification: Core
Component: File and Folder Operations
0.x.x [obsolete]
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-01-06 17:49 UTC by Daniel Brockman
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Daniel Brockman 2004-01-06 17:49:55 UTC 
Steps to reproduce the problem:

1. Execute the following commands (but make sure you don't have an
important file called `bar' in your home directory):
cd
touch foo
mkdir moomin
touch moomin/foo
echo "mv foo bar" > moomin/mymble.sh
chmod +x moomin/mymble.sh

2. Open a Nautilus window and enter the `moomin' directory.

3. Execute the `mymble.sh' script by double-clicking it and choosing `Run'
or `Run in Terminal'.

Expected result:
The file `~/moomin/foo' is moved to `~/moomin/bar'.

Actual result:
The file `~/foo' is moved to `~/bar'.

I can't see any reason for this behavior, and since it causes general
inconvenience and confusion (try running a bootstrap or configure script
from a package directory, for instance; it will appear to do nothing at
all), I believe it should be classified as a bug.
Comment 1 Matthew Gatto 2004-01-06 23:01:27 UTC 
Hmm, this was marked as fix in bug 110407. Guess it wasn't actually
fixed though ;). Thanks for the bug report.

*** This bug has been marked as a duplicate of 110407 ***