Steam Linux Runtime not able to find bz2 library while running Battle for Wesnoth on Slackware

[gbschenkel]

Your system information

• Steam Runtime Version: 1767909714
• Distribution (e.g. Ubuntu 18.04): Slackware 15.0-Current (12/Jan up-to-dated)
• Link to your full system information: Gist
• Have you checked for system updates?: Yes
• What compatibility tool are you using?: Steam Linux Runtime
• What versions are listed in steamapps/common/SteamLinuxRuntime/VERSIONS.txt?

#Name   Version         Runtime Runtime_Version Comment
depot   0.20240806.0                    # Overall version number
LD_LIBRARY_PATH -       scout   -       # see ~/.steam/root/ubuntu12_32/steam-runtime/version.txt
scripts 0.20240806.0                    # from steam-runtime-tools

• What versions are listed in steamapps/common/SteamLinuxRuntime_soldier/VERSIONS.txt?

#Name   Version         Runtime Runtime_Version Comment
depot   2.0.20250929.168591                     # Overall version number
pressure-vessel 0.20250926.0    scout           # pressure-vessel-bin.tar.gz
scripts 0.20250926.0                    # from steam-runtime-tools
soldier 2.0.20250929.168591     soldier 2.0.20250929.168591     # soldier_platform_2.0.20250929.168591/

• What versions are listed in steamapps/common/SteamLinuxRuntime_sniper/VERSIONS.txt?

#Name   Version         Runtime Runtime_Version Comment
depot   3.0.20250929.168600                     # Overall version number
pressure-vessel 0.20250926.0    scout           # pressure-vessel-bin.tar.gz
scripts 0.20250926.0                    # from steam-runtime-tools
sniper  3.0.20250929.168600     sniper  3.0.20250929.168600     # sniper_platform_3.0.20250929.168600/

Please describe your issue in as much detail as possible:

I am trying to run Battle for Wesnoth[599390] using branch development 1.19, the game crash while loading the libs, if I use the main/default branch, it works.
I ask for few other Linux users to try this branch, on Slackware it is not working, on other distros, like Arch, it is.
I filled the issue 10601 with Wesnoth devs but this issue appears be only in Slackware.

The Issue is when running this specific branch, the game crash with the message:
./wesnoth: error while loading shared libraries: libbz2.so.1.0: cannot open shared object file: No such file or directory

While running Steam with STEAM_LINUX_RUNTIME_LOG=1 I could see:

<6>17:30:04.743649: pressure-vessel-wrap[22462]: I: SONAME "libbz2.so.1.0" is canonically "libbz2.so.1" on host system
<6>17:30:04.743703: pressure-vessel-wrap[22462]: I: Found override for libbz2.so.1.0: /usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/libbz2.so.1

which points the steam and pressure-vessel-wraps are indeed find it, but when starting the runtime it don't which I think can be related to steam-runtime.
I tested with sniper, soldier, I don't remember if I tried with scout.
I also removed the pinned libraries before starting Steam to check if it could work.

Here is the full log

Steps for reproducing this issue:

1. On Slackware, launch Steam
2. Install Battle for Wesnoth (steam steam://install/599390)
3. Open Game Setting
   a. "Old layout" >> Betas >> 1.19 - Development release
   b. "New layout" >> Game Versions & Betas >> 1.19 - Development release
4. Start the game

[smcv]

There is some historical confusion about what is the correct SONAME for libbz2: some distros use libbz2.so.1 and others use libbz2.so.1.0. This puts it in an unfortunate situation where it has to go into less reliable code paths.

Ideally we'd use the libbz2.so.1.0 from sniper and completely ignore Slackware's libbz2.so.1, but that isn't necessarily an option if something in the graphics driver stack on Slackware depends on it.

[smcv]

I tested with sniper, soldier, I don't remember if I tried with scout

Battle for Wesnoth is configured to use sniper (unless they've changed it recently), which means that any runtime other than sniper would be considered to be incorrect.

[smcv]

Two things that would help to diagnose this:

1. Pleae collect a log similar to the one you already collected, but with STEAM_LINUX_RUNTIME_VERBOSE=1 in the environment: this will log additional information about what is happening here and why

2. Please investigate which one of Slackware's graphics driver libraries depends on libbz2.so.1, either directly or perhaps via something like libllvm or Boost or Cairo - ideally none of them would (on other distributions like Debian, they don't), and if that was the case, then this problem wouldn't occur