如何解决“检测到不一致：dl-lookup.c：111”（Java 结果 127）错误？

Question

I'm currently trying to build a Java project using Maven for a game I'm working on.

I think I'm using Java 8 OpenJDK (1.8.0_211) on a Ubuntu 18.04 LTS distribution.

The related question debugging ld, "Inconsistency detected by ld.so" was not able to help me. The Java Error Code 127 suggests that a resource cannot be found on my CLASSPATH (?)

The error, formatted for readability:

[java] Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: 
    Assertion `version->filename == NULL || 
    ! _dl_name_match_p (version->filename, map)' failed!
[java] Java Result: 127

Answer 1

I'm currently trying to build a Java project using Maven for a game I'm working on.

A recent push to our repository by another user has broken the build for me, but not other users.

No changes have been made the to Pom.xml in recent builds and my Java environment has remained consistent.

I'm using Java 8 OpenJDK (1.8.0_211) on a Ubuntu 18.04 LTS distribution.

The maven repository is able to compile successfully, but when I try to execute the code using our predetermined (mvn integration-test -Pdesktop) build I receive a Build Success, some errors and no application launch.

I've looked on Linux forums, but have been unable to find similar cases.

Normal Maven Debug options have not provided any initial indication of the problem that I recognise.

I've looked at several Stack Overflow questions including debugging ld, "Inconsistency detected by ld.so" but am unsure where to begin with the comments suggested approaches and if this is viable for my case.

I've looked at the Java Error Code 127, which suggests that a resource cannot be found on my CLASSPATH. Is this correct and how do I identify the missing resource on what seems to be a successful build?

The error is as follows.

 [java] Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: Assertion `version->filename == NULL || ! _dl_name_match_p (version->filename, map)' failed!
[java] Java Result: 127

On success, I'm expecting the build to report a success and to launch the Game. On failure, I had expected the build to report a failure, but instead I'm seeing a build success without the launch of the LibGDX application.

The build is currently running for users on other platforms.

Answer 2

Switch libGDX from lwjgl to lwjgl3

I had the same issue as you with OpenJDK 11 / Java 11 ( openjdk 11.0.10 2021-01-19 ). What fixed it was switching to lwjgl3 everywhere, which incidentally also fixed some other issues for me ! (whole screen going black when I exit the app, mouse cursor capture only partially working, etc)

In build.gradle change the first into the second block:

api "com.badlogicgames.gdx:gdx-backend-lwjgl:$gdxVersion"

api "com.badlogicgames.gdx:gdx-backend-lwjgl3:$gdxVersion"

Also adjust your imports (eg in the DesktopLauncher class):

import com.badlogic.gdx.backends.lwjgl.LwjglApplication;
import com.badlogic.gdx.backends.lwjgl.LwjglApplicationConfiguration;

import com.badlogic.gdx.backends.lwjgl3.Lwjgl3Application;
import com.badlogic.gdx.backends.lwjgl3.Lwjgl3ApplicationConfiguration;

lwjgl3 should be almost entirely compatible, in my case I just needed to update the config:

LwjglApplicationConfiguration config = new LwjglApplicationConfiguration();
config.samples = 8;
config.height = 720;
config.width = 1280;
config.vSyncEnabled = true;
new LwjglApplication(new RangeAnxietyGame(), config);

Lwjgl3ApplicationConfiguration config = new Lwjgl3ApplicationConfiguration();
config.setBackBufferConfig(8, 8, 8, 8, 16, 0, 8);
config.setWindowedMode(1280, 720);
config.useVsync(true);
new Lwjgl3Application(new RangeAnxietyGame(), config);

Answer 3

I'm currently trying to build a Java project using Maven for a game I'm working on.

A recent push to our repository by another user has broken the build for me, but not other users.

No changes have been made the to Pom.xml in recent builds and my Java environment has remained consistent.

I'm using Java 8 OpenJDK (1.8.0_211) on a Ubuntu 18.04 LTS distribution.

The maven repository is able to compile successfully, but when I try to execute the code using our predetermined (mvn integration-test -Pdesktop) build I receive a Build Success, some errors and no application launch.

I've looked on Linux forums, but have been unable to find similar cases.

Normal Maven Debug options have not provided any initial indication of the problem that I recognise.

I've looked at several Stack Overflow questions including debugging ld, "Inconsistency detected by ld.so" but am unsure where to begin with the comments suggested approaches and if this is viable for my case.

I've looked at the Java Error Code 127, which suggests that a resource cannot be found on my CLASSPATH. Is this correct and how do I identify the missing resource on what seems to be a successful build?

The error is as follows.

 [java] Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: Assertion `version->filename == NULL || ! _dl_name_match_p (version->filename, map)' failed!
[java] Java Result: 127

On success, I'm expecting the build to report a success and to launch the Game. On failure, I had expected the build to report a failure, but instead I'm seeing a build success without the launch of the LibGDX application.

The build is currently running for users on other platforms.