Arch Linux

zynex

Member

Registered: 2019-03-20

Posts: 29

Can't solve "libx265.so=209-64", depending on "jellyfin-ffmpeg"

Hi.

Upgraded my server containing Jellyfin today, and got dependency error for libx265, thus couldn't upgrade it. Seems they set a hard dependency for libx265.so to v209-64, old was 199. The old x265 was updated couple of years ago, but there is a newer version in testing not released to extras yet. Solved it by downloading the testing version of x265 and manually force upgrade it with pacman -Ud x265-3.6-1-x86_64.pkg.tar.zst, then made an upgrade for jellyfin-ffmpeg.

Shouldn't this be controlled before releasing a new version of jellyfin-ffmpeg before released?

Awebb

Member

Registered: 2010-05-06

Posts: 6,688

Re: Can't solve "libx265.so=209-64", depending on "jellyfin-ffmpeg"

Edit: I think I was wrong.
Edit2: File a bug report against jellyfin-ffmpeg.

Last edited by Awebb (2024-06-18 10:25:34)

zynex

Member

Registered: 2019-03-20

Posts: 29

Re: Can't solve "libx265.so=209-64", depending on "jellyfin-ffmpeg"

Hum, also realised that this approach broke php-gd big time.

PHP Warning:  PHP Startup: Unable to load dynamic library 'gd' (tried: /usr/lib/php/modules/gd (/usr/lib/php/modules/gd: cannot open shared object file: No such file or directory), /usr/lib/php/modules/gd.so (libx265.so.199: cannot open shared object file: No such file or directory)) in Unknown on line 0

Awebb

Member

Registered: 2010-05-06

Posts: 6,688

Re: Can't solve "libx265.so=209-64", depending on "jellyfin-ffmpeg"

That was to be expected :-)

The correct approach (from a user pov) would be to skip the jellyfin-ffmpeg update the way pacman suggests and wait for the mess to fix itself. It's not like jellyfin will stop working if that update isn't through.

I'd report the bug myself, but I'm on the phone right now and gitlab is only so and so cooperative.

zynex

Member

Registered: 2019-03-20

Posts: 29

Re: Can't solve "libx265.so=209-64", depending on "jellyfin-ffmpeg"

Could have worked, but this time.. nopp! Downgraded both jellyfin-ffmpeg and x265, and now it seems to work anyway. Could upgrade jellyfin itself though, so just need to wait for the others go catch up. Not sure why jellyfin-ffmpeg is needed if ffmpeg is installed though.

Not sure if I can post a bug report, seems like registration is disabled.

Awebb

Member

Registered: 2010-05-06

Posts: 6,688

Re: Can't solve "libx265.so=209-64", depending on "jellyfin-ffmpeg"

A patched ffmpeg is required for a bunch of the transcode feature of jellyfin.