[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#908012: wine-development fails to launch various applications with "Initializing dlls failed" error



Package: wine-development
Version: 3.14-2

Wine-development crashes when launching many applications, which are launched by non-development wine perfectly. Following is log for EVE Online launcher:

> $ WINEPREFIX=~/.wine_eve wine-development "C:\EVE\eve.exe"
> 0028:err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
> 000d:err:winediag:xrandr12_init_modes Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead.
> 002f:err:module:attach_dlls "libprotobuf.dll" failed to initialize, aborting
> 002f:err:module:attach_dlls Initializing dlls for L"C:\\EVE\\Launcher\\evelauncher.exe" failed, status c0000005

Wine team is aware of this issue [1], but it seems they can't do anything about it, at least for now. They mention workaround:

> You could either collect all the offenders that have no hotpatch entry point and send in patches that add DECLSPEC_HOTPATCH or use a "no-PIC" build of Wine.
> I've built and run Wine with '-fno-PIC' by default since several years.
> The GOT/PIC register usage in prolog code is incompatible with multiple copy protection/DRM schemes (bug 37540, bug 4666 for example) - even hotpatch doesn't help here, see y explanations. Yes, it can be partially mitigated by emitting syscall thunks for native API (Wine-Staging has some experimental patches) but this won't work for non-native/upper layer PI.

Could anything be done on debian side to mitigate this issue?

ps Sorry for last email w/o subject, please discard it

[1]  https://bugs.winehq.org/show_bug.cgi?id=45199

Regards,
-av

Reply to: