How do I troubleshoot “Inconsistency detected: dl-lookup.c: 111” (Java Result 127) error?

Question

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 1

Downgrade to OpenJDK 8

I had the same problem in Xubuntu 18.04 with Eclipse 2018-12 (4.10.0). It was working fine, but probably some update in the system (or to OpenJDK specifically) started this problem. In addition Gradle Tasks weren't showing up in the Gradle Window.

I solved the issue removing packages: default-jre, default-jdk, default-jre-headless, default-jdk-headless, all of them are "pointing at" openjdk-11.

Then I installed packages: openjdk-8-jre, openjdk-8-jdk, openjdk-8-jre-headless and openjdk-8-jdk-headless.

Changed eclipse.ini in the vm section to: -vm /usr/lib/jvm/java-8-openjdk-amd64/bin

And now everything is working fine, and Gradle tasks are showing again. To clarify, I'm also using LibGDX.