I have to seek out this forum for I problem I have. I couldn't find a topic with the same issue yet.
Problem:
Deskop shortcuts are generally untrusted. If I try to launch it, a message pops up telling me to right click on the shortcut and then click "Enable "allow Launching"
The problem is, when I right click on the icon, I do not see that option.
However, may it be a previous installation or not, I do remember seeing that option at some point.
Question now is what am I doing wrong or is my OS already broken?
You need to select 'Eigenschaften' (Properties). When that opens, select 'Berechtigungen' (Permissions) tab and check the box that allows the shortcut to be executable.
But okay, because of Your Shortcut: Was it automatically created or did You created it manually? I find it a bit weird that it is a .desktop File directly on the Desktop.
This is an issue when using Xorg, but not on Wayland. The only alternative that I'm aware of is to set a delay, and open the context menu. This does require using a separate utility, however, as the default screenshot that is built into the Gnome shell doesn't support that. But anyway, a topic for another day.
Hey there, the Allow Launching will not show up in some instances, such as a bad command on the Exec line in the .desktop file. Once you fix it, the Allow Launching will show. Not sure that's your issue but worth double checking.
jim@jim-X570-AORUS-ELITE:~/Schreibtisch$ ls -l $HOME/Schreibtisch/Baldur*
-rwxrwxr-x 1 jim jim 179 Nov 19 07:02 "/home/jim/Schreibtisch/Baldur's Gate 3.desktop"
jim@jim-X570-AORUS-ELITE:~/Schreibtisch$ cat $HOME/Schreibtisch/Baldur*
[Desktop Entry]
Name=Baldur's Gate 3
Comment=Play this game on Steam
Exec=steam steam://rungameid/1086940
Icon=steam_icon_1086940
Terminal=false
Type=Application
Categories=Game;
Shortcut was created by Steam via the option to create a desktop shortcut after installing.
@j_luz is right on the money. If you installed Steam through the Software store, the only package format available is Flatpak. This means that the Exec line inside the .desktop file needs to be adjusted:
[Desktop Entry]
Name=Baldur's Gate 3
Comment=Play this game on Steam
- Exec=steam steam://rungameid/1086940
+ Exec=flatpak run com.valvesoftware.Steam steam://rungameid/1086940
Icon=steam_icon_1086940
Terminal=false
Type=Application
Categories=Game;
You can obtain the exact identifier for a Flatpak package by running flatpak list:
By the way, I just found that what actually controls this "Allow launching" setting is a field in the metadata of the file itself. This can be queried with:
gio info "Baldur's Gate 3.desktop" | grep trusted
and changed with:
gio set "Baldur\'s\ Gate\ 3.desktop" metadata::trusted true
Although it will still error out if you don't point the Exec line to the right location; in this case, the Flatpak executable.
I do honestly thing there is something broken on my OS, it's not only the steam games, even when I go into the start menu and put stuff from there directly on the desktop I also don't get the "Allow Launch" option...
Now save it. Now rename it: test.desktop
Now right click Properties/Permissions and check the box Allow to execute and then close the dialogue. Now right click it. If you do not now see an Allow Launching, yes your computer is broken.
Welp, I guess I somehow mangled my OS, yet again...
Allow to execute still doesn't show up.
From here on, I guess I move on to try Fedora now. Zorins lack of HDR support also as shown as a bit of a dealbreaker recently. It's a bit of a shame, Zorin really looked like it could be the distro for me.
Maybe I come back to this. In case a fresh install of Zorin fixes it I will make sure to post it here.
Alright, one last reply. After a little detour I realized I really don't like the KDE environment and went back to Zorin. That fresh install also solved the issue it seems, the allow start is back now.
Would be good to know how I nuked that the last time to know what not to do, but we'll never find out what caused it to bug out, I guess.
Again, thanks for the help.
PS: I actually deleted windows by now, since it acted up ever since installing Linux as a second OS. Maybe I try installing it in a VM for compatibility reasons, who knows.
