Closed xBelladonna closed 9 months ago
I have updated the system information in this issue. I was able to get hyperiond to launch by copying the working libfreetype from Debian 12 to my Arch installation and symlinking it to libfreetype.so.6
. This is not a setup I have left permanently on my system, this was just for testing. I am willing to do any testing, building, investigation that I am capable of to get this fixed. Please let me know if recreating the test setup with the older libfreetype and doing some more work would be helpful.
Would you mind checking with the new releases 2.0.16? For Fedora, we now provide dedicated dnf installation files see here
I (unfortunately) run Arch Linux as I'm all about getting the latest bugs first, so I packaged 2.0.16 using the tarball release as the source and installed it as a normal Arch user would (I think). I can confirm it all works! libfreetype 2.13.2-1 seems to work fine with it and the workaround is no longer required. Thank you so much!!
Bug report
Hyperion 2.0.15 does not start on Arch Linux due to incompatibility with newer libfreetype 2.13. See #1359 for a similar issue on Fedora. Hyperion 2.0.15 is currently working on Debian bookworm with libfreetype 2.12.
Steps to reproduce
What is expected?
hyperiond will start normally and appear in the system tray.
What is actually happening?
hyperiond exits with the following error:
hyperiond: symbol lookup error: /usr/lib/libfreetype.so.6: undefined symbol: hb_ot_tags_from_script_and_language
If the library version from Debian 12 (bookworm) is copied to
/usr/lib
and symlinked tolibfreetype.so.6
, Hyperion then launches without issue. I have tested this with the current Debian library/usr/lib/x86_64-linux-gnu/libfreetype.so.6.18.3
. Arch's version appears to belibfreetype.so.6.19.0
.System
Hyperion Server:
Hyperion Server OS: