You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So i updated from 1.78 and now when i launch koboldcpp it works as intended aside from no longer automatically launching the browser and a weird line in the terminal.
exo-open: symbol lookup error: /lib/x86_64-linux-gnu/libharfbuzz.so.0: undefined symbol: FT_Get_Transform
I never got that kind of error in any of the previous versions, what is this?
im using debian 12 for context.
The text was updated successfully, but these errors were encountered:
i just download koboldcpp-linux-x64-cuda1210, what i always used, weirdly enough the program functions normally, i can type and get responses, everything just this error shows up at the very bottom.
edit: also forgot to mention when i go back to using 1.78 the error disappears, it's only in the latest version and it only shows up right after startup, new line right below the 'please connect to the custom endpoint'
Exo-open is the XFCE desktop environment's default url handler. It looks like it's trying to open a browser window in Chromium, which uses the library libharfbuzz, but it fails because...libharfbuzz is trying to call a function that was added in Freetype 2.11 and not finding it? But Debian 12 is on Freetype 2.12.1, I think, so I'm not sure why it can't find it or why this would happen only with certain versions of Kobold. I don't use Debian/Chromium/CUDA, and I don't have this issue on openSUSE Tumbleweed with Librewolf, so idk. Maybe someone else knows more.
So i updated from 1.78 and now when i launch koboldcpp it works as intended aside from no longer automatically launching the browser and a weird line in the terminal.
exo-open: symbol lookup error: /lib/x86_64-linux-gnu/libharfbuzz.so.0: undefined symbol: FT_Get_Transform
I never got that kind of error in any of the previous versions, what is this?
im using debian 12 for context.
The text was updated successfully, but these errors were encountered: