I have a loader application pertains to an application which is needed to run first to launch the main jar program.
If the program was launched through terminal as java -jar jarfile.jar, it works fine.
sequence goes to loader.jar runs , and which run is clicked in the loader, main program launches…
now I created a desktop file to have it launched in that file,
loader opens but when run is clicked from the loader, it doesnt works.
Perhaps try and compare when KDE creates a desktop file:
Right click the Plasma Desktop and select > “Create New” > “Link to Application”
Click the “Application” tab and enter the command
On the “Application” tab click “Advanced Options” and check “Run in Terminal”
Click the Permissions tab and click “Is executable”
You can always right click the desktop icon and select “Properties”.
View this file in $HOME/Desktop to your file, not only the contents but the permissions.
Just move this file as needed.
Yes sir, tried it. (after a ton of googling stacksoverflow, qoura., and some random sites)I’ve been working for these desktop config for hours and finally I solved it. I got it working by making an sh file to the .local/bin as app.sh and then specifying the exact path to the loader and the main app.
By the way I found the solution when Error: Unable to access jarfile by having the terminal open during the launch.
it freaking works after all, thanks yall.
Im still creeping out here migrating from Windows to linux. Windows just making me crazy due to lag issues even after removing bloatwares…
I just found what Aalacarte was so It’ll be a lesson for me as well, just saving this because someone might stumble on this the same issue,
I hear you on this point, but Plasma will make it executable. I created the desktop file using the above procedure. I did not explicitly make it executable, but when I viewed the file in the Desktop directory execute permission was set. I removed the permission and when I clicked the desktop file on the Desktop I got a prompt, “This will start the program”. I clicked “Continue”, checked the file, and it was executable again.
So I moved the desktop file to another directory (make sure there wasn’t anything “special” with Desktop), double-clicked the .desktop file in Dolphin and it ran. I then removed the execute permission, ran it, and when I went back to look at the desktop file the execute permission was set.
Of the 134 files in /usr/share/applications, 68 or ~51% are executable find /usr/share/applications -type f -perm -a=x|wc -l find /usr/share/applications -type f ! -perm -a=x|wc -l
If I executed the .desktop file using xdg-open, it indeed did not have to be executable
I see - that is new to me - this must be something KDE specific then because it is not required by the specification.
I am using Openbox and all launchers in the applications folder is not executable - that is with a single exception - which I believe is installed with the timeshift package.
It seems this is some sort of pseudo security. The desktop file doesn’t have to be executable. When it is not, the user will be prompted if executed from the Desktop or via the Desktop’s file manager (Dolphin, Thunar).
xdg-open doesn’t care because it knows to look inside of the .desktop file.
So on any system, at least KDE and XFCE, there is going to be a mixture of desktop files that are executable and not executable.
I looked on XFCE and there are only two desktop files that are executable in /usr/share/applications and they are both KDE Plasma apps.
I just looked over my local set of shortcuts - they are all executable - I will have to see why.
One thought is because it is possible to mark them trusted by the app installing it.
I think the pcmanfm does something different - default asking (Setting an option *Don’t ask options on launch executable file` remove the prompt) but not changing exec bit.
Changing to non exec - does change anything - they are launched anyway.
Yes sir that’s right, its in the home directory. I am just starting to grasp what with the linux environment and hey , community here is great. Now my only problem was with my iwlwifi driver not sure why its doesnt connect even it did not came from hibernation. which is quite weird adn contradicts the stated bugs of iwlwifi to Centrino 6502 card. Thanks a lot.