[Debian Bullseye/Sid] HarfBuzz Version Too Old?

Pokota

pokota@tim-lt-deb:~/beamdog$ apt search harfbuzz | grep installed

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

gir1.2-harfbuzz-0.0/testing,now 2.6.4-1 amd64 [installed,automatic]
libharfbuzz-bin/testing,now 2.6.4-1 amd64 [installed]
libharfbuzz-dev/testing,now 2.6.4-1 amd64 [installed]
libharfbuzz-gobject0/testing,now 2.6.4-1 amd64 [installed]
libharfbuzz-icu0/testing,now 2.6.4-1 amd64 [installed]
libharfbuzz0b/testing,now 2.6.4-1 amd64 [installed]

pokota@tim-lt-deb:~/beamdog$ ./beamdogClient-2.1.11-x86_64.AppImage 
/tmp/.mount_HC87tZ
installed: X-AppImage-BuildId=eecf1560-45a5-11a9-2e73-1fe010890803 image: X-AppImage-BuildId=eecf1560-45a5-11a9-2e73-1fe010890803

(beamdogClient:2553620): Pango-ERROR **: 08:19:40.266: Harfbuzz version too old (1.2.7)

Trace/breakpoint trap

Pokota

I'm not very used to using AppImage packages. I suppose my questions are:

1) Is there a bash script that checks for and enumerates unmet dependencies?
2) Will I need to install a specific Harfbuzz/Pango package?
3) Should I just bite the bullet and play the games through Steam (keeping in mind that I'm trying to avoid using Steam from the machine in question due to Valve being a butt about multiple machines signed into the same account running games at the same time, which puts this at odds with A Certain D&D-Licensee Idle Game)?

ghostdancer

Have the same problem, same distro. Did you get any solution?.

Pokota

No solution yet, we're largely waiting for Beamdog to have enough spare manpower to fix this.

hammers

Same here, but on Archlinux.
It would be great if someone of Beamdog could have a look into this sooner than later, as it renders their client, resp. games unusable/installable for the more recent distro releases. I also volunteer for alpha/beta testing

Lost

Same on LXQT ubuntu 20.04 build

ghostdancer

I have solved , I guess temporarily this problem for the launcher, I've downloaded some libraries from Debian Buster :

• libpango-1.0
• libpangocairo-1.0
• libpangoft2-1.0
• libharfbuzz0b_2.3.1

uncompress them and copy the libs to the directory where the appimage resides . And it's working.
For the launcher to work also from the menus I had to add
Path=/path/to/the/appimage
to the desktop file
The real solution would be for Beamdog to recompile/rebuild a new version with a more modern version of electron.

Pokota

When I tried doing that, I got

pokota@tim-lt-deb:~/beamdog$ ls -la
total 55500
drwxr-xr-x  2 pokota pokota     4096 Sep 18 19:35 .
drwxr-xr-x 51 pokota pokota     4096 Sep 18 19:37 ..
-rwxrwxrwx  1 pokota pokota 55312384 Apr 11 20:42 beamdogClient-2.1.11-x86_64.AppImage
lrwxrwxrwx  1 pokota pokota       24 Feb  1  2019 libharfbuzz.so.0 -> libharfbuzz.so.0.20301.0
-rw-r--r--  1 pokota pokota  1013440 Feb  1  2019 libharfbuzz.so.0.20301.0
lrwxrwxrwx  1 pokota pokota       24 Aug 25 08:46 libpango-1.0.so.0 -> libpango-1.0.so.0.4600.1
-rw-r--r--  1 pokota pokota   329648 Aug 25 08:46 libpango-1.0.so.0.4600.1
lrwxrwxrwx  1 pokota pokota       29 Aug 25 08:46 libpangocairo-1.0.so.0 -> libpangocairo-1.0.so.0.4600.1
-rw-r--r--  1 pokota pokota    63456 Aug 25 08:46 libpangocairo-1.0.so.0.4600.1
lrwxrwxrwx  1 pokota pokota       27 Aug 25 08:46 libpangoft2-1.0.so.0 -> libpangoft2-1.0.so.0.4600.1
-rw-r--r--  1 pokota pokota    96096 Aug 25 08:46 libpangoft2-1.0.so.0.4600.1
pokota@tim-lt-deb:~/beamdog$ ./beamdogClient-2.1.11-x86_64.AppImage 
/tmp/.mount_isJFbw
installed: X-AppImage-BuildId=eecf1560-45a5-11a9-2e73-1fe010890803 image: X-AppImage-BuildId=eecf1560-45a5-11a9-2e73-1fe010890803
/tmp/.mount_isJFbw/usr/bin/beamdogClient: symbol lookup error: libpangoft2-1.0.so.0: undefined symbol: hb_ot_metrics_get_position
pokota@tim-lt-deb:~/beamdog$ 

ghostdancer

I have the same , I get some errors but it launches , the only differences I see are minor version in some libs . The versions I got from Debian for libpango, libpangocairo and libpangoft2 are 1.0.so.4200.3 and yours are 1.0.so.0.4600.1 otherwise we have the same . Even though I',m on Bullseye I downloaded manually the libs from Buster repositories which are older and those are the ones I copied to the directory,

Pokota

The buster libs work, thanks.

PauloAugusto

Any news on this, Beamdog?

I remember I played Neverwinter Nights (again) in the past 2 years and it worked fine on my Ubuntu but now I want to play it again (this time specifically the expansion Infinite Dungeons) but I'm now getting this error...

VivienneL

ghostdancer wrote: »

I have solved , I guess temporarily this problem for the launcher, I've downloaded some libraries from Debian Buster :

• libpango-1.0
• libpangocairo-1.0
• libpangoft2-1.0
• libharfbuzz0b_2.3.1

uncompress them and copy the libs to the directory where the appimage resides . And it's working.
For the launcher to work also from the menus I had to add
Path=/path/to/the/appimage
to the desktop file
The real solution would be for Beamdog to recompile/rebuild a new version with a more modern version of electron.

I followed your directions and got the Beamdog client working on Ubuntu 20.04. I'm sharing the extracted libs here to make things simple for others:
https://drive.google.com/file/d/1GsKEXPgSoB0AWuLSuCX5J5nHt94ZyHOa/view?usp=sharing

Pokota

With Bullseye being the current stable version of Debian, we do need an official fix now.

ghostdancer

I'm not a programmer but someone told me that they just have to recompile the launcher app with a more modern version of Electron and it would be solved, don't know it it would be that easy but I guess that Beamdog has other priorities and maybe prefer Linux users to go through Steam, less headaches for them.

Pokota

The main problems I have with that solution are (1) that Steam currently requires Multiarch for a few key libs, even if you're only installing 64-bit games, and (2) someone had the bright idea of allowing Idle Games on Steam (steam doesn't allow you to run two different games from the same account on different computers at the same time. which is why the Idle Games are a logistical nightmare for me). Having a working native Beamdog client sidesteps both issues.