Autopsy Starts and hangs while starting modules

[swalker6663]

So I have everything loaded and all the many steps met however when it starts I get the splash screen but nothing else happens. ive scoured the internet but I cannot find any similar results. PLEASE HELP.

OS- Parrot
Running on both a virtual box OS and the same results on a dedicated machine with a full Parrot OS

[jknyght9]

Try running it with the --nosplash argument. You can view the help by running autopsy --help. I got it to work temporarily.

[swalker6663]

So you’re says no run ./autopsy —nosplash

…

On Thu, May 20, 2021 at 10:23 AM Jake ***@***.***> wrote: Try running it with the --nosplash argument. You can view the help by running autopsy --help. I got it to work temporarily. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6980 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR633FMXDFFI5475BACDHIDTOUZRVANCNFSM45DPNI2A> .

[jknyght9]

I dont know why it is hanging, but when I ran autopsy --nosplash the GUI came up and I was ready to work a case. Looks like there is a bug in either the splash screen or the module loader for 4.18 in Linux.

[swalker6663]

I dont know why it is hanging, but when I ran autopsy --nosplash the GUI came up and I was ready to work a case. Looks like there is a bug in either the splash screen or the module loader for 4.18 in Linux.

It worked the issue is that there is a confirmation screen behind the splash when it starts that you cannot get too. Thank you for your help!! SOOOOOOOO many hours wasted for such a simple and undocumented problem.

[mh4ckt3mh4ckt1c4s]

Hello, any news for a fix ? I'm still getting this on the latest version, built from source. As I'm running it with ant run I can't / don't know how to use the --nosplash bypass. I'm on Archlinux with i3.

[swalker6663]

Yes there is a window hiding behind the splash picture once you click ok everything worked.

…

On Wed, Mar 16, 2022 at 4:36 AM mh4ckt3mh4ckt1c4s ***@***.***> wrote: Hello, any news for a fix ? I'm still getting this on the latest version, built from source. As I'm running it with ant run I can't / don't know how to use the --nosplash bypass. I'm on Archlinux with i3. — Reply to this email directly, view it on GitHub <#6980 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR633FMML3QTTUBGKHUB65TVAG2T3ANCNFSM45DPNI2A> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[GregoriousTheBrave]

Hello, any news for a fix ? I'm still getting this on the latest version, built from source. As I'm running it with ant run I can't / don't know how to use the --nosplash bypass. I'm on Archlinux with i3.

As a workaround, I managed to get in by using alt-tab to make the splash screen the active window, then pressing Alt-F4 to presumably close the hidden dialog box.

[mh4ckt3mh4ckt1c4s]

As a workaround, I managed to get in by using alt-tab to make the splash screen the active window, then pressing Alt-F4 to presumably close the hidden dialog box.

Thanks for your answer. Thing is, using i3 doesn't allow me to do that. I'm stuck on the splash image no matter what, and it doesn't seem to be a dialog box or I can't access it with i3...

[dominikborkowski]

This issue continues to appear in 4.19.2. What exactly is that pop-up window setting? We'd like to be able to have a silent installer, but as it stands the first execution results in this problem.

In our case we use XFCE, and there is no indication there is another window.

[dominikborkowski]

Side note, here's the window in question, that's never seen due to the splash screen:

[N3ar]

This spash screen issue is still relevant on Ubuntu 22.04 LTS as of Jan 2025.