Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • Likely impossible to answer without knowing how you are "running" the .desktop file and, maybe, what the content of linuxStart.sh is, but your issue is most likely related to Exec=./linuxStart.sh: the Desktop Entry Specification states that the Exec key must be either a full path or a name, which is in turn searched for in your PATH. Does the directory that contains linuxStart.sh appear in your PATH? Commented Sep 18, 2021 at 16:06
  • Thanks. No, it's not in my path. The idea is to make a portable app for linux (for DokuWiki). Since it should be run from Dropbox, USB, etc. (and be user-friendly) I cannot use the full path. The command however executes fine, it simply ignores the xdg-open command. I'll post the linuxStart.sh as well. Commented Sep 18, 2021 at 16:15
  • Thank you for you edit. I wouldn't know how it's supposed to work on MX Linux/Xfce but, on Arch Linux + KDE, Exec=./foo only works if foo can be found through a PATH search. So (based on the aforementioned Desktop Entry Specification) I'm reasonably sure Exec=./foo isn't portable. (How should the program interpreting the .desktop file guess the actual path . is meant to refer to? Note that .desktop files are also used by menus and launchers, which generally won't have an intuitive concept of "current working directory"). Commented Sep 18, 2021 at 16:50
  • 1
    That said, trying to be more helpful with the issue you describe: how are you detecting that xdg-open http://localhost:8080 is not executed, while others command are? Are you watching the script running in a terminal emulator? Do you get any error message? Commented Sep 18, 2021 at 17:09
  • I got it working!! I simply removed Terminal=true. It seemed to launch a separate X terminal and mess things up. I did not see any error messages. Can you reproduce on Arch? Thank you! Commented Sep 18, 2021 at 17:30