Processor Failed due to unexpected output

[Pairadocks]

Operating System

Linux

Version of Prism Launcher

9.4

Version of Qt

6.9.1

Description of bug

I couldn't find this issue mentioned anywhere here already, so I'm putting it in now.

Due to the zlib files on a lot of linux distros are switching to zlib-ng. This is a problem because all the the files are able to be read, but the hash value ends up being different thus causing a "Processor Failed:" error and then the modpacks won't start. Normal Minecraft still seems to work during all of this. I did manage to find a reddit thread with a workaround which is doing the command "sudo pacman -S zlib lib32-zlib" but it is annoying to need to do that. The FTB launcher gets around this new issue by adding in a way to disable the hash check. So I believe Prism should at bare minimum at least add that feature in if not some other way to fix it.

Here is a link to the reddit thread for anyone who would like it:
https://www.reddit.com/r/PrismLauncher/comments/1ifpbgp/issue_with_modpacks/

Steps to reproduce

Use a linux distro that use zlib-ng instead of zlib. I currently use CachyOS though I know that other Arch Linux and Fedora distros use zlib-ng now since the Dec 31st release

Suspected cause

zlib-ng hashes being different than zlib

This issue is unique

• I have searched the issue tracker and did not find an issue describing my bug.

[Trial97]

Go complain to forge and neoforge about this stuff
For us here is where we track this:PrismLauncher/ForgeWrapper#3
And for a short history:

• neoforge recently merged a change that added a flag for this (add a flag to control the hash checking neoforged/LegacyInstaller#43)
• on forge side, I was hit with the fact that the flag was a hack, and they only accept full implementations(in my opinion, there is not a good way to check) (add a flag to control the hash checking MinecraftForge/Installer#77)

So right now we are waiting for forge to fix it on their side.