[Bug 47224] New: Wine-4.8 releases

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

Bug ID: 47224
           Summary: Wine-4.8 releases
           Product: Packaging
           Version: unspecified
          Hardware: x86
                OS: Mac OS X
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: wine-packages
          Assignee: [e-mail]
          Reporter: [e-mail]
                CC: [e-mail], [e-mail],
                    [e-mail]

The following happens for all Wine-4.8 packages, this doesn’t happen If I
compiled wine myself

0016:err:rpc:I_RpcReceive we got fault packet with status 0x3e6
0016:fixme:service:service_control_dispatcher failed to open service
L"PlugPlay"
000f:fixme:service:scmdatabase_autostart_services Auto-start service
L"PlugPlay" failed to start: 1053
001d:err:rpc:I_RpcReceive we got fault packet with status 0x3e6
001d:fixme:service:service_control_dispatcher failed to open service
L"Winedevice1"
000f:fixme:service:scmdatabase_autostart_services Auto-start service L"WineBus"
failed to start: 1053
0024:err:rpc:I_RpcReceive we got fault packet with status 0x3e6
0024:fixme:service:service_control_dispatcher failed to open service
L"Winedevice2"
000f:fixme:service:scmdatabase_autostart_services Auto-start service
L"MountMgr" failed to start: 1053
0009:err:winecfg:open_mountmgr failed to open mount manager err 2

This happens even if just using winecfg on a clean prefix, this doesn’t happen
on Wine-4.7 releases.

[Bug 47224] Wine-4.8 releases - Broken

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

Gcenx  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Wine-4.8 releases           |Wine-4.8 releases - Broken

[Bug 47224] Wine-4.8 releases - Broken

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

Gcenx  changed:

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

[Bug 47224] Wine-4.8 releases - Broken

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

--- Comment #1 from Gcenx  ---
Created attachment 64562
  --> https://bugs.winehq.org/attachment.cgi?id=64562
Wine-Staging-4.9 64Bit winecfg log

Same issue is also precent in the Wine-4.9 packages

I recreated the issue on my system by not having mingw installed.
If mingw is installed this issue doesn't happen

[Bug 47224] Wine-4.8/Wine-4.9 64Bit releases - Broken

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

Gcenx  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Hardware|x86                         |x86-64
            Summary|Wine-4.8 releases - Broken  |Wine-4.8/Wine-4.9 64Bit
                   |                            |releases - Broken

[Bug 47224] Wine-4.8/Wine-4.9 64Bit releases - Broken

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

Shadders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |richard.shadbolt@btinternet
                   |                            |.com

--- Comment #2 from Shadders  ---
Hi,
Yes, can confirm, WINE 64bit application operation fails, all 32bit programs
function.

https://bugzilla.redhat.com/show_bug.cgi?id=1713945

Only occurred since upgrade to wine 4.8 from wine 4.7, 25th May 2019.

Regards,
Shadders.

[Bug 47224] Wine-4.8/Wine-4.9 64Bit releases - Broken

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

--- Comment #3 from Gcenx  ---
(In reply to Shadders from comment #2)
> Hi,
> Yes, can confirm, WINE 64bit application operation fails, all 32bit programs
> function.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1713945
>
> Only occurred since upgrade to wine 4.8 from wine 4.7, 25th May 2019.
>
> Regards,
> Shadders.

Wine-4.8/4.9 would need to be recompiled with mingw installed at compile time,
for some reason everyone seems to think it’s a runtime dependancie it’s a build
dependancie as of Win-4.8 it shouldn’t be the case but until the issue is fixed
it’s more requires

[Bug 47224] Wine-4.8/Wine-4.9 64Bit releases - Broken

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

--- Comment #4 from Rosanne DiMesio  ---
(In reply to Shadders from comment #2)
> Only occurred since upgrade to wine 4.8 from wine 4.7, 25th May 2019.

Are you using the WineHQ packages or the distro ones? The WineHQ Linux packages
are all built with mingw support now.

[Bug 47224] Wine-4.8/Wine-4.9 64Bit releases - Broken

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

--- Comment #5 from Shadders  ---
(In reply to Rosanne DiMesio from comment #4)
> (In reply to Shadders from comment #2)
> Are you using the WineHQ packages or the distro ones? The WineHQ Linux
> packages are all built with mingw support now.

Hi,
I am using the distro packages - makes it easier to manage the PC installation
- single point source.

I have got around the issue by installing PlayOnLinux - and this allows me to
run the packages required after re-installation.

Thanks and regards,
Shadders.

[Bug 47224] WineHQ 64Bit macOS packages broken (built without mingw)

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

Rosanne DiMesio  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Wine-4.8/Wine-4.9 64Bit     |WineHQ 64Bit macOS packages
                   |releases - Broken           |broken (built without
                   |                            |mingw)

--- Comment #6 from Rosanne DiMesio  ---
(In reply to Shadders from comment #5)
> I am using the distro packages - makes it easier to manage the PC
> installation - single point source.

This is a packaging bug; if you are not using the WineHQ packages, your problem
does not belong here.

Changing the summary to clarify that this bug is for WineHQ macOS packages
only.

[Bug 47224] WineHQ 64Bit macOS packages broken (built without mingw)

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

--- Comment #7 from Rosanne DiMesio  ---
Bug 47275 has been reported fixed in 4.10; are the macOS WineHQ packages for
4.10 now working properly?

[Bug 47224] WineHQ 64Bit macOS packages broken (built without mingw)

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

--- Comment #8 from Gcenx  ---
While the mount issue is resolved in Wine-4.10 Winehq packages I would like
confirmation that mingw was added into the builder or not. As too many bugs are
happening when building without mingw.

Also while the bug was fixed within the Winehq packages I was also told from
someone who also builds wine regularly they still get the mounting issue when
passing —without-mingw.

I haven’t had chance to test building —without-mingw myself yet due to needing
my laptop today

[Bug 47224] WineHQ 64Bit macOS packages broken (built without mingw)

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

Rosanne DiMesio  changed:

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

--- Comment #9 from Rosanne DiMesio  ---
(In reply to Gcenx from comment #8)
> While the mount issue is resolved in Wine-4.10 Winehq packages I would like
> confirmation that mingw was added into the builder or not. As too many bugs
> are happening when building without mingw.

I don't maintain the macOS packages, so I can't say definitively what was done
in the builder. What I can say is that after extracting the macOS "portable"
packages  for 4.9 and 4.10, the /usr/lib/wine subdirectory for 4.10 includes
many files with just a dll extension that in 4.9 had a dll.so extension, and
the file command identifies those dll files as "PE32 executable (DLL) (console)
Intel 80386, for MS Windows" whereas the corresponding dll.so files in 4.9
return "Mach-O i386 bundle, flags:<NOUNDEFS|DYLDLINK|TWOLEVEL>". So clearly
something has changed in the build process.
> Also while the bug was fixed within the Winehq packages I was also told from
> someone who also builds wine regularly they still get the mounting issue
> when passing —without-mingw.
>
> I haven’t had chance to test building —without-mingw myself yet due to
> needing my laptop today

This bug is about the WineHQ packages, and those have been reported fixed.
Problems that occur when you build Wine yourself without mingw should be
reported separately as Wine bugs, not Packaging bugs.

[Bug 47224] WineHQ 64Bit macOS packages broken (built without mingw)

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

Rosanne DiMesio  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #10 from Rosanne DiMesio  ---
Closing fixed packaging bug.

[Bug 47224] WineHQ 64Bit macOS packages broken (built without mingw)

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

--- Comment #11 from Gcenx  ---
(In reply to Rosanne DiMesio from comment #9)
> This bug is about the WineHQ packages, and those have been reported fixed.
> Problems that occur when you build Wine yourself without mingw should be
> reported separately as Wine bugs, not Packaging bugs.

I only mentioned the other bug as you yourself mentioned the other bug. (I also
confirmed that without mingw the same issue occurs I posted into that bug)

But your right it does seem that the Winebuilder now has mingw installed.