Skip to content
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

Closed
kambala-decapitator opened this issue May 15, 2024 · 7 comments · Fixed by #628
Closed

[macOS] 1.10 release doesn't work #623

kambala-decapitator opened this issue May 15, 2024 · 7 comments · Fixed by #628
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@kambala-decapitator
Copy link
Contributor

Describe the bug
Client doesn't load, crash dialog appears:

Termination Reason:    Namespace DYLD, Code 1 Library missing
Library not loaded: /usr/local/Cellar/qt@5/5.15.13_1/lib/QtGui.framework/Versions/5/QtGui
Referenced from: <FC0F6FB1-9B65-363C-9F53-9DE00118EA61> /Applications/Jellyfin Media Player.app/Contents/Frameworks/QtWebEngineCore.framework/Versions/5/Helpers/QtWebEngineProcess.app/Contents/MacOS/QtWebEngineProcess
Reason: tried: '/usr/local/Cellar/qt@5/5.15.13_1/lib/QtGui.framework/Versions/5/QtGui' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/Cellar/qt@5/5.15.13_1/lib/QtGui.framework/Versions/5/QtGui' (no such file), '/usr/local/Cellar/qt@5/5.15.13_1/lib/QtGui.framework/Versions/5/QtGui' (no such file), '/Library/Frameworks/QtGui.framework/Versions/5/QtGui' (no such file), '/System/Library/Frameworks/QtGui.framework/Versions/5/QtGui' (no such file, not in dyld cache)
(terminated at launch; ignore backtrace)

To Reproduce

Simply launch the player

Expected behavior
Players opens withour errors

Desktop (please complete the following information):

  • OS: macOS 14.4.1
  • Version 1.10 Intel

Additional context
QtGui.framework is present in /Applications/Jellyfin Media Player.app/Contents/Frameworks but still QtWebEngineCore tries to load it from homebrew path

@poulpor
Copy link

poulpor commented May 15, 2024

Same here, Jellyfin Server 10.9.1 latest is used.

@iwalton3 iwalton3 added the help wanted Extra attention is needed label May 15, 2024
@thoja21
Copy link

thoja21 commented May 15, 2024

Same here with latest client (1.10.0) and server 10.9.1 on MacOS 12.7.5.
I get the following but the log file link doesn't do anything. The log in ~/Library/Logs/Jellyfin Media Player doesn't seem to suggest anything is going wrong, although I might be missing something:

Jellyfin Media Player.log

Screenshot 2024-05-15 at 10 02 27 am

@iwalton3
Copy link
Member

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.

@szethh
Copy link

szethh commented May 15, 2024

Same here with latest client (1.10.0) and server 10.9.1 on MacOS 12.7.5. I get the following but the log file link doesn't do anything. The log in ~/Library/Logs/Jellyfin Media Player doesn't seem to suggest anything is going wrong, although I might be missing something:

Jellyfin Media Player.log

Screenshot 2024-05-15 at 10 02 27 am

I have the same issue, also latest jellyfin on macos

@kambala-decapitator
Copy link
Contributor Author

kambala-decapitator commented May 15, 2024

@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)

@kambala-decapitator
Copy link
Contributor Author

kambala-decapitator commented May 15, 2024

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 otool -L on it does show absolute paths to Homebrew for a number of Qt frameworks.

another strange things I noticed:

  • all Qt dylibs (the binaries I mean) are also copied to the Frameworks dir, which doesn't make sense as you already have those binaries inside respective frameworks, and this results in additional ~200 MB
  • version of QtWebEngineCore is reported as 5.15.16 which indicates that it was built from commercial Qt version while e.g. QtGui reports 5.15.13 (the latest open-source Qt 5 version)

@jakobzudrell
Copy link

Any eta when the new builds with this fix are released?
I've seen that at least within the pre-release branch pipeline they were built..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
Development

Successfully merging a pull request may close this issue.

6 participants