How to debug an XFCE launcher which fails to launch its app?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















I have a command for one of my launchers:



discord


That's all. When launch from the terminal, it runs fine, Discord starts as intended.



When I click the launcher, nothing happens. I see a small burst of CPU activity on the CPU monitor, that's all. Nothing starts.



Specifying the absolute path does not solve the problem.



What about using the full path to "Discord" instead of "discord"? This is what gets added when I simply add an "existing item" to the launcher:



/usr/share/discord/Discord


Nope. Nothing.



However, if I run /usr/share/discord/Discord in the terminal, it starts fine again.



Now, maybe there is a third way, the "actual" way of starting Discord? I don't really care, I want to know why it works in the terminal, and why it doesn't work in the launcher -- with the exact same command!



How do I debug this? How can I see the output of the obviously failed command (as indicated by the little burst in CPU activity)?










share|improve this question

























  • Know nothing about discord but you can try with a laucher like : xterm -e sh -c 'discord'

    – ctac_
    8 hours ago


















2















I have a command for one of my launchers:



discord


That's all. When launch from the terminal, it runs fine, Discord starts as intended.



When I click the launcher, nothing happens. I see a small burst of CPU activity on the CPU monitor, that's all. Nothing starts.



Specifying the absolute path does not solve the problem.



What about using the full path to "Discord" instead of "discord"? This is what gets added when I simply add an "existing item" to the launcher:



/usr/share/discord/Discord


Nope. Nothing.



However, if I run /usr/share/discord/Discord in the terminal, it starts fine again.



Now, maybe there is a third way, the "actual" way of starting Discord? I don't really care, I want to know why it works in the terminal, and why it doesn't work in the launcher -- with the exact same command!



How do I debug this? How can I see the output of the obviously failed command (as indicated by the little burst in CPU activity)?










share|improve this question

























  • Know nothing about discord but you can try with a laucher like : xterm -e sh -c 'discord'

    – ctac_
    8 hours ago














2












2








2








I have a command for one of my launchers:



discord


That's all. When launch from the terminal, it runs fine, Discord starts as intended.



When I click the launcher, nothing happens. I see a small burst of CPU activity on the CPU monitor, that's all. Nothing starts.



Specifying the absolute path does not solve the problem.



What about using the full path to "Discord" instead of "discord"? This is what gets added when I simply add an "existing item" to the launcher:



/usr/share/discord/Discord


Nope. Nothing.



However, if I run /usr/share/discord/Discord in the terminal, it starts fine again.



Now, maybe there is a third way, the "actual" way of starting Discord? I don't really care, I want to know why it works in the terminal, and why it doesn't work in the launcher -- with the exact same command!



How do I debug this? How can I see the output of the obviously failed command (as indicated by the little burst in CPU activity)?










share|improve this question
















I have a command for one of my launchers:



discord


That's all. When launch from the terminal, it runs fine, Discord starts as intended.



When I click the launcher, nothing happens. I see a small burst of CPU activity on the CPU monitor, that's all. Nothing starts.



Specifying the absolute path does not solve the problem.



What about using the full path to "Discord" instead of "discord"? This is what gets added when I simply add an "existing item" to the launcher:



/usr/share/discord/Discord


Nope. Nothing.



However, if I run /usr/share/discord/Discord in the terminal, it starts fine again.



Now, maybe there is a third way, the "actual" way of starting Discord? I don't really care, I want to know why it works in the terminal, and why it doesn't work in the launcher -- with the exact same command!



How do I debug this? How can I see the output of the obviously failed command (as indicated by the little burst in CPU activity)?







xfce application launcher






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 2 mins ago









K7AAY

956928




956928










asked 9 hours ago









AlphaCentauriAlphaCentauri

227129




227129













  • Know nothing about discord but you can try with a laucher like : xterm -e sh -c 'discord'

    – ctac_
    8 hours ago



















  • Know nothing about discord but you can try with a laucher like : xterm -e sh -c 'discord'

    – ctac_
    8 hours ago

















Know nothing about discord but you can try with a laucher like : xterm -e sh -c 'discord'

– ctac_
8 hours ago





Know nothing about discord but you can try with a laucher like : xterm -e sh -c 'discord'

– ctac_
8 hours ago










0






active

oldest

votes












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f510568%2fhow-to-debug-an-xfce-launcher-which-fails-to-launch-its-app%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • 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%2funix.stackexchange.com%2fquestions%2f510568%2fhow-to-debug-an-xfce-launcher-which-fails-to-launch-its-app%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

CARDNET

Boot-repair Failure: Unable to locate package grub-common:i386

濃尾地震