Wine: Required file not found

[MrHotAir]

Hello.

I have been using this tool to enjoy Diablo 2 Median XL on my Debian 12 machine, many thanks.

However, in my recent installation of Diablo 2 and patching by D2launcher, I receive the error when starting Diablo 2:

"/home/user/Games/d2launcher-4.0.5/d2launcher: line 781: /home/user/.d2launcher/bin/wine/bin/wine: cannot execute: required file not found"

I was confused as I installed Wine along with other prerequisites with 'sudo apt install wine zenity curl unzip jq wmctrl libfuse2 xdelta3' command and when I started D2Launcher, I would allow it to download Wine when requested.

Just to confirm, I removed Diablo 2, D2Launcher folder and the .d2launcher folder. After re-installing Diablo 2, downloading D2Launcher and allowing it to download both Median XL patch, wine and allow to patch Diablo 2. However, I get the same error when launching and when I try to access Wine settings in D2Launcher. A forced update option re-installs Wine, but doesn't fix the issue.

I checked the /.d2launcher/bin/wine/bin/ folder, to find that amongst other files, there is a 'wine' file that even has the executable authority.

Being a little perplexed over this issue, I decided to make this issue ticket. Thank you for reading my message.

[murkl]

That is indeed confusing. Have you changed any properties? Can you try if this command is working for you: /home/user/.d2launcher/bin/wine/bin/wine --version

[MrHotAir]

Hi, pardon for not being able to reach you sooner.

The confusion over the issue has continued. I tried your command and attempted to launch different Wine utilities from the bin folder, only to encounter the same 'required file not found' on that Wine executable that still is there. In trying to at least close the cap on the range of possibilities, I tried d2launcher on an older laptop that had Linux Mint on it, and the Wine executable appeared to have worked.

For now, I have found a workaround of just launching Median XL through Lutris Flatpak, so at least there is that. My working theory is that the issue must be something on my end, well, I will know eventually as I am sure going to fumble the migration to Debian 13 somehow. But, as I said, this is most likely an unintentional error on my part, considering that for such a huge thing no one here or on Median XL forums seem to have encountered a similar issue.

Thanks for answering my initial post. Whilst I could not get the d2launcher to work at the moment, I have had a blast of a time with it previously and wish all the best for the whole stack of contributors trying to make Diablo 2 coming better for the Linux community.