Vortex deploy fails with Skyrim SE - vortex.log says "EXDEV: cross-device link not permitted" #828
Comments
|
Related to #823 I think.
This is very interesting, I haven't tried modding, only whether Vortex boots up. Are you saying that modding works as expected with the Steam Linux Runtime disabled (after installation, where it is required)? As a heads up, the SLR is unfortunately required to install Vortex on SteamOS, and was thought to be required thereafter to launch Vortex at all (see #806). On Desktop, it is not needed at all. If the SLR turns out to be a problem for deploying mods, and if disabling the SLR resolves the issue for you and the user in #823, then I will note on the wiki that it should be disabled. P.S. I have very little time for Vortex, I hate it with a passion, so I don't have much time to investigate deeply. The investigation you did in your opening issue is excellent and makes life easier for anyone who might be willing to contribute to improve Vortex. |
|
A potential solution which occurred to me which STL could implement (should the SLR turn out to be the culprit):
Not sure if it would work well or not. I'll need to investigate some more. Getting users to toggle the SLR manually is a fine step in the meantime though. |
sonic2kk
added
enhancement
|
Removed the bug label, because this can to my understanding be fixed by disabling the Steam Linux Runtime, and issues modding games are not SteamTinkerLaunch issues (as long as the tool starts, anything beyond that to make mods work is an enhancement). |
Exactly; as long as the setup was done with the runtime, and later disabled, everything works.
Understandable, I have been trying to get Skyrim Together to work on Linux (entirely different can of worms), and at least Mod Organizer didn't fight me back like this, although it also didn't work with that particular mod.
Sounds good, but I'll add: it seems like Vortex can both run and install regardless of SLR, but .NET requires SLR to install. So another way would be to install .NET when preparing the Vortex prefix, with SLR ON in this step, and then install and run Vortex without SLR. Of course, I haven't looked at the code of STL much, so I don't know which option would be easiest and/or more robust. |
Great, I have a branch locally that I am working on which changes the current option to use the Steam Linux Runtime only to install Vortex. On subsequent boots, after .NET 6 is installed by Vortex (checks for the dotnet install dir in the prefix), the SLR will not be used by default. A separate checkbox has been added which allows the user to enable the Steam Linux Runtime with Vortex if they so choose. Going with the approach to allow Vortex to install .NET 6 is the lowest overhead solution, because it means I won't have to manage and bump .NET 6 versions, Vortex can handle that and to be blunt, it won't be my problem 😅 Having both of these checkboxes gives the best flexibility, where a user who might have problems with or without the SLR can toggle it however they need, with (hopefully) generally good defaults based on this issue. When I have pushed this branch, I will reply and you're free to test it (you can clone the repo and checkout the branch once it's up with
According to extensive testing done in #806, on SteamOS, the Steam Linux Runtime is required to install Vortex (and do basically anything Wine-related on SteamOS with Proton 8 and above). If you get a chance I'd be interested to know if this behaviour also happens on EndeavourOS. A user on Linux Mint using Pacstall (meaning the latest git) was able to mod without issues. However the Steam Deck does its drive mappings may indeed cause issues with the Steam Linux Runtime. |
|
Branch You can check that the SLR is not running by searching for Good luck! |
|
On the back of the many, many Vortex issues that have come in recently, I have updated the wiki to note that I really am not interested in helping users with Vortex issues any further. If it were easy, I would rip Vortex support out of STL (and may do after v14 is out), but right now it's actually easier to leave support in and hope someone will step up to try and better maintain it. Has not happened in the 3 years STL has been around, and most vocal users are no longer technical users, so I don't think it'll happen. I am very tired of Vortex at this point, and don't want anything to do with it for a long time, so even though I really appreciate the extra mile you went with your investigation before opening this issue (seriously, the amount of users that can't even fill in an issue template is insane) I will close this issue regardless of the output from your test, because I am not motivated to work on Vortex any further. If your test works and if there is also positive feedback from #823, I will merge #829 and call it a day with Vortex. My focus since taking over has and always will be on the non-modding side of STL, I am much more interested in its use as a command-line utility and a tool to configure various neat launch options for games, as well as One-Time Run which I really get a kick out of. I love MO2 and try to support it but even then it's a bit dicey, and even on Windows I have never liked Vortex, so my interest in using it with STL is virtually 0 nevermind providing support for it. Good luck with your tests, and I hope you have a better day than the day I've had today :-) |
|
Thanks for your help, and I understand completely; I first tried to install mods with Mod Organizer 2, which works right now, but the particular mod I am trying to get working (Skyrim Together) doesn't start, I think because of MO2's virtual filesystem in Wine. So, I tried Vortex again, dug into the logs, found that issue, and faced a stone wall; it was by pure change, while looking at older issues, that I decided to try to disable SLR. It was frustrating, and it was only one error; if you've been fighting it for a while, then dropping it completely in the future makes sense. I will test the branch today, and see how it goes, but don't feel bad about dropping support: seems like there are other approaches now, namely @pikdum's new WIP vortex-linux project, so if they're cool with it, it might make more sense to have people interested in modding redirected there. |
|
I have just tested it on Steam Deck, and the branch There was an issue where I installed Vortex with this branch, started it while keeping |
|
I have seen Pikdum's attempts to get Vortex to run on Linux, but users seem to come here when it doesn't work without actually trying to contribute to either project, so I wish them luck because dealing with non-technical users is exhausting 😅 If they can carry that torch, so be it. I would prefer to have someone attempt to contribute to STL's Vortex support. In fact, I would rather have more community around STL, but no one wants to contribute. That unfortunately mostly makes it my project instead of a community-driven project like I would hope for (previous maintainer had the same issues, it didn't help their motivation at all).
This sounds like #823, but I haven't been able to replicate on my Arch PC.
NXM link handling breaks intermittently; I always recommend installing mods manually. If you must use one-click installs, using collections inside of the Vortex UI seems to work (according to #825). I appreciate the testing and detailing how you went about testing especially too. I will merge that branch today. |
I see; it kind of makes sense, as in my experience the cross-section of "gamers" and technically-inclined users is not that big. Gaming as an industry is too large for that. I might be inclined to contribute in the future, since I certainly will keep using my Steam Deck, but this summer I'm in the middle of a cross-Europe move, so yeah 😅
I'm a developer by trade, so I know how hard these things can be 😉 I still haven't managed to have Skyrim Together work on my machine, so if I suspect STL has something to do with it (not clear right now), I will certainly let you know, maybe even do a PR if I can. |
Unfortunately true, even though STL is a tool for technical users, I have not yet been able to get that message across (though usage has dived off a cliff from the traffic, so maybe the message is finally getting out!) Out of interest, is the SLR running (i.e. are there any I suspect it is running in the SLR, because if I recall, we use the The strange thing is why it only fails on SteamOS, there must be something... odd going on there, maybe it has more trouble creating links or something. I am honestly not too sure :-)
Heh, my day job is software too 😉
Do report back, if there are any non-intrusive environment variables STL can set or something I could do that. And do feel free to open PRs whenever you like, or if you know someone willing, let them know too. Managing STL mostly alone and working on features I don't even use is tough :-) Good luck with your modding. I will keep this issue and #823 (or open a separate issue altogether if the issue runs deep) to figure out why the vortcmd is hanging. |
Now that you say that, I remember SLR running when Still, I tested again both on EndeavourOS and Steam Deck, on latest |
Ah sorry, I thought you had said it got stuck. I have some changes locally that I will probably push straight to master (because I'm daring today) which only uses the SLR when installing Vortex and when starting it (so it won't run for Feel free to test that it doesn't cause a regression when I push. I would like to get both of these issues resolved ideally :-) And fwiw, vortcmd doesn't hang on my PC either. I run a vanilla Arch install which I've had for about 5 years now, so not too far off endeavourOS (I actually wanted to use Endeavour but chose Arch). I haven't tried on my Steam Deck but have only gotten the one report of vortcmd hanging. Though I don't look up issues external to the issue tracker for my own sanity. |
|
Change was pushed in fb6201f. |
I did say it got stuck, but I'm not really sure when/how; it's inconsistent. At the very least, on EndeavourOS the latest |
|
Happy to hear it, if it's okay with you then I think we can close this issue as the original issue is solved, and there are no regressions. Please re-open or open a new issue if the problem persists, whichever you think makes the most sense :-) Thanks and good luck! |
|
One last, unrelated thing (I could create an issue for it): I was looking to create a While doing that, I decided to These are minor errors, as the desktop entry still works; but the fix was to change This is on EndeavourOS, so I'm not 100% sure if all distros will have the same categories by default; and it's a nitpick anyway. |
|
This is interesting. Did changing this key fix anything? In other words, were the errors of any substance? I can push a fix for this, or if you'd like you could create a PR if/when you're free to do so (no pressure, I just like giving users who spot issues the opportunity to fix them if they're able and willing 😄 I was afforded this opportunity myself when I got started and try to give others the same) |
System Information
Issue Description
I had a working Vortex install, which broke after a recent update; after this was fixed on SteamTinkerLaunch, and tinkering with options, Vortex now works.
After further configuring Vortex (logging in on my Nexus account, setting Vortex profiles), and trying to deploy, Vortex shows non-descriptive error messages, and none of the hardlinks are created.
Looking around on my own, I found where Vortex stores logs (attached below): there are a lot of errors, at least one per hardlink, all of them with the message
EXDEV: cross-device link not permitted.I managed to fix this locally on my Steam Deck, by installing Vortex normally, shut it down, configure SteamTinkerLaunch to not use Steam Runtime with Vortex, and then running Vortex again.
Could there be some permissions issue when trying to hardlink with Steam Runtime?
Things I have tried, deleting the
vortexfolder completely between tries:Logs
Vortex logs can be found in
~/.config/steamtinkerlaunch/vortex/compatdata/pfx/drive_c/users/steamuser/AppData/Roaming/Vortex/.Each is hundreds of lines, and bigger than the allowed Pastebin free limit; I will upload it if needed, but the only thing that jumped to me was this line (repeated once per mod file):
Last
steamtinkerlaunch.log, after reproducing the issue:The text was updated successfully, but these errors were encountered: