[Issue]: MacOS unstable arm build is corrupt #5561

Closed
opened 2026-02-07 01:56:29 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @rasmuslos on GitHub (Mar 31, 2024).

Please describe your bug

The latest unstable arm build for macOS is not working, while the same build for amd64 works fine (through rosetta on the same device).

Bildschirmfoto 2024-03-31 um 20 40 56 The terminal on the left shows the amd64 build, the one on the right the arm one.

I ensured that the executable was not quarantined but I am pretty sure that the executable is not run correctly in the first place. Both installs are completely fresh.

Reproduction Steps

  1. Download the latest unstable Jellyfin macOS arm build
  2. Try to run it

Jellyfin Version

Unstable (master branch)

if other:

No response

Environment

- OS: MacOS 14.4.1
- Processor: M1 Pro

Jellyfin logs

`zsh: killed     ./jellyfin`

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Originally created by @rasmuslos on GitHub (Mar 31, 2024). ### Please describe your bug The latest unstable arm build for macOS is not working, while the same build for amd64 works fine (through rosetta on the same device). <img width="1611" alt="Bildschirmfoto 2024-03-31 um 20 40 56" src="https://github.com/jellyfin/jellyfin/assets/49640416/956d4e24-6a19-41db-9536-ea11d1ff2fbe"> The terminal on the left shows the amd64 build, the one on the right the arm one. I ensured that the executable was not quarantined but I am pretty sure that the executable is not run correctly in the first place. Both installs are completely fresh. ### Reproduction Steps 1. Download the latest unstable Jellyfin macOS arm build 2. Try to run it ### Jellyfin Version Unstable (master branch) ### if other: _No response_ ### Environment ```markdown - OS: MacOS 14.4.1 - Processor: M1 Pro ``` ### Jellyfin logs ```shell `zsh: killed ./jellyfin` ``` ### FFmpeg logs _No response_ ### Please attach any browser or client logs here _No response_ ### Please attach any screenshots here _No response_ ### Code of Conduct - [X] I agree to follow this project's Code of Conduct
OVERLORD added the questionsupport labels 2026-02-07 01:56:29 +03:00
Author
Owner

@jellyfin-bot commented on GitHub (Mar 31, 2024):

Hi, it seems like your issue report has the following item(s) that need to be addressed:

  • The format of the environment section has been altered from the template.
  • You have not provided a sufficient amount of logs. Please provide every line during the time of the event plus 10 lines before and after.
  • You have not provided any ffmpeg logs. They should be included if transcoding or remuxing.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

@jellyfin-bot commented on GitHub (Mar 31, 2024): Hi, it seems like your issue report has the following item(s) that need to be addressed: - The format of the environment section has been altered from the template. - You have not provided a sufficient amount of logs. Please provide every line during the time of the event *plus 10 lines before and after*. - You have not provided any ffmpeg logs. They should be included if transcoding or remuxing. This is an automated message, currently under testing. Please file an issue [here](https://github.com/jellyfin/jellyfin-triage-scripts/issues) if you encounter any problems.
Author
Owner

@gnattu commented on GitHub (Apr 1, 2024):

dotnet projects do not work with Apple's auto ad-hoc signing mechanism, you have to manually sign all binaries in the folder, only removing the quarantine flag is not enough:

xattr -rd com.apple.quarantine .
codesign -fs - --deep jellyfin

This is documented on our website: https://jellyfin.org/docs/general/testing/server/macos

@gnattu commented on GitHub (Apr 1, 2024): dotnet projects do not work with Apple's auto ad-hoc signing mechanism, you have to manually sign all binaries in the folder, only removing the quarantine flag is not enough: ``` xattr -rd com.apple.quarantine . codesign -fs - --deep jellyfin ``` This is documented on our website: https://jellyfin.org/docs/general/testing/server/macos
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#5561