Wine appimage not working

[Blad3forc3]

Recently I have noticed the size of the wine appimage has reduced (from nearly 900mb to 230mb) since this i have found the wine appimage doesnt work with everything it once did. Can you build wine appimages with 32bit support?

[ivan-hc]

In my use case, 32bit apps are working but are very very slow.

[ivan-hc]

@mmtrt any solution?

[ivan-hc]

@Blad3forc3 just realized that this may be an issue with the experimental support to Wayland, are you on an x11 environment too?

@mmtrt should an environment variable be included in the package?

[mmtrt]

@ivan-hc Try using dxvk and d8vk if facing slow perf, also that exp support for wayland is not enabled.

[ivan-hc]

Try using dxvk and d8vk if facing slow perf,

how? If you are referring to the version from the repositories, it doesn't work. I also tried restarting.

[Blad3forc3]

I am on x11 yes. It is only 32bit apps that fail. I didn't have a problem when the appimages were 800+ mb.

[mmtrt]

how? If you are referring to the version from the repositories, it doesn't work. I also tried restarting.

./wine-devel_9.2-x86_64.AppImage winetricks dxvk

for d8vk just place d3d8.dll in app/game dir and in winecfg add dlloverride d3d8 as native

here 32bit game with d8vk perf

[ivan-hc]

./wine-devel_9.2-x86_64.AppImage winetricks dxvk

for d8vk just place d3d8.dll in app/game dir and in winecfg add dlloverride d3d8 as native

here 32bit game with d8vk perf

I've followed all the instructions, Diablo 2 LOD (year 1999) still lags

[mmtrt]

I've followed all the instructions, Diablo 2 LOD (year 1999) still lags

use d2dx with dxvk for diablo 2 lod

[ivan-hc]

Tried and didn't work.

However, I've two 32bit games:

• Diablo 2 LOD: is very slow and I get this message

  0118:err:environ:init_peb starting L"Z:\\media\\ivan\\userdata\\Giochi\\Diablo II\\SystemSurvey.exe" in experimental wow64 mode
  0118:err:winediag:ntlm_check_version ntlm_auth was not found. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.
  0118:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems

• Fifa 2004: it doesn't start anymore, I get this message

  0024:err:environ:init_peb starting L"Z:\\media\\ivan\\userdata\\Giochi\\FIFA 2004\\fifa2004.exe" in experimental wow64 mode
  0024:err:module:import_dll Library d3d8.dll (which is needed by L"Z:\\media\\ivan\\userdata\\Giochi\\FIFA 2004\\fifa2004.exe") not found
  0024:err:module:loader_init Importing dlls for L"Z:\\media\\ivan\\userdata\\Giochi\\FIFA 2004\\fifa2004.exe" failed, status c0000135

  I use your AppImage since you had 5 stars (I remember this because its one of my favourites)

[ivan-hc]

UPDATE: I've tried to create a new wine prefix using old wine builds from https://github.com/Kron4ek/Wine-Builds and still does not work as before. At this point I think that there is something broken with some recent updates. I use Debian Testing and recently I remember that I've updated MESA from version 8 to 9. May this be the issue?

@Blad3forc3 can you confirm what I say?

[mmtrt]

0118:err:environ:init_peb starting L"Z:\media\ivan\userdata\Giochi\Diablo II\SystemSurvey.exe" in experimental wow64 mode 0118:err:winediag:ntlm_check_version ntlm_auth was not found. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. 0118:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems

install winbind for fixing ntlm errors, for d2dx add glide3x to game dir and add that as native windows dlloverride, install dxvk from winetricks and launch game with these args -3dfx -dxnocompatmodefix should be working now.

for fifa idk why it keeps crashing only work after first install without any changes now it just crashes.

[ivan-hc]

• glide3x is alredy into the directory of Diablo
• to install dxvk from winetricks I get this error

  warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
  ------------------------------------------------------
  ------------------------------------------------------
  warning: You apppear to be using Wine's new wow64 mode. Note that this is EXPERIMENTAL and not yet fully supported. If reporting an issue, be sure to mention this.
  ------------------------------------------------------
  Using winetricks 20240105-next - sha256sum: c1b154448fb623c5a52167c4e07a5b5b5634db4493a674d0ec68b919e755ffb8 with wine-9.0 and WINEARCH=win64
  Executing w_do_call dxvk
  ------------------------------------------------------
  warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
  ------------------------------------------------------
  ------------------------------------------------------
  warning: You apppear to be using Wine's new wow64 mode. Note that this is EXPERIMENTAL and not yet fully supported. If reporting an issue, be sure to mention this.
  ------------------------------------------------------
  dxvk already installed, skipping

• to launch Diabo 2 with -3dfx -dxnocompatmodefix, nothing changes

However, I've just finishet trying to use wine/wine32 from Debian repositories... same issue.

I've never had issues with your AppImage, but if also with wine 8.x from binaries and wine 9 from repositories does not work anymore, I think that there is an issue with MESA or something

[mmtrt]

really weird d2 lod seem to work fine for me with that config.

[ivan-hc]

I've done a test in Virtualbox, Windows 10, and the games are quite fluid, it is not a MESA issue as I was thinking about.

Its really too strange.

[mmtrt]

found the cause of games crashing it seems is starting path of executable issue idk why this happens

/to/the/path/wine.appimage filename.exe game works

/to/the/path/wine.appimage /to/the/path/filename.exe game crashing

[ivan-hc]

???

what does it has to do with it? I tried both ways, the result is the same: Fifa2004 doesn't start, Diablo2 is slow.

[ivan-hc]

@mmtrt according to my tests, the problem is elsewhere, maybe not the AppImage itself. If you can share the AppImage of version 8.x, therefore prior to the latest release, I am convinced that it will not work the same. I don't know what happened, a different version MESA driver, some kernel module... if you have some old build, I might test to see if I'm wrong.

[mmtrt]

nvm that issue seem only related to fifa 2004 demo crashing,

also both games working fine here now.

[mmtrt]

Try local building of devel and staging appimage using this last known v8 repo changes

[ivan-hc]

appimagebuilder.modules.setup.generator.RuntimeGeneratorError: Unsupported AppRun version (v3.0.0-devel-2), please use v2.0.0 or newer

[ivan-hc]

I'll try with AppRun v2.0.0

[ivan-hc]

File "/home/ivan/Scrivania/WINE_AppImage/squashfs-root/usr/lib/python3.8/site-packages/appimagebuilder/commands/run_script.py", line 82, in __call__
    raise RuntimeError("Script exited with code: %s" % _proc.returncode)
RuntimeError: Script exited with code: 2

[mmtrt]

alright done re enabled v8 builds

[ivan-hc]

I've seen, now I'm downloading "stable"

[ivan-hc]

Everything works really good now!

[ivan-hc]

So there is something in the new wine 9.x appimages that does not work as it should.

[mmtrt]

Everything works really good now!

that's great.

So there is something in the new wine 9.x appimages that does not work as it should.

should be related to wow64 not everything works with it ig.

[ivan-hc]

yep, I've taken a look around and seems that none talks about a troubleshot. I was so happy to use it with my AppImage of Bottles.

[ivan-hc]

Sadly they don't provide a 32bit runner, but your AppImage, if symlinked as "wine" and "wine64" in ~/.local/bin did the trick

[ivan-hc]

@mmtrt I don't know if this would help in investigating on why wine 9 does not work for me: I have an old Nvidia GeForce GT 710 (driver "nvidia-tesla-470-driver" on Debian repositories).

[mmtrt]

@mmtrt I don't know if this would help in investigating on why wine 9 does not work for me: I have an old Nvidia GeForce GT 710 (driver "nvidia-tesla-470-driver" on Debian repositories).

its older gpu so it would be better to use older dxvk like 1.10.x which have support for 470.x nv drivers.

[ivan-hc]

if so, how should I install it? should I use winetricks?

[mmtrt]

ye winetricks or you can manually add from its archive.

[ivan-hc]

@mmtrt I've tried and it didn't worked (I've installed "dxvk0054").

Fifa2004 now starts and also the game is quite fluid, but menus are slow, the same happen to Diablo2... but also the gameplay is slow and unplayable.

[ivan-hc]

@mmtrt Forgive me for asking, I extracted the two AppImages and noticed some differences.

I can see that the new AppImage have no more an AppRun.env file in the root of thearchive, but the AppRun binary is bigger than the previous one and also the wrapper is quite different (at least in the header, you exported the wine and wineserver binaries which shouldn't be a problem).

This seems to be a huge change in the code, but more than that I can't investigate further.

I build AppImage packages myself, I typically list all the environment variables and commands needed in a single AppRun script (and I'm often forced to export libraries from the host as well to make my packages work). I liked the modular method you adopted in version 8, but since I can't extract the AppRun binary I can't take a look to see if anything has changed.

I wonder, could this revolution you have made to the code have contributed to the malfunctioning with old Nvidia cards?

[ivan-hc]

@mmtrt For example, the file AppRun.config exports /usr/lib and /lib, but not /opt/wine-stable/lib/wine/x86_64-unix, should them be included in LD_LIBRARY_PATH?

Also, I'm not a WINE expert, so I don't know how wow64 works exactly, but I can't see 32bit libraries in the package, this time (the previous versions had also a i386-linux-gnu directory under /lib or /usr/lib). May this be a limit for 32bit programs (at least on old GPUs)?

[mmtrt]

well AppRun binary and AppRun.env, AppRun.config changes are due to using diff appimagebuilder with AppImage runtime v3 b/c without using that wine v9 was not working so I had to shift to that.

[ivan-hc]

I understand, so the previous one work with libfuse2 and this one does not need it