Wine fails because of missing libgcc_s_dw2-1.dll

[Miguel A. Vallejo]

Hello

After the recent update of Wine packages in Sid, some programs do not
run because of a missing libgcc_s_dw2-1.dll. They all worked just fine
with the previous version.

~$ wine SpaceEngine.exe
014c:err:module:import_dll Library libgcc_s_dw2-1.dll (which is needed
by L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\zlib1.dll") not
found
014c:err:module:import_dll Loading library zlib1.dll (which is needed
by L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\libtiff3.dll")
failed (
error c000007b).
014c:err:module:import_dll Library libtiff3.dll (which is needed by
L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\SpaceEngine.exe") not
found
014c:err:module:LdrInitializeThunk Importing dlls for
L"Z:\\home\\eoz\\Programs\\SpaceEngine\\system\\SpaceEngine.exe"
failed, status c0000135

I looked in my backups and I never had any libgcc_s_dw2-1.dll
installed in my system, but now it seems to be needed.

Any ideas? Thanks in advance

[Eike Lantzsch ZP6CGE]

Hi Hello!

 

When I didn't find libgcc_s_dw2-1.dll at first, installing the other missing libraries by using winetricks I was able to start my applications at least.
Start with zlib1.dll - that is in winetricks.
Then copy the other libraries into the pertinent folders of your windows folder of your wine installation.
libgcc_s_dw2-1.dll can be found here

 https://www.sts-tutorial.com/download/start/Mjc2NA==
and libtiff3.dll can be faound herehttps://everydll.com/gnuwin32/libtiff3-dll/#download-dll

Google is your friend - this time -
..._ _.__ __... ...__

 

--

Eike Lantzsch ZP6CGE

[Miguel A. Vallejo]

Hello!

Finding and placing missing DLLs into the Windows directory of Wine is easy.

I think the problem is the windows executables in wine have not been
compiled with the -static-libgcc option of MinGW, so not including all
these libgcc DDLs can be considered a bug itself.

But compiling it without -static-libgcc can be considered a bug also.

This is why I'm asking.

[Eike Lantzsch ZP6CGE]

We are talking about closed source here, don't we? I don't see any
straight forward way to know how the programs have been compiled except
reverse engineering. Not going to do that. Contacting the provider of
the Windows-Programs IMHO would not help either because "it works on xxx
version of MS-Windows".
If the problem is a bug or changes in Wine (6.0.2 is a development
version - no?) Wine-HQ would be the right place to ask, I think.
Either way debian-users does not seem to be the right mailing list for
this kind of problems.
Unless this is a packaging problem ("...repack..."?) but I don't know.

I can't help I'm afraid.
..._ _.__ __... ...__
._._.
--
Eike Lantzsch ZP6CGE

[Floris Renaud]

Not entirely sure, but I think this is the issue:
More and more Wine DLL files are built with mingw.
The libwine package already depends on libz-mingw.
Probably the 'gcc-mingw-w64-i686-win32-runtime' package should now be
installed as well.

Does the program work when you install this package?

[Miguel A. Vallejo]

> Not entirely sure, but I think this is the issue:
> More and more Wine DLL files are built with mingw.
> The libwine package already depends on libz-mingw.
> Probably the 'gcc-mingw-w64-i686-win32-runtime' package should now be
> installed as well.
>
> Does the program work when you install this package?

Installed gcc-mingw-w64-i686-win32-runtime (and gcc-mingw-w64-base
because of dependencies) but still not working.

These packages install some DLLs in /usr/lib/gcc/i686-w64-mingw32 so
win32 programs can't load them there. Also note libgcc_s_dw2-1.dll is
not provided with these packages.

I'm pretty sure the problem is the Wine DLL files were built without
the -static-libgcc flag

Time to file a bug?

[Floris Renaud]

On donderdag 03 maart 2022 14:38:32 (+01:00), Miguel A. Vallejo wrote:

> > Not entirely sure, but I think this is the issue:
> > More and more Wine DLL files are built with mingw.
> > The libwine package already depends on libz-mingw.
> > Probably the 'gcc-mingw-w64-i686-win32-runtime' package should now be
> > installed as well.
> >
> > Does the program work when you install this package?
>
> Installed gcc-mingw-w64-i686-win32-runtime (and gcc-mingw-w64-base
> because of dependencies) but still not working.
>
> These packages install some DLLs in /usr/lib/gcc/i686-w64-mingw32 so
> win32 programs can't load them there. Also note libgcc_s_dw2-1.dll is
> not provided with these packages.
>

Strange, I get:
$ dpkg -L gcc-mingw-w64-i686-win32-runtime | grep libgcc_s
/usr/lib/gcc/i686-w64-mingw32/10-win32/libgcc_s_dw2-1.dll

I had hoped that the Wine packages would refer to that, but unfortunately
that is not the case.

> I'm pretty sure the problem is the Wine DLL files were built without
> the -static-libgcc flag
>
> Time to file a bug?
>

I think it is

[Miguel A. Vallejo]

> > I'm pretty sure the problem is the Wine DLL files were built without
> > the -static-libgcc flag
> >
> > Time to file a bug?
> >
>
> I think it is

I'm looking for the exact package that contains zlib1.dll but I can't
find it. Libwine depends on libz-mingw-w64 but the zlib1.dll there is
not the same as the one wine puts in the drive_c directory. The one in
drive_c directory is a PE32 DLL and the one provided with
libz-mingw-w64 is a 64 bit one.

I confirmed zlib1.dll needs libgcc_s_dw2-1.dll and this one needs
libwinpthread-1.dll and... I can see a DLL hell in advance.

Where does this zlib1.dll come from? It appears everytime wine creates
a drive_c directory, even for a new user.

[Christian Britz]

> I'm looking for the exact package that contains zlib1.dll but I can't
> find it. Libwine depends on libz-mingw-w64 but the zlib1.dll there is
> not the same as the one wine puts in the drive_c directory. The one in
> drive_c directory is a PE32 DLL and the one provided with
> libz-mingw-w64 is a 64 bit one.

On Stable:
apt-file search zlib1.dll
libterralib-doc: /usr/share/doc/libterralib-dev/examples/Debug/zlib1.dll
libz-mingw-w64: /usr/i686-w64-mingw32/lib/zlib1.dll
libz-mingw-w64: /usr/x86_64-w64-mingw32/lib/zlib1.dll

Seems both 32 and 64 bit dll are included in the package.

Regards,
Christian

--
http://www.cb-fraggle.de

[Miguel A. Vallejo]

Thank you!

I filled a bug report. Let's see what happens now.

[Eike Lantzsch ZP6CGE]

On Donnerstag, 3. März 2022 12:17:37 -03 Miguel A. Vallejo wrote:
> Thank you!
>
> I filled a bug report. Let's see what happens now.

Just because I mentioned installing DLLs by means of winetricks: beware
of using winetricks in this situation. Obviously it installs DLLs which
are not compatible with the current wine packages.
After trying this I had some Win-programs coming up nicely, or even
better than before the Debian Sid updates but went haywire when they
started their own update routines of data.
Trying to resolve this and by using wintricks for some DLLs I now
managed to have the programs start and appear as running applications
but they are not showing any windows in X11 - duh ...

--
Eike Lantzsch ZP6CGE

[Miguel A. Vallejo]

Hello!

Opened a bug report against Wine, because I was not sure about what
package was the culprit. #1006725

It was reasigned to libz-mingw-w64 and a few moments ago I downloaded
the updated package from the repository.

Everything works fine now. Thanks to everyone who made this possible.