Skip to content
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

Kali linux cannot run bin/autopsy , Library not found in jar (libtsk_jni) SleuthkitJNI: failed to load libtsk_jni #7887

Open
CatharsisCoding opened this issue Mar 20, 2024 · 8 comments

Comments

@CatharsisCoding
Copy link

Here is the error i have when i try to run bin/autopsy after i follow all the installation

┌──(maliki㉿Maliki-club)-[~/hack/autopsy-4.21.0/bin]
└─$ sudo ./autopsy
WARNING: Unknown module: javafx.base specified to --add-exports
WARNING: Unknown module: javafx.controls specified to --add-exports
WARNING: Unknown module: javafx.controls specified to --add-opens
Library not found in jar (libtsk_jni)
SleuthkitJNI: failed to load libtsk_jni

image

Fatal Error!
X
Problem with Sleuth Kit JNI. Test call failed!
Is Autopsy or Cyber Triage already running?
Details: java.lang.UnsatisfiedLinkError: 'java.lang.String org.sleuthkit.datamodel.SleuthkitJNI.getVersionNat()'
OK

image

It seem that autopsy application cannot be download in kali and but we can use the web app (i prefrere the normal app like in windows)

@CatharsisCoding CatharsisCoding changed the title Kali linux cannot run Library not found in jar (libtsk_jni) SleuthkitJNI: failed to load libtsk_jni Kali linux cannot run bin/autopsy , Library not found in jar (libtsk_jni) SleuthkitJNI: failed to load libtsk_jni Mar 20, 2024
@markmckinnon
Copy link
Contributor

Can you run the command mmls -V and report what the version of Sleuthkit is?

@mhauri
Copy link

mhauri commented Jun 8, 2024

Have the same issue: mmls -V returns: The Sleuth Kit ver 4.12.1

@ecr00012
Copy link

ecr00012 commented Jun 8, 2024

Ever find the solution to this?

@markmckinnon
Copy link
Contributor

Here are steps that I have done to uninstall/install Autopsy in a Kali VM.

mkdir autopsy-install
cd autopsy-install

sudo apt-get purge --auto-remove autopsy
sudo apt-get purge --auto-remove sleuthkit

sudo apt-get update

curl -s -O https://raw.githubusercontent.com/sleuthkit/autopsy/master/linux_macos_install_scripts/install_prereqs_ubuntu.sh
chmod 755 install_prereqs_ubuntu.sh

curl -s -O https://raw.githubusercontent.com/sleuthkit/autopsy/master/linux_macos_install_scripts/install_application.sh
chmod 755 install_application.sh

curl -L https://github.com/sleuthkit/autopsy/releases/download/autopsy-4.21.0/autopsy-4.21.0.zip -O autopsy-4.21.0.zip
curl -L https://github.com/sleuthkit/autopsy/releases/download/autopsy-4.21.0/autopsy-4.21.0.zip.asc -O autopsy-4.21.0.zip.asc
curl -L https://github.com/sleuthkit/sleuthkit/releases/download/sleuthkit-4.12.1/sleuthkit-java_4.12.1-1_amd64.deb -O sleuthkit-java_4.12.1-1_amd64.deb

Install the newest release of sleuthktit

sudo apt-get install ./sleuthkit-java_4.12.1-1_amd64.deb

Install the prereqs for Autopsy

./install_prereqs_ubuntu.sh

Run the following command to get the Java Home

java -XshowSettings:properties -version 2>&1 > /dev/null | grep 'java.home'

Set Java Home based on previous step

I suggest updating this in your profile so it will be persistent

export JAVA_HOME=

./install_application.sh -z ~/autopsy-install/autopsy-4.21.0.zip -i ~/autopsy -j $JAVA_HOME -n autopsy -v autopsy-4.21.0.zip.asc

Change to autopsy bin directory

./autopsy --nosplash

Let me know if this does or does not work for you.

@ecr00012
Copy link

ecr00012 commented Jun 11, 2024 via email

@ecr00012
Copy link

ecr00012 commented Jun 11, 2024 via email

@markmckinnon
Copy link
Contributor

What tar are you referring to. The error states the jar file cannot be found so my guess is that installing from the tar did not put the jar file in the correct place. If you install from the deb it will put the jar file in the correct place.

@ecr00012
Copy link

ecr00012 commented Jun 18, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants