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 478599 - Desktop launchers (.desktop files) don't work on NFS mounted partitions
Desktop launchers (.desktop files) don't work on NFS mounted partitions
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-20 13:40 UTC by Irene Fernandez
Modified: 2009-11-02 18:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Irene Fernandez 2007-09-20 13:40:58 UTC 
Please describe the problem:
Scenario:
Debian etch with GNOME 2.14.3 desktop.
User's home directory is on an NFS mounted partition.

Problem:
Desktop launchers (whether old or newly created, for any application) do not work:

They are treated as regular text or executable files (depending on file permissions), and do not launch applications.



Steps to reproduce:
1. Create a user whose home directory is on a remote NFS mounted partition
2. Log in as this user
3. create a desktop launcher (.desktop files): using contextual menu or manually editing the file.
4. Clic on the launcher


Actual results:
Dialog asks whether we want to "run [launcher-name] or display its contents" 

(previously existing launchers did not have execute permissions- when clicking them, the .desktop file is displayed with gedit)

Expected results:
Application should be launched

Does this happen every time?
Yes

Other information:
This problem has been reproduced with Debian testing/unstable client running GNOME 2.18 desktop.

This problem does not take place if:
The user logs in using KDE session instead of GNOME.
The user's home is on a local partition instead of an NFS mounted one
Comment 1 Vincent Untz 2007-09-22 16:36:02 UTC 
Could be a duplicate of bug 92951.
Comment 2 Irene Fernandez 2007-09-24 08:35:48 UTC 
I didn't know this issue was due to nautilus, here's the version information:

I have replicated the problem with versions 2.14.3 and 2.18.1

HOWEVER, there was no such problem with version 2.8.2

bug 92951 seems to be an older on-going problem, whereas we started to detect this bug after a Debian upgrade, which changed nautilus version 2.8.2 (everything was working fine) to 2.14.3
Comment 3 Irene Fernandez 2008-04-04 10:15:51 UTC 
Just upgraded to nautilus 2.20.0-3 (debian package), and the proble is still there.
Comment 4 Tobias Mueller 2009-06-15 20:15:02 UTC 
Irene, could you please try with a more recent GNOME? Bug 502987 had a similar issue and it can't be reproduced with 2.26 :)
Comment 5 Cosimo Cecchi 2009-11-02 18:10:44 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!