bug#42342: Wine64 segfaults (5.12/staging)

bug#42342: Wine64 segfaults (5.12/staging)

[Leo Prikler]

Since commit 065a5ed677cdd1a65acae20f185d7c4bd23b1f2c wine and wine64
are upgraded to version 5.12.  The latter segfaults when doing anything
other than wine --help or wine --version.  (Try for example wine
regedit or winecfg).

The old 5.3 version continues to work after roll-back, and would
probably also work through inferiors.  I am currently checking previous
versions of wine64-staging with guix time-machine to see at which point
the error might have been introduced.  Until now, version 5.6 from
7b23a69d6b97c463cb1ef237931af11c22c19c67 fails with the following
output:

000b:fixme:winediag:__wine_start_process Wine Staging 5.6 is a testing
version containing experimental patches.
000b:fixme:winediag:__wine_start_process Please mention your exact
version when filing bug reports on winehq.org.
0009:err:module:LdrInitializeThunk "kernelbase.dll" failed to
initialize, aborting
0009:err:module:LdrInitializeThunk Initializing dlls for
L"C:\\windows\\system32\\winecfg.exe" failed, status c0000005

Regards, Leo

bug#42342: Wine64 segfaults (5.12/staging)

[Leo Prikler]

Interestingly enough 5.8 (ec16aaff5da9eb52b9d762531660f02e785d72de)
works without problems and there is no version packaged between it and
5.12/5.12.1 (wine64 and wine64-staging respectively).  Given this array
of results I'm pretty sure something goes wrong upstream.

I'll use inferiors as a local workaround for the time being and wait
for the problem to be fixed upstream.  I'll also look into 5.9 to 5.11
and perhaps provide a proper downgrade patch later on.

Regards, Leo

bug#42342: Wine64 segfaults (5.12/staging)

[Tobias Geerinckx-Rice via Bug reports for GNU Guix]

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

Leo Prikler 写道：
> I'll use inferiors as a local workaround for the time being and 
> wait
> for the problem to be fixed upstream.  I'll also look into 5.9 
> to 5.11
> and perhaps provide a proper downgrade patch later on.

I admit to being a bit confused.  IIRC on #guix you reported that 
wine-staging was broken, not wine64-staging.  If you only want to 
downgrade the latter, that's all right by me, but I consider that 
one of the risks of using the staging branch to begin with.

Is there a reason you rely on staging, and the 64-bit version to 
boot?

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[Leo Prikler]

Am Dienstag, den 28.07.2020, 18:53 +0200 schrieb Tobias Geerinckx-Rice:
> Leo Prikler 写道：
> > I'll use inferiors as a local workaround for the time being and 
> > wait
> > for the problem to be fixed upstream.  I'll also look into 5.9 
> > to 5.11
> > and perhaps provide a proper downgrade patch later on.
> 
> I admit to being a bit confused.  IIRC on #guix you reported that 
> wine-staging was broken, not wine64-staging.  If you only want to 
> downgrade the latter, that's all right by me, but I consider that 
> one of the risks of using the staging branch to begin with.
> 
> Is there a reason you rely on staging, and the 64-bit version to 
> boot?
> 
> Kind regards,
> 
> T G-R
I'm referring to the package "wine64-staging", which is on master.  I
may have been confused myself at the time I mentioned this in #guix,
but now I have tested this a bit more thoroughly.

For one, I've historically been using wine64, since (at least on Guix)
it works with both 32bit and 64bit software and I sometimes stumble
upon the latter.  As a result, I have a 64bit wine prefix and using
wine (or wine-staging) does not really work well with that.  I was able
to determine that plain wine is unaffected by running the same commands
on a machine with no existing prefix.  (Note, that regular wine64 still
fails with a fresh prefix.)  My experiments with wine64-staging were
solely meant as a way of finding the point at which wine64 fails, I
have no intent of actually using it for more than that.
I'm not quite sure, what exactly is at fault here.  It could be
upstream, or it could be the magic that we use to merge 32 and 64 bit
wine.

TL;DR: The affected packages are wine64 and wine64-staging, the latter
of which is broken beyond 5.8 (though 5.9 would work as well).  Since
this affects the 64bit version of wine specifically, we either have to
fix something in our build (not sure what) or desync wine and wine64
(same with -staging variants)

Regards,
Leo

bug#42342: Wine64 segfaults (5.12/staging)

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 114 bytes --]

I can reproduce and indeed, staging 5.8 was working fine for me.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 77 bytes --]

Cc-ing to Tobias and Jakub.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[Tobias Geerinckx-Rice via Bug reports for GNU Guix]

[-- Attachment #1: Type: text/plain, Size: 320 bytes --]

Pierre Neidhardt 写道：
> Cc-ing to Tobias and Jakub.

Thanks.  Have you reported this upstream?  It sounds similar to 
[0].

I'm against reverting wine-staging to a previous version though. 
If you want a stable wine, use wine.

Kind regards,

T G-R

[0]: https://bugs.winehq.org/show_bug.cgi?id=49380

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 444 bytes --]

Tobias Geerinckx-Rice <me@tobias.gr> writes:

> [0]: https://bugs.winehq.org/show_bug.cgi?id=49380

This issue is about wine being unable to load a dll.
Here our wine segfaults, meaning it does not even get the  chance to
start before looking up the .dlls.

I'm suspecting an issue with us because I doubt that upstream would fail
to notice a completely unusable wine for 3 versions :p

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[Tobias Geerinckx-Rice via Bug reports for GNU Guix]

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

Pierre Neidhardt 写道：
> I'm suspecting an issue with us because I doubt that upstream 
> would fail
> to notice a completely unusable wine for 3 versions :p

What about me?

--8<---------------cut here---------------start------------->8---
~/guix master λ git log gnu/packages/wine.scm | grep -B3 'gnu: 
wine-staging.*: Update'
Author: Tobias Geerinckx-Rice <me@tobias.gr>

    gnu: wine-staging: Update to 5.13.
--
Author: Tobias Geerinckx-Rice <me@tobias.gr>

    gnu: wine-staging: Update to 5.12.1.
--
Author: Tobias Geerinckx-Rice <me@tobias.gr>

    gnu: wine-staging-patchset-data: Update to 5.8.
--
Author: Tobias Geerinckx-Rice <me@tobias.gr>

    gnu: wine-staging-patchset-data: Update to 5.6.
--8<---------------cut here---------------end--------------->8---

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 72 bytes --]

Is it working for you?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[Jakub Kądziołka]

[-- Attachment #1: Type: text/plain, Size: 445 bytes --]

On Tue, Jul 28, 2020 at 05:58:08PM +0200, Pierre Neidhardt wrote:
> Cc-ing to Tobias and Jakub.
> 
> -- 
> Pierre Neidhardt
> https://ambrevar.xyz/

Hi,

I can't reproduce this. I usually use 32-bit wine, so when it complained
about the bitness of the wineprefix, I did

$ mv ~/.wine ~/.wine32

then

$ guix environment --ad-hoc wine64 -- wine64 regedit

fired up the registry editor just fine.

Regards,
Jakub Kądziołka

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[pelzflorian (Florian Pelz)]

On Thu, Jul 30, 2020 at 04:54:45PM +0200, Jakub Kądziołka wrote:
> $ guix environment --ad-hoc wine64 -- wine64 regedit
> 
> fired up the registry editor just fine.


Indeed, when running pure 64-bit applications (like VLC’s 64-bit
Windows build), using wine64 instead of wine works fine.  I did not
even know this command existed.

It seems the issue is only with WoW64, i.e. supporting both 32-bit and
64-bit programs.  The synopsis of wine64 claims it’s a WoW64 version.

For example, the installer of VLC’s 32-bit or 64-bit Windows version
fails to run.  The installer is claimed by binutils’ objdump program
to be a 32-bit i386 executable instead of i386:x86-64.

Regards,
Florian

bug#42342: Wine64 segfaults (5.12/staging)

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 3024 bytes --]

Now that wine stable is 5.12, I can't use start 32-bit applications
anymore.  I tried from a clean wine prefix and I only get this error:

--8<---------------cut here---------------start------------->8---
Segmentation fault
--8<---------------cut here---------------end--------------->8---

Here is the end of the strace:

--8<---------------cut here---------------start------------->8---
openat(AT_FDCWD, "/gnu/store/fhxjkwnv9w8a283f5qaiqq8hcmfmdap9-wine64-5.12/bin/../lib/wine32/wine/ntdll.dll.so", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/gnu/store/ajyl64ycr9vv51q2np68agwz2ad9lxqs-wine-5.12/lib/wine32/wine/ntdll.dll.so", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P\360\302{4\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0555, st_size=941360, ...}) = 0
mmap2(0x7bc00000, 864996, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7bc00000
mmap2(0x7bc1e000, 487424, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e000) = 0x7bc1e000
mmap2(0x7bc95000, 200704, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x95000) = 0x7bc95000
mmap2(0x7bcc6000, 49152, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xc5000) = 0x7bcc6000
mmap2(0x7bcd2000, 4836, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7bcd2000
close(3)                                = 0
openat(AT_FDCWD, "/gnu/store/ajyl64ycr9vv51q2np68agwz2ad9lxqs-wine-5.12/lib/wine32/libm.so.6", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/gnu/store/z4li262il798hbl0l1h1k3a5g7r6bffa-glibc-2.31/lib/libm.so.6", O_RDONLY|O_LARGEFILE|O_CLOEXEC) = 3
read(3, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\241\0\0004\0\0\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0555, st_size=1109456, ...}) = 0
mmap2(NULL, 1048680, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7eeff000
mmap2(0x7ef09000, 774144, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xa000) = 0x7ef09000
mmap2(0x7efc6000, 229376, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xc7000) = 0x7efc6000
mmap2(0x7effe000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xfe000) = 0x7effe000
close(3)                                = 0
mprotect(0x7effe000, 4096, PROT_READ)   = 0
mprotect(0x7bc00000, 122880, PROT_READ|PROT_WRITE) = 0
mprotect(0x7bc1e000, 487424, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mprotect(0x7bc95000, 200704, PROT_READ|PROT_WRITE) = 0
mprotect(0x7bc95000, 200704, PROT_READ) = 0
mprotect(0x7bc1e000, 487424, PROT_READ|PROT_EXEC) = 0
mprotect(0x7bc00000, 122880, PROT_READ) = 0
mprotect(0x7bcc6000, 4096, PROT_READ)   = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x30} ---
+++ killed by SIGSEGV +++
Segmentation fault
--8<---------------cut here---------------end--------------->8---

Are 32-bit applications really working for some of you?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[Pierre Neidhardt]

[-- Attachment #1: Type: text/plain, Size: 307 bytes --]

OK, I think I got it.  I had to have _both_ wine and wine64 (staging or
not) in my profile.

Previously, the "wine" executable (for 32-bit apps) used to work when
wine64 alone was in the profile.  Now it looks like we need both.  Any
idea what changed?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[Jakub Kądziołka]

[-- Attachment #1: Type: text/plain, Size: 837 bytes --]

On Sun, Aug 09, 2020 at 04:03:07PM +0200, Pierre Neidhardt wrote:
> OK, I think I got it.  I had to have _both_ wine and wine64 (staging or
> not) in my profile.

Interesting. Perhaps we should merge the two packages, then? We'd need
to take care to make it work right on i686-linux, but I don't think
that's unsurmountable...

> Previously, the "wine" executable (for 32-bit apps) used to work when
> wine64 alone was in the profile.  Now it looks like we need both.  Any
> idea what changed?

Perhaps loading 32-bit programs with the wine64 wasn't supposed to work
in the first place, and we were relying on some implementation quirk?
Alternatively, cross-compiling from 64 to 32 bit is less tested by
upstream than compiling natively on 64 or 32 bit, and we're hitting an
upstream bug?

Regards,
Jakub Kądziołka

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#42342: Wine64 segfaults (5.12/staging)

[Leo Prikler]

We are currently at wine 6.8/6.6-staging and from my own estimates my
fix proved useful.