Closed kambala-decapitator closed 4 months ago
Same here, Jellyfin Server 10.9.1 latest is used.
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:
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.
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:
I have the same issue, also latest jellyfin on macos
@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 otool -L
on it does show absolute paths to Homebrew for a number of Qt frameworks.
another strange things I noticed:
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..
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 path