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

Autopsy stalls because I cannot click the "Information" dialog #7870

Open
superclarkk opened this issue Sep 28, 2023 · 2 comments
Open

Autopsy stalls because I cannot click the "Information" dialog #7870

superclarkk opened this issue Sep 28, 2023 · 2 comments

Comments

@superclarkk
Copy link

System Environment
OS: Debian 12 (bookworm)
Autopsy: autopsy-4.21.0
SleuthKit: sleuthkit-java 4.12.1
Java: update-java-alternatives -l | grep java-1.17: java-1.17.0-openjdk-amd64 1711 /usr/lib/jvm/java-1.17.0-openjdk-amd64

Problem
When I start ./autopsy, it shows the loading graphic, which states, "Starting modules,,," at the bottom. If I hover over the application in the lower panel, I can see the preview of an "Information" dialog, that presumably requires the user to click the OK button to continue. However, there's no way to show the dialog to click the button.

The software stays like this forever. In the shell, it shows the following:

$ ./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
Temp Folder for Libraries: /tmp
SleuthkitJNI: loaded libtsk_jni
@superclarkk
Copy link
Author

After a few restarts, the software continues past the dialog. In the shell, it shows the following:

WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.netbeans.TopSecurityManager (file:/home/myuser/autopsy/autopsy-4.21.0/platform/lib/boot.jar)
WARNING: Please consider reporting this to the maintainers of org.netbeans.TopSecurityManager
WARNING: System::setSecurityManager will be removed in a future release

@superclarkk
Copy link
Author

It seems that a workaround is to click the close button on the preview for the "Information" dialog.

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

1 participant