[Bug 40516] New: Office 2013 programs crash after wine-staging update from 1.9.7 to 1.9.8

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

Bug ID: 40516
           Summary: Office 2013 programs crash after wine-staging update
                    from 1.9.7 to 1.9.8
           Product: Wine-staging
           Version: 1.9.8
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
                CC: [e-mail], [e-mail],
                    [e-mail]
      Distribution: ---

Created attachment 54321
  --> https://bugs.winehq.org/attachment.cgi?id=54321
PowerPoint2013x32 Fedora 23 x64 Wine Staging 1.9.8 Traceafter crash

I've just managed to get Office 2013 working and after updating wine-staging
today Office tools are suddenly stopped working. PowerPoint only runs from time
to time but only in safe mode. Logs from Excel, Word and PowerPoint attached.

Fedora 23 64bit
wine-1.9.8 (Staging)

[Bug 40516] Office 2013 programs crash after wine-staging update from 1.9.7 to 1.9.8

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

--- Comment #1 from [e-mail] ---
Created attachment 54322
  --> https://bugs.winehq.org/attachment.cgi?id=54322
MSWord2013x32 Fedora 23 x64 Wine Staging 1.9.8 Trace after crash

[Bug 40516] Office 2013 programs crash after wine-staging update from 1.9.7 to 1.9.8

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

--- Comment #2 from [e-mail] ---
Created attachment 54323
  --> https://bugs.winehq.org/attachment.cgi?id=54323
Excel2013x32 Fedora 23 x64 Wine Staging 1.9.8 Trace after crash

[Bug 40516] Office 2013 programs crash after wine-staging update from 1.9.7 to 1.9.8

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

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
       Distribution|---                         |Fedora

[Bug 40516] Office 2013 programs crash after wine-staging update from 1.9.7 to 1.9.8

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

[e-mail] changed:

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

--- Comment #3 from [e-mail] ---
Unhandled exception: unimplemented function
webservices.dll.WsCreateServiceProxyFromTemplate called in 32-bit code
(0x7b43f30e).

[Bug 40516] Office 2013 programs crash after wine-staging update from 1.9.7 to 1.9.8

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

--- Comment #4 from Sebastian Lackner  ---
WsCreateServiceProxyFromTemplate has been implemented in the meantime (and is
present in 1.9.9 or later). Does the issue still occur?

[Bug 40516] Office 2013 programs crash after wine-staging update from 1.9.7 to 1.9.8

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

--- Comment #5 from [e-mail] ---
Unfortunately, I needed to uninstall all Office applications. I am trying to
install it again but without success. Following error occurs:

err:msi:ITERATE_Actions Execution halted, action L"StartServices" returned 1627

wine-1.9.16 (Staging)

I couldn't find anything about this problem.
Should I create a separate bug for it?

[Bug 40516] Office 2013 programs crash after wine-staging update from 1.9.7 to 1.9.8

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

[e-mail] changed:

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

--- Comment #6 from [e-mail] ---
(In reply to bystrzak14 from comment #5)
> Unfortunately, I needed to uninstall all Office applications. I am trying to
> install it again but without success. Following error occurs:
>
> err:msi:ITERATE_Actions Execution halted, action L"StartServices" returned
> 1627
>
> wine-1.9.16 (Staging)
>
> I couldn't find anything about this problem.
> Should I create a separate bug for it?

Could you test newer wine-staging if it doest still work a new bug report would
be good, but you also would need to do regressions testing.