-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NXM downloads don't work with Flatpaks #317
Comments
It is not MO2 that gives you the error but modorganizer2-linux-installer (kind of). If you are running flatpak version of protontricks, try switching to pipx version. It helped me. I had same problem (or rather symptom) as you. In my case it was caused by "modorganizer2-nxm-broker.sh" script calling protontricks-launch, which is not a part of flatpak version and therefore was not on my system. I tried to rewrite the script myself to get it working with flatpak version of protontricks, but I was defeated by flatpak's handling of encapsulation. I recognized my failure, installed protontricks via pipx and let my hatred towards flatpaks/snaps grow stronger. |
Your fix worked like a charm, thanks man. I was at my wit's end. |
Uninstalling the protontricks flatpak, removing the alias line from my |
I seem to get similar problem after I updated protontricks, however it works if you hit the download button when MO2 is not running, then it starts up and the download is working, but if I try to download something more I i'm getting an en error, have tried to re-install MO2, but hasn't helped. |
Probably related: Installing protontricks-git fixed the issue for me |
Same issue, installing protontricks-git from AUR fixed it for me too |
I'll improve the readme to include better instructions for Flatpak users as soon as I can. Perhaps the system requirement checks can also be improved to warn users of potential incompatibilities. |
pipx works for me too, but I have same problem as @Osced86 , I can't download with MO2 from Nexus if it's open already, unlucky Linux still such mess |
@kylecarow |
Just to give a quick update on this issue: there is no way to fully utilize the NXM links functionality when Flatpaks are involved. As far as I can tell, there is no way to make the necessary inter-process communication work because of the Flatpak security design. If that feature is important for you, don't use Flatpaks. |
So is there a way to have adequate Linux setup for gaming? For example Fallout: New Vegas and MO2 with working links all the time, can we have setup with auto updates or it's cringe for Linux devs to create something that fully working? |
As I mentioned here, by editing the
is it possible to use the NXM Handler with flatpaks |
This works perfectly for New Vegas as well.
As a question for proton-knowledgable users. Isn't MO2 using proton 8.0 now? @Martan404's |
Hi, I made a makeshift solution for Flatpak users. It's a bit more involved, but if one decided to use Linux, editing .sh files and taking API keys shouldn't be beyond them. For Steam Deck buyers, sorry, you signed up for this, like it or not. https://gist.github.com/aki-hp/27dbcd38f55b68e21d2edd5b5a46ebc5 Replace ~/.local/share/modorganizer2/modorganizer2-nxm-broker.sh with this one, and put your Personal Nexus API Key in nexus_apikey, on line 4. At the very least, it should provide you with seamless NXM download for multiple games. @Martan404 and @metalbass 's solution was actually very nice, but sadly I couldn't make it work for multiple games. Limitations as of now:
Limitation always:
I hope this helps someone. EDIT : Tested with Steam Deck, and added "progress bar". In its current state it's not working properly yet (the progress bar is not moving, but the pop-up will stay until the download is finished), but I might be able to throw a fix in a near future. |
This is very nice and works. Thank you very much. I have only had to change the proton path to 8.0 there, because that's what I use for Skyrim. Now if someone could please explain to me, how do I install "protontricks-git" "from AUR"? or whatever protontricks that is not a flatpack? Google leads me to here: https://aur.archlinux.org/packages/protontricks-git, but how do I install that? I tried (Just in case it's not clear, I'm on Steam Deck) |
Unfortunately there is no easy and reliable way to install AUR packages on to the Steam Deck. If you want to install system packages you need to enter the command But why can you not use the flatpak version of Protontricks? If the flatpak is not working then try to exit the Steam client fully before opening Protontricks Edit: On my desktop Arch system I prefer to use paru and this is how I install it
|
Desktop entry helped to resolve the issue, it raises the question why the system didn't generate it in that format from the beginning... |
@StellarHarbour The way it usually sets it up allows for managing multiple games automatically. I don't think that version can, it's set to a single game. |
@andersmmg Are you saying it can't be improved to work with every game? |
Hey there, First of all thanks for trying to help all of us :) |
Sorry, I just got the time to reply. Was there any error pop-up, or was it a silent error? I found an error caused by executing MO2 directly instead of using the forwarder, so I wanted to make sure about your execution condition. |
Hi and thanks for the reply, it is a fully silent error. I tried launching it through steam, and also by using a nexus mod link (Which launches it and does the first download but not others) |
This works great, it seems the issue is mostly one of paths included in this .desktop file. Mine is as follows for fallout 4, for future google travelers: [Desktop Entry] Exec=bash -c 'env "STEAM_COMPAT_CLIENT_INSTALL_PATH=/home/SR/.var/app/com.valvesoftware.Steam/.local/share/Steam" "STEAM_COMPAT_DATA_PATH=/blaze/SteamLibrary/steamapps/compatdata/377160" "/home/SR/.var/app/com.valvesoftware.Steam/data/Steam/compatibilitytools.d/GE-Proton8-32/proton" run "/home/SR/Games/mod-organizer-2-fallout4/modorganizer2/nxmhandler.exe" "%u"' Name=Mod Organizer 2 NXM Handler |
EDIT: While the below approach worked for me, you're probably better off using nix to install protontricks instead. I didn't know about nix until recently.
@Martan404 This isn't entirely correct, I modified the steps @TaPO4eg3D suggested in #425 and got the standard nxm handler working using rwfus to allow installation of protontricks-git from AUR without disabling read-only mode Beware rwfus can brick your system if you try to do a general update of all packages using pacman, read the warnings on the rwfus github page . However I believe it is safer than turning off read-only mode and it should survive an OS update. I may be pushing it installing base-devel. While I think it should be fine, I haven't had a steamOS update yet, so do the below at your own risk:
|
Adding what worked for me, combining a couple of the above snippets, to get MO2 launching on a Steam Deck to manage Fallout 4 using the flatpak Protontricks. There's nothing truly new here, but the comment that mentioned Fallout 4 had some odd pathing.
NOTES:
|
I tried this on Mint and it didnt work :/ |
Speaking up to say that a modified version of this is working seemingly perfectly for me on Linux Mint 21.3 - I just had to change Also, this seems to work for me with both the Flatpak version and the Mint system package version of Protontricks, for the record. For other Mint users like @Rain-Gayming, setting
This is set up for use with Fallout 4 and Proton 9.0 - see the instructions in metalbass' post for changing the steam app id and MO2 installation directory. To change the proton version you're using just open |
until you have a minor change to the system python version and it breaks everything pipx installed :) |
OK .. using the info that others have posted for the .desktop file, this is what I did for Norbara 40 and its default setup (for Starfield):
There is absolutely NO TECHNICAL REASON why the modorganizer2-nxm-broker.sh can't be updated to provide the proper variable information to make this happen in both flatpak and system installs. All the variables you need you can get from variable files in compatdata directory and in the MO2 directory. It CAN be done from flatpak pythontricks .. and even from flatpak browser installs. you just need the proper paths. The config_info file from the /steamapps/compatdata/1716740 tells you which python you are using, you can look it up .. you know where your MO2 is installed. The info is all there. |
These are the changes that worked for me on Fedora 41 KDE.
|
When trying to download mods via NXM links on nexus MO2 will give me the error "failed to start download".
i have tested this on a fresh install of SkyrimSE/AE.
The text was updated successfully, but these errors were encountered: