Package Details: autopsy 4.22.1-1

Git Clone URL: https://aur.archlinux.org/autopsy.git (read-only, click to copy)
Package Base: autopsy
Description: Digital forensics platform and graphical interface to The Sleuth Kit® and other digital forensic tools
Upstream URL: http://www.sleuthkit.org/autopsy/
Keywords: forensics gui java postmoterm recovery sleuthkit
Licenses: Apache-2.0
Submitter: Mikos
Maintainer: mh4ckwascut
Last Packager: mh4ckwascut
Votes: 86
Popularity: 0.44
First Submitted: 2005-09-03 19:00 (UTC)
Last Updated: 2025-04-27 12:30 (UTC)

Dependencies (7)

Required by (0)

Sources (2)

Pinned Comments

Latest Comments

1 2 3 4 5 6 .. 11 Next › Last »

stoked-security commented on 2026-01-05 14:01 (UTC) (edited on 2026-01-05 14:03 (UTC) by stoked-security)

Hi, two improvement suggestions:

1) Could the /usr/bin/autopsy symlink be replaced with a small shell script that sets JAVA_HOME to the JDK17 install directory? This way other applications could use a more modern system wide JRE/JDK version set through archlinux-java, while autopsy continues to run using JDK 17. I used the following script for testing:

#!/usr/bin/env bash
JAVA_HOME="/usr/lib/jvm/java-17-openjdk"
export PATH="$JAVA_HOME/bin:$PATH"
/usr/share/autopsy/bin/autopsy

Changing the Exec value in the .desktop file to point to this scripts works as well.

2) By adding the following line to the .desktop file the autopsy icon will show in the task switcher instead of the default:

StartupWMClass=java-lang-Thread

I hope you want to implement these changes so all could benefit.

stoked-security commented on 2025-12-10 14:58 (UTC)

Solved my own question, sleuthkit-java was compiled with a more modern version of java. Removed the package and cached builds and reinstalled with java 17 enabled. Now autopsy is running without errors.

stoked-security commented on 2025-12-10 14:47 (UTC)

I tried running autopsy with Java 17 as instructed. However, autopsy will display an error message during start as org/sleuthkit/datamodel/TskCoreException throws a class version error requiring at least version 68.0 (java 24). This problem has also been reported here: https://github.com/sleuthkit/autopsy/issues/7977

Not sure if this is something that has to be fixed upstream or has to do with the packaging for Arch?

Mario156090 commented on 2025-02-08 17:30 (UTC)

@ochiruko, you should to move to java 17 and try compile. But is very very slow.

ochiruko commented on 2024-10-08 18:24 (UTC)

Build failed for me, with an exception when building gradle. On line 3528 of build.gradle, "Process 'command 'perl'' finished with non-zero exit value 2". Aside from errno=2 indicating that something was missing, I have no idea where to go from here.

mh4ckwascut commented on 2024-02-28 15:04 (UTC)

You only have to enable java 17 for the build, you can revert it to 21 later and only use java 17 to use autopsy.

Autopsy is developed to work with java 17, they is no official support for java 21 yet.

georgerabus commented on 2024-02-26 00:40 (UTC)

@mh4ckwascut if I enable system wide jre 17 then other applications that use 21 will stop working. Btw is it possible to update the package to jre 21 or it's too much of a hustle?

mh4ckwascut commented on 2024-02-25 23:15 (UTC)

You can switch to jre 17 using the command archlinux-java, then try to reinstall from there. The build of java17-openjfx is building because java 21 is used. Otherwise you can try to build the package from a clean chroot.

georgerabus commented on 2024-02-22 17:03 (UTC) (edited on 2024-02-22 18:16 (UTC) by georgerabus)

im trying to install autospy from AUR but it has a jre17-openjdk dependecy, while jre-openjdk is already installed on my system and they are conflicting. How to solve this issue?

https://0x0.st/H51V.txt

eritquearcus commented on 2023-11-23 08:34 (UTC) (edited on 2023-11-23 08:35 (UTC) by eritquearcus)

If you stuck on loading module screen like me, check this https://sleuthkit.discourse.group/t/hangs-on-starting-modules-ubuntu-20-04/2598 (run autopsy with --nosplash once)