ollama - 💡(How to fix) Fix bug: 0.22.0 image generation working from DMG but not Homebrew with mlx response parse and mlx scanner errors [1 participants]

Below log excerpt show errors only seen with Ollama 0.22.0 installed by Homebrew, tested using both models cited in experimental announcement in Jan-2026, x/z-image-turbo and x/flux2-klein. Command execution will accept and process, within 1-2 second reach 100% and stdout will show blank new line without any error message. level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line="" level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line="" level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line="" level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line="" level=DEBUG source=server.go:331 msg="mlx response parse error" error="unexpected end of JSON input" line="" level=WARN source=server.go:135 msg=mlx-runner msg="SIGSEGV: segmentation violation" level=WARN source=server.go:135 msg=mlx-runner msg="PC=0x115423130 m=11 sigcode=2 addr=0x0" level=WARN source=server.go:135 msg=mlx-runner msg="signal arrived during cgo execution" level=WARN source=server.go:135 msg=mlx-runner msg="fault 0x0" level=ERROR source=server.go:362 msg="mlx scanner error" error="unexpected EOF"

TL;DR

The issue with Ollama 0.22.0 image generation when installed via Homebrew on macOS may be related to a JSON parsing error or a segmentation violation, suggesting a potential compatibility or configuration problem.

Guidance

• Investigate the mlx response parse error with unexpected end of JSON input to determine if there's an issue with the JSON data being processed or if it's a symptom of a larger problem.
• Examine the SIGSEGV: segmentation violation error and the subsequent warnings to identify if there's a memory-related issue or a compatibility problem with the Apple GPU or CPU.
• Compare the installation and execution environments between the DMG installation (which works) and the Homebrew installation to identify any differences that could be causing the issue.
• Consider checking the issue tracker for any updates or fixes related to the mentioned https://github.com/ollama/ollama/issues/15107, as it may be relevant to the problem at hand.

Notes

The provided log output suggests a complex issue that could be related to either a software bug, a compatibility problem with the Apple hardware, or an issue with the Homebrew installation process. Without more specific details about the environment and the exact commands used for installation, it's challenging to provide a definitive fix.

Recommendation

Apply workaround: Given the complexity and the potential for this being a compatibility or configuration issue, attempting to replicate the working environment of the DMG installation or waiting for an update that addresses the mentioned issue might be the most straightforward path forward.