Autopsy has released version "4.23.1". Please update this package.

The tag says "postmoterm," I think that's a typo for "postmortem?"

Doesn't seem to work:

bash -c 'JAVA_HOME=/usr/lib/jvm/java-17-openjdk PATH=$JAVA_HOME/bin:$PATH /usr/bin/autopsy'
/opt/autopsy/bin/../etc/autopsy.conf: line 18: $'\r': command not found
/opt/autopsy/bin/../etc/autopsy.conf: line 56: $'\r': command not found
/opt/autopsy/bin/../etc/autopsy.conf: line 59: $'\r': command not found
/opt/autopsy/bin/../etc/autopsy.conf: line 64: $'\r': command not found
/opt/autopsy/bin/../etc/autopsy.conf: line 67: $'\r': command not found
Detected KDE; adding awt.useSystemAAFontSettings=on
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
egrep: warning: egrep is obsolescent; using grep -E
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
java.lang.IllegalStateException: Host module FixedModule:org.openide.filesystems was enabled before, will not accept fragment FixedModule:org.openide.filesystems.compat8
        at org.netbeans.ModuleManager.attachModuleFragment(ModuleManager.java:1104)
        at org.netbeans.ModuleManager.maybeAddToEnableList(ModuleManager.java:1717)
        at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1640)
        at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1613)
        at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:290)
        at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:326)
        at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:252)
        at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:298)
        at org.netbeans.core.startup.Main.getModuleSystem(Main.java:173)
        at org.netbeans.core.startup.Main.getModuleSystem(Main.java:142)
        at org.netbeans.core.startup.Main.start(Main.java:299)
        at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:98)
        at java.base/java.lang.Thread.run(Thread.java:840)

org.netbeans.InvalidException: StandardModule:org.sleuthkit.autopsy.core jarFile: /opt/autopsy/autopsy/modules/org-sleuthkit-autopsy-core.jar: java.lang.UnsupportedClassVersionError: org/sleuthkit/datamodel/TskCoreException has been compiled by a more recent version of the Java Runtime (class file version 68.0), this version of the Java Runtime only recognizes class file versions up to 61.0

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.

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.

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?

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

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.

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.

@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?