-
-
Notifications
You must be signed in to change notification settings - Fork 334
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
[macOS] 1.10 release doesn't work #623
Comments
Same here, Jellyfin Server 10.9.1 latest is used. |
Sounds like a bad release. I checked the build logs and it did bundle a web client so I am unsure exactly what is happening, but it looks like QT Web engine is broken and not it didn't bundle the web client? Help is very appreciated since I don't have the ability to thoroughly test or troubleshoot the Mac version. |
@iwalton the issue is that rpath on QtWebEngineCore wasn't adjusted to point inside the app bundle (or maybe it simply uses absolute path, can't check atm) |
sorry, I was wrong a bit. The issue is not with QtWebEngineCore itself but rather with its embedded app QtWebEngineProcess (QtWebEngineCore.framework/Versions/5/Helpers/QtWebEngineProcess.app/Contents/MacOS/QtWebEngineProcess). Running another strange things I noticed:
|
Any eta when the new builds with this fix are released? |
Describe the bug
Client doesn't load, crash dialog appears:
To Reproduce
Simply launch the player
Expected behavior
Players opens withour errors
Desktop (please complete the following information):
Additional context
QtGui.framework is present in
/Applications/Jellyfin Media Player.app/Contents/Frameworks
but still QtWebEngineCore tries to load it from homebrew pathThe text was updated successfully, but these errors were encountered: