missing mesa-vulkan-drivers:i386

Battle.net fails to launch through Lutris because mesa-vulkan-drivers:i386 is missing by default:

On a fresh PikaOS installation, Battle.net installed through the official Lutris installation script fails to launch.

Lutris starts the configured Proton-CachyOS runner correctly, but Battle.net immediately exits with a DXVK/Vulkan initialization error:

err: DxvkInstance::createInstance: Failed to create Vulkan instance err: Failed to initialize DXVK.

Installing the missing 32-bit Mesa Vulkan driver fixes the problem immediately:

sudo apt install mesa-vulkan-drivers:i386

After installing this package, Battle.net launches normally through Lutris without any other changes.

System

• Distribution: PikaOS
• Desktop: GNOME 51
• Session: Wayland
• GPU: AMD Radeon RX 9060 XT
• Vulkan driver: RADV
• Mesa: 26.2.3 (PikaOS YellowBirb Mesa Stable)
• Lutris: installed from PikaOS
• Battle.net: installed using the Lutris Battle.net installation script
• Wine/Proton runner: Proton-CachyOS Latest
• UMU: 1.4.4
• Steam Runtime: steamrt4

Vulkan status

The system Vulkan installation was working correctly before the fix.

vulkaninfo --summary detected:

deviceName = AMD Radeon RX 9060 XT (RADV GFX1200) driverName = radv driverInfo = Mesa 26.2.3 - PikaOS YellowBirb Mesa Stable apiVersion = 1.4.354

The system also had i386 enabled:

amd64 i386

Most Mesa and Vulkan 32-bit libraries were already installed, including:

libvulkan1:i386 libmesa-stable:i386 mesa-lib-gallium:i386 libgl1-mesa-dri:i386

However, the following package was missing:

mesa-vulkan-drivers:i386

Only the 64-bit package was installed:

mesa-vulkan-drivers:amd64

Lutris error

The relevant part of the Lutris/UMU log was:

Proton: /home/brebs/Games/battlenet/drive_c/Program Files (x86)/Battle.net/Battle.net Launcher.exe Proton: Executable is a unix path, launching with 'umu.exe'. ntsync: up and running.

err: DxvkInstance::createInstance: Failed to create Vulkan instance err: Failed to initialize DXVK. err: DxvkInstance::createInstance: Failed to create Vulkan instance

The process then exited with return code 0.

Workaround

Installing:

sudo apt install mesa-vulkan-drivers:i386

was sufficient to resolve the issue.

No other changes were made to Lutris, Proton, Battle.net, Vulkan configuration, or the Wine prefix.

Battle.net then launched successfully.

Expected behavior

For a gaming-focused PikaOS installation with i386 support enabled, the required 32-bit Vulkan Mesa driver should either:

1. be installed by default, or
2. be pulled in automatically as a dependency when the relevant gaming/Wine/Proton components are installed.

Question

Should mesa-vulkan-drivers:i386 be included by default in the PikaOS gaming environment, or otherwise be pulled in automatically by the packages responsible for the 32-bit gaming stack?

This issue makes Battle.net appear to be broken immediately after installation, even though the underlying Vulkan installation is otherwise working correctly.

Thanks a lot.

Great regards.