Linux user from about two months, I switched from Windows specifically for Linux’s freedom, and now I’m stuck with this bs of a warning when trying to run Outer Wilds through the Outer Wilds Mod Manager for Linux, because the .exe I’m trying to run is not from Steam.
How do I either bypass it entirely forever and ever without ever seeing it again, or switch to Hyprland easily so that I can forget about KDE’s bs once and for all? 
I have never seen that message. Please provide more context.
I tried to run Outer Wilds with the Linux mod manager for it, and that error message from KIO pops up, which doesn’t happen if you give the Mod Manager a Steam installation of Outer Wilds. In order for my friend to use Outer Wilds from my Steam library, I had to get the Epic Games version, which I just have as an Outer Wilds folder in my Games folder in my home directory.
My issue is the fact that such a warning even exists; why should KDE decide what I can or cannot run? The mere idea of this infuriates me beyond any limit.
Please let me know if you need any more context, I’d be happy to help the community help me with this issue. It’s actually frustrating beyond any description I could give, since there’s seemingly no way to bypass this in my context, where it’s an app running the game and the commands it uses to do so aren’t available.
We don’t know what “Outer Wilds with the Linux mod manager” is, so you need to provide more details on how exactly you are trying to launch it.
As an example: my mikrotik router has an exe application which I need to use in order to configure it. So I have created a menu ite for that which is actually instructs wine (which I have as flatpak in my system) to run this executable. Apparently it runs as expected.
running windows .exe in linux under wine is a different setup than using steam’s proton (they both use wine, but set up as separate containers).
so if you want your mod .exe to “see” you steam game, then you need to either run it from steam, or manually copy the files of your own wine container into the appropriate places in the steam directory structure.
with greater freedom comes greater responsibility.
Sorry, you’re right, Outer Wilds Mod Manager is a mod manager and mod installer for the game Outer Wilds.
Its purpose is to make it easy to install mods for the game, but to do so it needs an installation of the game.
I get the error when pressing the “Run Game” button, after a few logs of information in a log console. I’m not sure why I’m encountering this error only with a non-Steam installation of the game, but from speculation, it might be that the mod manager isn’t running Wine when it should.
I’ll file a bug report for this in their repo, but the original issue still persists; there is no way to bypass the warning when the context doesn’t allow for a .desktop entry or running from the terminal, because I don’t have the command that the Mod Manager program is running when attempting to open the game. It’d be nice if there was an option to disable the warning altogether.
Let me know if there’s a need for any more information, and sorry for the frustrated tone of voice I used originally; after sleeping on it, I’m a bit more composed about the issue.
Also, would there be any way of intercepting the command that the Mod Manager, or any program really, is trying to run when opening the game? If there is, that would make a lot of things easier on my system.
So apparently it’s that mod manager which tries to launch an executable (and not you clicking something in dolphin or some shortcut for example) and something is giving you that message. The message you are getting might be related to dolphin according to “internet’s wisdom” but you might want to ask to some place related to that mod manager.
What I get is:
You tried to run a .exe file using the Linux Mod Manager (LMM) and got the error message.
Firstly, the error message you are getting is most probably not a KDE message. The message would have been created by LMM and maybe sent to DBus, which then caused KDE to display the message.
Your context is most probably LMM itself and maybe also Wine. You might want to look for a solution/answer discussing in related forums.
I feel like it might have something to do with your Wine configuration.
Hiya, thanks for the reply.
The issue is most definitely with KDE’s Input / Output library. It’s not the Mod Manager’s message, but a behavior of KIO caused by the fact that the LMM is trying to run the .exe without Wine.
I ended up solving that issue by running the Mod Manager, then trying to run the game, and by leaving the logs window open and running the game through Wine got the LMM to hook to the game.
The issue at root is still not solved though; how do I execute something that KIO doesn’t want me to execute when I can’t use the terminal or a .desktop entry? That’s the core issue I’d like an answer or resolution for, but I believe it might not ever happen, as to some the security risks just outweigh the convenience that a bypass option would give.
Thanks for your contribution jinliu. Unfortunately, this has nothing to do with Dolphin, as no file manager is even involved.
