Latest Log
Latest Log
Latest Log
I/jrelog (13597): dlopen libjvm.so failed: dlopen failed: library "libjvm.so" not
found
I/jrelog (13597): dlopen
/data/user/0/net.kdt.pojavlaunch/runtimes/Internal-17/lib/server/libjvm.so success
2023-09-12 17:03:33,180 main ERROR appender Console has no parameter that matches
element Policies
[17:03:36] [Render thread/INFO]: Setting user: shull
Registered forkAndExec
[17:03:55] [Render thread/INFO]: [STDERR]: [LWJGL] Failed to load a library.
Possible solutions:
a) Add the directory that contains the shared library to -Djava.library.path
or -Dorg.lwjgl.librarypath.
b) Add the JAR that contains the shared library to the classpath.
[17:03:55] [Render thread/INFO]: [STDERR]: [LWJGL] Enable debug mode with -
Dorg.lwjgl.util.Debug=true for better diagnostics.
[17:03:55] [Render thread/INFO]: [STDERR]: [LWJGL] Enable the SharedLibraryLoader
debug mode with -Dorg.lwjgl.util.DebugLoader=true for better diagnostics.
[17:03:56] [Render thread/INFO]: Backend library: LWJGL version 3.2.3 SNAPSHOT
EGLBridge: Binding to OpenGL ES
[17:04:05] [Render thread/WARN]: ERROR : Couldn't load Narrator library : Unable to
load library 'fliteWrapper': Native library (linux-aarch64/libfliteWrapper.so) not
found in resource path ([])
[17:04:05] [Render thread/INFO]: Reloading ResourceManager: Default
I/LIBGL (13597): version string: (null)
This means that either the device shut down, logd crashed, or this instance of
logcat was unable to read log
messages as quickly as they were being produced.
If you have enabled significant logging, look into using the -G option to increase
log buffer sizes.
--------- beginning of main
This means that either the device shut down, logd crashed, or this instance of
logcat was unable to read log
messages as quickly as they were being produced.
If you have enabled significant logging, look into using the -G option to increase
log buffer sizes.
This means that either the device shut down, logd crashed, or this instance of
logcat was unable to read log
messages as quickly as they were being produced.
If you have enabled significant logging, look into using the -G option to increase
log buffer sizes.
This means that either the device shut down, logd crashed, or this instance of
logcat was unable to read log
messages as quickly as they were being produced.
If you have enabled significant logging, look into using the -G option to increase
log buffer sizes.