Vortex Mod Manager doesn't boot after install

Support
1

Hello,

I have installed Vortex mod manager directly from the lutris page.

The install went smoothly and I followed the instructions to deactivate the internet, boot vortex, disable auto updates and close out. The installer said it was finished so I closed out, turned my internet back on then tried to boot vortex. It went from launching, to stop, then back to play.
I tried uninstalling and re-installing vortex which led to the same result.
Vortex had already launched so I know it knew where the file was and had to have been set up properly in some fashion.

The error log is here
https://pastebin.com/3DyyRpPe
Exit with return code 256

1 Like
2

The pastebin seems to have an issue. Here is the same error, different pastebin.
https://paste.ubuntu.com/p/pRJ3dMbBmv/

3

I have the similar issues, I’ve been trying to install Vortex all day.

I followed the instructions to disable internet access before first launch, then disable updates, close the app, re-enable internet and then after that nothing happens. For me Lutris doesn’t even show Vortex as being installed.

4

Having the same issue rn. I was able to get Vortex working on a previous install but recently it just doesnt start after initial setup. Logs show some error messages but i can’t make sense of it

Start monitoring process.
esync: up and running.

net.js:329
err = this._handle.open(fd);
^

Error: EINVAL: invalid argument, uv_pipe_open
at new Socket (net.js:329:26)
at createWritableStdioStream (internal/bootstrap/switches/is_main_thread.js:67:18)
at process.getStdout [as stdout] (internal/bootstrap/switches/is_main_thread.js:122:12)
at Object. (electron/js2c/browser_init.js:185:793)
at Object…/lib/browser/init.ts (electron/js2c/browser_init.js:185:3714)
at webpack_require (electron/js2c/browser_init.js:1:128)
at electron/js2c/browser_init.js:1:1200
at electron/js2c/browser_init.js:1:1267
at NativeModule.compileForInternalLoader (internal/bootstrap/loaders.js:277:7)
at NativeModule.compileForPublicLoader (internal/bootstrap/loaders.js:219:10) {
errno: -4071,
code: ‘EINVAL’,
syscall: ‘uv_pipe_open’
}
Monitored process exited.
Initial process has exited (return code: 256)
Exit with return code 256

Ive tried removing Vortex from Lutris and reinstalling, same thing hapens. Ive tried rebooting, reinstalling Lutris. Ive even tried keeping the internet on during install to see if that makes a difference, nope. Setup goes fine, but it will not run afterwards. I dont know what to do from here.

5

In all of my testing I was able to complete the initial installation of vortex but was unable to launch after the fact.

I have attempted to use separate vortex-setup-X.X.X.exe files with interesting results. Using the default download option for vortex-setup my logs are as follows:

Start monitoring process.
esync: up and running.

net.js:329
err = this._handle.open(fd);
^

Error: EINVAL: invalid argument, uv_pipe_open
at new Socket (net.js:329:26)
at createWritableStdioStream (internal/bootstrap/switches/is_main_thread.js:67:18)
at process.getStdout [as stdout] (internal/bootstrap/switches/is_main_thread.js:122:12)
at Object. (electron/js2c/browser_init.js:185:793)
at Object…/lib/browser/init.ts (electron/js2c/browser_init.js:185:3714)
at webpack_require (electron/js2c/browser_init.js:1:128)
at electron/js2c/browser_init.js:1:1200
at electron/js2c/browser_init.js:1:1267
at NativeModule.compileForInternalLoader (internal/bootstrap/loaders.js:277:7)
at NativeModule.compileForPublicLoader (internal/bootstrap/loaders.js:219:10) {
errno: -4071,
code: ‘EINVAL’,
syscall: ‘uv_pipe_open’
}
Monitored process exited.
Initial process has exited (return code: 256)
Exit with return code 256

Using version 1.5.11 resulted in:

[JAVASCRIPT ERROR WINDOW]

Uncaught Exception:
Error: EINVAL: invalid argument, uv_pipe_open
at new socket (node:net327:24)
at createWritableStudioStream (node:internal/bootstrap/switches/is_main_thread:72:18)
at process.getStdout [as stdout] (node:internal/bootstrap/switches/is_main_thread:123:12)
at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\colors\lib\system\supports-colors.js:40:15
at Object. (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\colors\lib\system\supports-colors.js:61:3)
at Module._compile (node:internal/modules/cjs/loader:1116:14)
at Object.Module._extensions.js (node:internal/modules/cjs/loader:1169:10)
at Module.load (node:internal/modules/cjs/loader:988:12)
at Module._load (node:internal/modules/cjs/loader:829:12)
at function.c._load (node:electron/js2c/asar_bundle:5:13331)

[LOGS WINDOW]

lutris-wrapper: Vortex Mod Manager
Started initial process 16942 from /home/gaige/.local/share/lutris/runners/wine/lutris-6.14-4-x86_64/bin/wine /home/gaige/Games/vortex-mod-manager/drive_c/Program Files/Black Tree Gaming Ltd/Vortex/Vortex.exe
Start monitoring process.
esync: up and running.

[248:0508/190540.918:ERROR:network_change_notifier_win.cc(227)] WSALookupServiceBegin failed with: 0

Using version 1.3.22 resulted in:

Start monitoring process.

net.js:314
err = this._handle.open(fd);
^

Error: EINVAL: invalid argument, uv_pipe_open
at new Socket (net.js:314:26)
at createWritableStdioStream (internal/process/stdio.js:179:18)
at process.getStdout [as stdout] (internal/process/stdio.js:28:14)
at Object. (electron/js2c/browser_init.js:5773:13)
at Object…/lib/browser/init.ts (electron/js2c/browser_init.js:5929:30)
at webpack_require (electron/js2c/browser_init.js:20:30)
at electron/js2c/browser_init.js:84:18
at electron/js2c/browser_init.js:87:10
at NativeModule.compile (internal/bootstrap/loaders.js:287:5)
at NativeModule.compileForPublicLoader (internal/bootstrap/loaders.js:222:8) {
errno: -4071,
code: ‘EINVAL’,
syscall: ‘uv_pipe_open’
}
Monitored process exited.
Initial process has exited (return code: 256)
Exit with return code 256

I am seeing this as a result of Java issues but I am unsure how to resolve the situation. All testing was done on a fresh installation of Lutris.

6

Check this:

7

Same error here.

Googling the error suggests it is a piping issue with nodeJS and is seen in some other electron apps running on linux, but I couldn’t find a fix. Vortex does start when I manually run ‘wine Vortex.exe’ in terminal, and it works fine during the setup process, so its something specific to how its started by Lutris. Sadly, running it manually used a version of wine which didn’t have .net working and I couldn’t figure that out.

I ended up just using mod organizer 2 like owohnzimmer suggested above. Though that failed at first too until I set steam to use ‘Proton Experimental’, despite the install instructions requiring Proton 6.3. (Skyrim kept crashing on menu screen with 6.3)