[Bug 48044] New: wine64 err:msiexec:custom_action_server Failed to create custom action server pipe

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48044

Bug ID: 48044
           Summary: wine64 err:msiexec:custom_action_server Failed to
                    create custom action server pipe
           Product: Wine
           Version: 4.0.2
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: msi
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

I realise this has come up many time before (e.g. 45663, 45509, 45856), but I
am still seeing it on both 4.0 and 4.18-staging. I have verified that the
previous patch to address this (circa wine-3.15) has been applied in both
versions:

https://source.winehq.org/git/wine.git/blobdiff/6552ddaaa5c189db504e81a2360b...

It could be that I'm doing something wrong (I'm not a wine expert). I only have
the 64bit wine installed (as is the norm for centos/fedora), so have not tried
with a 32bit wine prefix.

Steps to reproduce:

rm -rf ~/.wine
wineboot
winetricks python27

Executing wine msiexec /i python-2.7.16.msi ALLUSERS=1
0030:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
0038:err:msiexec:custom_action_server Failed to create custom action server
pipe: 2

I have also seen it with a few other random installers too.

[Bug 48044] wine64 err:msiexec:custom_action_server Failed to create custom action server pipe

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48044

Zebediah Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Zebediah Figura  ---
Can you please try with the current development version? There's a chance
27a7952a8 may have fixed this.

[Bug 48044] wine64 err:msiexec:custom_action_server Failed to create custom action server pipe

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48044

--- Comment #2 from Daire  ---
Thanks Zebediah,

I actually had also tried wine 4.18 (which definitely includes those patches)
but got the same thing.

But now I've just tried installing the wine32 binaries & libs for v4.0.2 and
the same 64bit wineprefix is now getting past this... which I don't really
understand.

In both cases I was actually using a wine64 prefix. Let me do some more testing
to verify (I have been swapping lots of packages around).

Not having the 32bit libs packaged for EL/Fedora makes everything harder....

Daire

[Bug 48044] wine64 err:msiexec:custom_action_server Failed to create custom action server pipe

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48044

--- Comment #3 from Daire  ---
Yea so I think I had confused myself slightly. I had a 64bit wineprefix but was
essentially using "winetricks python27" with wine -> wine32.

Either way, the installer works fine with 32bit and fails with 64bit. This is
the case for 4.0.2 & 4.18 staging.

Daire

[Bug 48044] wine64 err:msiexec:custom_action_server Failed to create custom action server pipe

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48044

--- Comment #4 from Austin English  ---
To be clear, before it worked, you only had 64 bit wine, but no 32 bit, right?

If so, that's not supported.

[Bug 48044] wine64 err:msiexec:custom_action_server Failed to create custom action server pipe

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48044

--- Comment #5 from Daire  ---
Yes, it would not install with only the wine64 binaries and libs installed
(this is how EPEL & Fedora distribute it).

I was able to install with wine32 & libs installed along with the using a 64bit
wineprefix.

I thought the goal was to have it such that eventually, wine64 would be able
install and run 64bit only windows applications without wine32?

If that's not the case, then I wonder why many distros only provide the 64bit
version?

Daire

[Bug 48044] wine64 err:msiexec:custom_action_server Failed to create custom action server pipe

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48044

Zebediah Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #6 from Zebediah Figura  ---
(In reply to Daire from comment #5)
> Yes, it would not install with only the wine64 binaries and libs installed
> (this is how EPEL & Fedora distribute it).
>
> I was able to install with wine32 & libs installed along with the using a
> 64bit wineprefix.
>
> I thought the goal was to have it such that eventually, wine64 would be able
> install and run 64bit only windows applications without wine32?

No, that's never the case. We need system and library support for 32-bit code.
> If that's not the case, then I wonder why many distros only provide the
> 64bit version?

I don't know, but it's kind of pointless to do so.

I suspect many don't realize the needs of Wine and Win32 programs (cf. Ubuntu
dropping 32-bit support, and initially waving off Wine with "your 64-bit
programs will still work"). Even 64-bit programs almost always ship with 32-bit
installers, since otherwise they can't work on pure 32-bit Windows
installations (which, yes, still exist).

Anyway, resolving invalid since the installer works with a correct
configuration; please reopen if I've misread or there's still a bug here.

[Bug 48044] wine64 err:msiexec:custom_action_server Failed to create custom action server pipe

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48044

André H.  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED
                 CC|                            |[e-mail]

--- Comment #7 from André H.  ---
closing invalid