17.10 / 18.04.TLS .desktop files are no longer trusted












5















I've moved from 17.04 to 17.10 (by update, not fresh install)



I have a bunch of customized .desktop files in my desktop.



When I try to run then, I get a message telling me these are "untrusted", and I have to retrust them manually.



Is there a way to trust them all?



note:




  • desktop files have executable bit set (I have run chmod +x).

  • before trusting they appear as a generic file, after with proper icon (e.g. terminal, browser, ...)

  • worked fine before (that is icons and action were OK in 17.04)

  • desktop to samba share are OK.


edit:




  • files are not located in /tmp neither in $HOME.


I have read :




Execute-Permission Bit Required




  • Applications, including desktops and shells, must not run executable code from files when they are both:


    • lacking the executable bit

    • located in a user's home directory or temporary directory.







  • my desktop are in neither of those.




  • This includes *.desktop, *.jar, and *.exe files.





  • .desktop files being r--r--r-- or r-xr-xr-x won't execute.




  • Nothing may provide a workaround to run them anyway automatically ...




Update




  • 18.04 problem persist, accepted answer still work.










share|improve this question




















  • 2





    Possible duplicate of Permission of a .desktop file

    – JoKeR
    Oct 25 '17 at 20:45











  • @JoKeR I did set +x bit ..

    – Archemar
    Oct 25 '17 at 20:51











  • Did you read the policy from the answer mentioned in that post?

    – JoKeR
    Oct 25 '17 at 20:58













  • @JoKeR I have that too, with files which permissions are set to 755 so this is not a dupe, its something new with 17.10

    – Videonauth
    Oct 25 '17 at 21:09











  • might be reported as a bug then...

    – JoKeR
    Oct 25 '17 at 21:15
















5















I've moved from 17.04 to 17.10 (by update, not fresh install)



I have a bunch of customized .desktop files in my desktop.



When I try to run then, I get a message telling me these are "untrusted", and I have to retrust them manually.



Is there a way to trust them all?



note:




  • desktop files have executable bit set (I have run chmod +x).

  • before trusting they appear as a generic file, after with proper icon (e.g. terminal, browser, ...)

  • worked fine before (that is icons and action were OK in 17.04)

  • desktop to samba share are OK.


edit:




  • files are not located in /tmp neither in $HOME.


I have read :




Execute-Permission Bit Required




  • Applications, including desktops and shells, must not run executable code from files when they are both:


    • lacking the executable bit

    • located in a user's home directory or temporary directory.







  • my desktop are in neither of those.




  • This includes *.desktop, *.jar, and *.exe files.





  • .desktop files being r--r--r-- or r-xr-xr-x won't execute.




  • Nothing may provide a workaround to run them anyway automatically ...




Update




  • 18.04 problem persist, accepted answer still work.










share|improve this question




















  • 2





    Possible duplicate of Permission of a .desktop file

    – JoKeR
    Oct 25 '17 at 20:45











  • @JoKeR I did set +x bit ..

    – Archemar
    Oct 25 '17 at 20:51











  • Did you read the policy from the answer mentioned in that post?

    – JoKeR
    Oct 25 '17 at 20:58













  • @JoKeR I have that too, with files which permissions are set to 755 so this is not a dupe, its something new with 17.10

    – Videonauth
    Oct 25 '17 at 21:09











  • might be reported as a bug then...

    – JoKeR
    Oct 25 '17 at 21:15














5












5








5


3






I've moved from 17.04 to 17.10 (by update, not fresh install)



I have a bunch of customized .desktop files in my desktop.



When I try to run then, I get a message telling me these are "untrusted", and I have to retrust them manually.



Is there a way to trust them all?



note:




  • desktop files have executable bit set (I have run chmod +x).

  • before trusting they appear as a generic file, after with proper icon (e.g. terminal, browser, ...)

  • worked fine before (that is icons and action were OK in 17.04)

  • desktop to samba share are OK.


edit:




  • files are not located in /tmp neither in $HOME.


I have read :




Execute-Permission Bit Required




  • Applications, including desktops and shells, must not run executable code from files when they are both:


    • lacking the executable bit

    • located in a user's home directory or temporary directory.







  • my desktop are in neither of those.




  • This includes *.desktop, *.jar, and *.exe files.





  • .desktop files being r--r--r-- or r-xr-xr-x won't execute.




  • Nothing may provide a workaround to run them anyway automatically ...




Update




  • 18.04 problem persist, accepted answer still work.










share|improve this question
















I've moved from 17.04 to 17.10 (by update, not fresh install)



I have a bunch of customized .desktop files in my desktop.



When I try to run then, I get a message telling me these are "untrusted", and I have to retrust them manually.



Is there a way to trust them all?



note:




  • desktop files have executable bit set (I have run chmod +x).

  • before trusting they appear as a generic file, after with proper icon (e.g. terminal, browser, ...)

  • worked fine before (that is icons and action were OK in 17.04)

  • desktop to samba share are OK.


edit:




  • files are not located in /tmp neither in $HOME.


I have read :




Execute-Permission Bit Required




  • Applications, including desktops and shells, must not run executable code from files when they are both:


    • lacking the executable bit

    • located in a user's home directory or temporary directory.







  • my desktop are in neither of those.




  • This includes *.desktop, *.jar, and *.exe files.





  • .desktop files being r--r--r-- or r-xr-xr-x won't execute.




  • Nothing may provide a workaround to run them anyway automatically ...




Update




  • 18.04 problem persist, accepted answer still work.







18.04 17.10 .desktop






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 13 at 17:06







Archemar

















asked Oct 25 '17 at 20:14









ArchemarArchemar

432314




432314








  • 2





    Possible duplicate of Permission of a .desktop file

    – JoKeR
    Oct 25 '17 at 20:45











  • @JoKeR I did set +x bit ..

    – Archemar
    Oct 25 '17 at 20:51











  • Did you read the policy from the answer mentioned in that post?

    – JoKeR
    Oct 25 '17 at 20:58













  • @JoKeR I have that too, with files which permissions are set to 755 so this is not a dupe, its something new with 17.10

    – Videonauth
    Oct 25 '17 at 21:09











  • might be reported as a bug then...

    – JoKeR
    Oct 25 '17 at 21:15














  • 2





    Possible duplicate of Permission of a .desktop file

    – JoKeR
    Oct 25 '17 at 20:45











  • @JoKeR I did set +x bit ..

    – Archemar
    Oct 25 '17 at 20:51











  • Did you read the policy from the answer mentioned in that post?

    – JoKeR
    Oct 25 '17 at 20:58













  • @JoKeR I have that too, with files which permissions are set to 755 so this is not a dupe, its something new with 17.10

    – Videonauth
    Oct 25 '17 at 21:09











  • might be reported as a bug then...

    – JoKeR
    Oct 25 '17 at 21:15








2




2





Possible duplicate of Permission of a .desktop file

– JoKeR
Oct 25 '17 at 20:45





Possible duplicate of Permission of a .desktop file

– JoKeR
Oct 25 '17 at 20:45













@JoKeR I did set +x bit ..

– Archemar
Oct 25 '17 at 20:51





@JoKeR I did set +x bit ..

– Archemar
Oct 25 '17 at 20:51













Did you read the policy from the answer mentioned in that post?

– JoKeR
Oct 25 '17 at 20:58







Did you read the policy from the answer mentioned in that post?

– JoKeR
Oct 25 '17 at 20:58















@JoKeR I have that too, with files which permissions are set to 755 so this is not a dupe, its something new with 17.10

– Videonauth
Oct 25 '17 at 21:09





@JoKeR I have that too, with files which permissions are set to 755 so this is not a dupe, its something new with 17.10

– Videonauth
Oct 25 '17 at 21:09













might be reported as a bug then...

– JoKeR
Oct 25 '17 at 21:15





might be reported as a bug then...

– JoKeR
Oct 25 '17 at 21:15










1 Answer
1






active

oldest

votes


















7














I found my desktop files being mentioned in a binary file called ~/.local/share/gvfs-metadata/home which I could not edit. However, after some digging, I found the gio command. Run the following command followed by doing a refresh in nautilus



gio set yourfile.desktop "metadata::trusted" yes





share|improve this answer


























  • does it work for you?

    – Pierre.Vriens
    Jan 14 '18 at 8:04






  • 4





    hardest part was to find F5 command to refresh desktop :(

    – Archemar
    Jan 14 '18 at 17:27











  • It worked for me, but only AFTER I did a refresh. This has been an irritation to me for several weeks before I finally found this solution. I hope it works for everyone.

    – Byron Smith
    Jan 15 '18 at 3:13











  • for all icons, do this ls -1 ~/Desktop/*.desktop | xargs -i gio set "{}" "metadata::trusted" yes and then hit the F5 key to refresh

    – knb
    Oct 24 '18 at 15:22











  • I think this no longer works in 18.04 or 18.10. I don't know what the new solution is.

    – Byron Smith
    Dec 28 '18 at 7:13











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f969231%2f17-10-18-04-tls-desktop-files-are-no-longer-trusted%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









7














I found my desktop files being mentioned in a binary file called ~/.local/share/gvfs-metadata/home which I could not edit. However, after some digging, I found the gio command. Run the following command followed by doing a refresh in nautilus



gio set yourfile.desktop "metadata::trusted" yes





share|improve this answer


























  • does it work for you?

    – Pierre.Vriens
    Jan 14 '18 at 8:04






  • 4





    hardest part was to find F5 command to refresh desktop :(

    – Archemar
    Jan 14 '18 at 17:27











  • It worked for me, but only AFTER I did a refresh. This has been an irritation to me for several weeks before I finally found this solution. I hope it works for everyone.

    – Byron Smith
    Jan 15 '18 at 3:13











  • for all icons, do this ls -1 ~/Desktop/*.desktop | xargs -i gio set "{}" "metadata::trusted" yes and then hit the F5 key to refresh

    – knb
    Oct 24 '18 at 15:22











  • I think this no longer works in 18.04 or 18.10. I don't know what the new solution is.

    – Byron Smith
    Dec 28 '18 at 7:13
















7














I found my desktop files being mentioned in a binary file called ~/.local/share/gvfs-metadata/home which I could not edit. However, after some digging, I found the gio command. Run the following command followed by doing a refresh in nautilus



gio set yourfile.desktop "metadata::trusted" yes





share|improve this answer


























  • does it work for you?

    – Pierre.Vriens
    Jan 14 '18 at 8:04






  • 4





    hardest part was to find F5 command to refresh desktop :(

    – Archemar
    Jan 14 '18 at 17:27











  • It worked for me, but only AFTER I did a refresh. This has been an irritation to me for several weeks before I finally found this solution. I hope it works for everyone.

    – Byron Smith
    Jan 15 '18 at 3:13











  • for all icons, do this ls -1 ~/Desktop/*.desktop | xargs -i gio set "{}" "metadata::trusted" yes and then hit the F5 key to refresh

    – knb
    Oct 24 '18 at 15:22











  • I think this no longer works in 18.04 or 18.10. I don't know what the new solution is.

    – Byron Smith
    Dec 28 '18 at 7:13














7












7








7







I found my desktop files being mentioned in a binary file called ~/.local/share/gvfs-metadata/home which I could not edit. However, after some digging, I found the gio command. Run the following command followed by doing a refresh in nautilus



gio set yourfile.desktop "metadata::trusted" yes





share|improve this answer















I found my desktop files being mentioned in a binary file called ~/.local/share/gvfs-metadata/home which I could not edit. However, after some digging, I found the gio command. Run the following command followed by doing a refresh in nautilus



gio set yourfile.desktop "metadata::trusted" yes






share|improve this answer














share|improve this answer



share|improve this answer








edited Oct 19 '18 at 8:06









pomsky

30.3k1193126




30.3k1193126










answered Jan 14 '18 at 6:15









Byron SmithByron Smith

8613




8613













  • does it work for you?

    – Pierre.Vriens
    Jan 14 '18 at 8:04






  • 4





    hardest part was to find F5 command to refresh desktop :(

    – Archemar
    Jan 14 '18 at 17:27











  • It worked for me, but only AFTER I did a refresh. This has been an irritation to me for several weeks before I finally found this solution. I hope it works for everyone.

    – Byron Smith
    Jan 15 '18 at 3:13











  • for all icons, do this ls -1 ~/Desktop/*.desktop | xargs -i gio set "{}" "metadata::trusted" yes and then hit the F5 key to refresh

    – knb
    Oct 24 '18 at 15:22











  • I think this no longer works in 18.04 or 18.10. I don't know what the new solution is.

    – Byron Smith
    Dec 28 '18 at 7:13



















  • does it work for you?

    – Pierre.Vriens
    Jan 14 '18 at 8:04






  • 4





    hardest part was to find F5 command to refresh desktop :(

    – Archemar
    Jan 14 '18 at 17:27











  • It worked for me, but only AFTER I did a refresh. This has been an irritation to me for several weeks before I finally found this solution. I hope it works for everyone.

    – Byron Smith
    Jan 15 '18 at 3:13











  • for all icons, do this ls -1 ~/Desktop/*.desktop | xargs -i gio set "{}" "metadata::trusted" yes and then hit the F5 key to refresh

    – knb
    Oct 24 '18 at 15:22











  • I think this no longer works in 18.04 or 18.10. I don't know what the new solution is.

    – Byron Smith
    Dec 28 '18 at 7:13

















does it work for you?

– Pierre.Vriens
Jan 14 '18 at 8:04





does it work for you?

– Pierre.Vriens
Jan 14 '18 at 8:04




4




4





hardest part was to find F5 command to refresh desktop :(

– Archemar
Jan 14 '18 at 17:27





hardest part was to find F5 command to refresh desktop :(

– Archemar
Jan 14 '18 at 17:27













It worked for me, but only AFTER I did a refresh. This has been an irritation to me for several weeks before I finally found this solution. I hope it works for everyone.

– Byron Smith
Jan 15 '18 at 3:13





It worked for me, but only AFTER I did a refresh. This has been an irritation to me for several weeks before I finally found this solution. I hope it works for everyone.

– Byron Smith
Jan 15 '18 at 3:13













for all icons, do this ls -1 ~/Desktop/*.desktop | xargs -i gio set "{}" "metadata::trusted" yes and then hit the F5 key to refresh

– knb
Oct 24 '18 at 15:22





for all icons, do this ls -1 ~/Desktop/*.desktop | xargs -i gio set "{}" "metadata::trusted" yes and then hit the F5 key to refresh

– knb
Oct 24 '18 at 15:22













I think this no longer works in 18.04 or 18.10. I don't know what the new solution is.

– Byron Smith
Dec 28 '18 at 7:13





I think this no longer works in 18.04 or 18.10. I don't know what the new solution is.

– Byron Smith
Dec 28 '18 at 7:13


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f969231%2f17-10-18-04-tls-desktop-files-are-no-longer-trusted%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Questions related to Moebius Transform of Characteristic Function of the Primes

List of scandals in India

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?