#814771 nemo: refuses to launch application symlinks

Package:
nemo
Source:
nemo
Description:
File manager and graphical shell for Cinnamon
Submitter:
Michal Suchanek
Date:
2026-10-08 17:39:22 UTC
Severity:
normal
Tags:
#814771#5
Date:
2016-02-15 09:49:55 UTC
From:
To:
Hello,

I made a symlink on my desktop

lrwxrwxrwx chromium.desktop -> /usr/share/applications/chromium.desktop

When I try to start chromium from my desktop nemo complains that the
application is non-executable and untrusted. There is no reasonable way to make
the application file in /usr/share/applications executable. The symlink itself
is.

Please amend this mechanism so that launching symlinks to system applications
is possible without nemo complaining.

Thanks

Michal

#814771#14
Date:
2016-05-29 13:26:37 UTC
From:
To:
Hi Michal,

Thanks for your report.

El Lunes 15 Febrero 2016 10:49 CET, Michal Suchanek <michal.suchanek@ruk.cuni.cz> Ha escrito:
https://github.com/linuxmint/nemo/issues/1130

Unfortunately, there has been no activity there.

I wanted to tell you that a simple way of obtaining a similar
behavior to what you want is to copy the .desktop file instead of
making a symlink.  Of course this is not exactly the same but
may serve as a workaround until the issue is fixed.

Cheers,
Marga

#814771#27
Date:
2026-09-26 19:13:23 UTC
From:
To:
Hi Michal,

sorry for the very long silence on this report. The problem is still
there in nemo 6.6.4-1 in unstable: a symlink on the desktop to
/usr/share/applications/org.gnome.Calculator.desktop is shown with its
file name and a generic icon, and double-clicking it opens the
"Untrusted application launcher" dialog.

The upstream issue [1] was closed in 2020 without a fix (the suggested
workaround was to make the system file executable as root), which is why
bts-link added the fixed-upstream tag; I have removed it.

The cause: nemo trusts a launcher if it is executable or if it lives in
a system data directory, but for a symlink the directory checked is the
one of the link, while the permissions read are the ones of the target
(root-owned, not executable). I have proposed upstream [2] to resolve
the symlink and apply the system directory check to the file it points
to, so a link to a system launcher is trusted and one to a file
elsewhere is not. It is tested in a VM with nemo 6.6.4 rebuilt with that
change.

Until then, the "Launch Anyway" button of the dialog starts the
application, and copying the launcher to the desktop instead of linking
it (then making the copy executable) avoids the dialog altogether.

[1] https://github.com/linuxmint/nemo/issues/1130
[2] https://github.com/linuxmint/nemo/pull/3846

Regards,
Fabio