-
Notifications
You must be signed in to change notification settings - Fork 33
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
Failed loading library file: jk2mvmenu #94
Comments
That's really strange. Try launching jk2mvmp like that:
|
That's very strange then. Even stranger is that I rebuilt from source and as long as I leave the final builds in the folder they were created in within the build structure, it actually runs fine. If I move them, regardless of the On the other hand, even after I move them, if I run with the options you specified above, it runs fine. I am completely baffled. It was a clean install of Linux Mint 18.1 (Ubuntu derivative), and the build environment was created specifically for this project, and for xLAva's Single-player Build. Still, if you want it, here's the output from
*** Edit: I used |
I do see one thing that's different however... In the failed instance, I see this:
Where as in the successful instance, I see this:
The only things in
Did I somehow mess something up? |
Then this is a installed build. No idea what could cause it but I see you use links for the base directory, this usually doesn't break anything on unix but still. I'd test it with a very minimalistic config with only assets in base and a portable build. |
I created an LXC container and tested with a portable build, but it doesn't like that, and I guess that's cheating (kind of):
I'll have to do it properly when I get home from work. I was thinking I might be able to get something more usable, even if it couldn't connect to a GUI, but it looks like it checks for that first. |
you dont need that, just build a portable version |
Can you explain what's wrong with .deb package? Install, run and if it doesn't launch, paste |
I'm closing the issue because of no further activity and the fact that nobody was able to reproduce it. |
I think it was a system issue on my end, but that system died and I haven't been able to replace it yet anyway. Sorry for the delay! |
I can reproduce this by dual booting 2 versions of ubuntu. older version 18 works newer version 20.04 gives me the missing jk2mvmenu. different partitions odd. 15050 files in pk3 files |
I've now encountered this bug too, Running void linux. I just built a release from source. I'll try building portable now to see if that helps. |
Just hit the same issue, Fedora 38 here.
When I try to build the Can someone shed some light on the project status and which branch/tag is actually to be used? |
Sorry for the late reply. I got a notification about this via mail, but finding it in an issue that has been closed back in 2017 was a bit more tricky. The project is still being worked on and we hope to release a new version soon. These are the open pull requests we want to finish/review/merge before the next release:
The |
Same issue here. Installed from JK2 is an old favorite my family used to play a bunch some 15 years ago and we played the Steam version for game night tonight. Myself on Mint and my brother on Windows had a bunch of issues with multi-monitor, windowing, and crashes. Another had a BSOD on Windows while playing. So here I am looking for an open source solution to prevent those issues in the future, as we did not long ago for JKDF2. |
I initially got this error by using the pre-built binaries installed by the
.deb
package that's downloadable, so I cloned the repo withGIT
and built it myself locally, and I still get this error but I don't understand why.The crashlog always says the same thing:
No errors were reporting during the build, and the configuration is exactly the same as on my other machine, which runs this fine. First I built the default
release
then I built adebug
and it's always the same thing.jk2mvmenu_amd64.so
is in the same folder asjk2mvmp
-- which was the solution when I encountered this problem on my other machine.Any other files or logs you want or need that would help?
The text was updated successfully, but these errors were encountered: