Whenever I try to download a mod directly off of Nexus using MO2, I get the error; “Unable to create io-slave. Unknown protocol ‘nxm’.”
I assume this has to do with what MimeType it is pointing to. So I went to system settings, searched for File Associations, and created what MimeType it was pointing to in applications, and named it “x-scheme-handler”, added the modorganizer2-nmx-broker.sh to the application preference order and added to the filename patterns both *.nxm and nxm, and done so both separately. Even after all of that, I still get the same error.
This is my "modorganizer2-nxm-handler.desktop file.
Apparently, it seems like it is able to be found while placed on /usr/local/bin, I have no clue why it’s not able to be found on /home/usr/.local/bin/ though.
The error has evolved into;
Unknown error code 100
The program 'modorganizer2-nxm-broker.sh' was found at '/usr/local/bin/modorganizer2-nxm-broker.sh' but it is missing executable permissions.
Please send a full bug report at https://bugs.kde.org.
How do I make it so that KIO can also read and execute from /home/usr/.local/bin/ or is it that the handler is written wrong and is executing it at the wrong place?
With what we did with changing the exec and all that was all apart of the same error system which was “KIOExec”, so I don’t think it has anything to do with MO2 and that we were on the right track… I just don’t know how to do what I want to do, so I am asking people who do.
It seemed like with the command that you wrote previously, it turned off that path from being able to be selected as a choice. How do you undo that so I can apply it to home/usr/.local/bin instead?