We did some work on bug 7060 in order to make it possible to start the server installer from the GNOME file manager. Unfortunately, the GNOME folks have decided to entirely remove the support for launching binaries or desktop files, see: https://www.linuxuprising.com/2018/05/nautilus-will-no-longer-launch-binaries.html However, this change might be reverted: https://www.linuxuprising.com/2018/05/nautilus-ability-to-launch-binaries-or.html https://gitlab.gnome.org/GNOME/nautilus/issues/443 We need to track what is happening in this area. On Fedora 30, things are broken: * Nautilus provides a checkbox "Allow running as program", but even though it is ticked, the file will open in gedit * Trying to run binaries is broken: Will give you an error message about missing libraries, even though this is not the case.
For reference, in RHEL 8 with nautilus 3.28.1 it is still possible to double click a .desktop file and get the question to trust it (and it will launch correctly). However the install-server script will be opened in gedit by default (can be fixed from nautilus' preferences). However with newer nautilus (tested 3.32.1) both files are simply opened in gedit. Changing nautilus preferences to run scripts allows install-server to work, but the .desktop file still opens in gedit after you tell nautilus to "run" it. Double-clicking a binary gives the same error in both the old and new nautilus: an error message saying that there is no application for opening "shared library files". I assume that is because all ELF binaries will be identified as libraries.
Upstream issue for allowing .desktop files again: https://gitlab.gnome.org/GNOME/nautilus/issues/445
Instructions now updated to something safer to account for the fact that the .desktop file might not work.
Looks good.