Correct ! One little thing : between “running” and “play” the battle net logo appears in the i3bar half a second.

Got it, I already put this in place. However, I will lock driver and mesa for a few months anyway, just to see what happens. I will come back here to give a feedback !

Thanks a lot !

I applied your advice and gave a feedback about it. My first feeling about you may have been right, you are just unable to not miss the point…

Thank you for your answer. Yes that are things I heard about, but it seems to me that the problem I described occurred even without a battle net update. However, an update may have been applied as I did not notice it.

I will stop upgrade my vulka/mesa packages and see what happens, if the same problem happens again, it will mean that it is a battle net / wine compatibility problem.

Ok, thanks !

The default Lutris’ wine version is wine-ge-8-26-x86_64 by default for me, it can be installed directly from the lutris’ interface. And at the moment, it fails to launch battle net (unlike GE-Proton10-27). In addition, when battle net was in a nonworking period, Lutris’ wine versions failed to run it too.

Why should I since battle net works at the moment with the previous mentioned version ?

At the moment GE-Proton10-27 to lock a working version, by the past it worked with Proton Experimental too (but this one is constantly evolving, that’s why I avoid it now). I tried some others but none of them work when proton doesn’t.

I never launch lutris games through Steam. I wanted to say that I did the following tests :

• Launch steam games through lutris, in order to verify how lutris work.
• Launch windows-only games other than battle net through lutris, in order to verify the behavior of the export VK_ICD_FILENAMES= commands on other games.

It appeared that steam games launched through lutris work (so, in my opinion, lutris works) and games launched with the export VK_ICD_FILENAMES= commands never run (so, in my opinion, those ICD files do not define a working vulkan environment).

Thank you very much for your answers.

I am using X11 and I launch battle net through lutris. It was hard to compare because I only played battle net games last months, but when I launch steam games from lutris, it works as good as if launched from steam.

I experienced instabilities : battle net works then cannot be launched some weeks later then works again after some other weeks. I upgrade my packages every week, that’s why I suspect this problem comes from incompatible upgrades.

I have only one gpu :

# lshw -C video
  *-display                 
       description: VGA compatible controller
       product: Navi 14 [Radeon RX 5500/5500M / Pro 5500M]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:2d:00.0
       logical name: /dev/fb0
       version: c5
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=amdgpu latency=0 resolution=1920,1080
       resources: irq:77 memory:d0000000-dfffffff memory:e0000000-e01fffff ioport:e000(size=256) memory:fcb00000-fcb7ffff memory:fcb80000-fcb9ffff

After your comments I had the idea to test other windows pure games and it the result is the following : none of them work with the previous mentioned ICDs, so those latter seem nonworking. Thus I will avoid them, as advised by @just_another_person@lemmy.world.

During nonworking periods, I had no error messages from battle net or lutris, just the Play button turning to Stop then to Play again after few seconds. So battle net just crashed at startup.

I consider excluding the following packages from upgrades : mesa vulkan-radeon vulkan-icd-loader vulkan-mesa-implicit-layers and their lib32 counterparts. Do you think it will do the trick ?

Thank you very much for your attention and help.