https://bugs.winehq.org/show_bug.cgi?id=39146
Bug ID: 39146 Summary: Msiexec fails to use next cabinet file in media table (CDROM_SyncCache error) Product: Wine Version: 1.7.48 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: msi Assignee: wine-bugs@winehq.org Reporter: mattmill30@googlemail.com Regression SHA1: 597c5f9c4b35c7645d916cd687cede42fd331d0e Distribution: Debian
Created attachment 52171 --> https://bugs.winehq.org/attachment.cgi?id=52171 WINEDEBUG=+all,-relay extract
During installation of proplusww.msi, a part of the Microsoft Office 2013 installer, via direct invocation of msiexec, the second Cabinet file is mishandled, resulting in an installation failure and rollback.
At lines 11-24, the installer is seen accessing ProPsWW.CAB twice, then following the MEDIA table lookup, at lines 981-988 it changes focus to ProPsWW2.CAB but only accesses it once.
During a successful install on 1.7.22, the WINEDEBUG for both CAB files read similarly. The ISO was mounted on /dev/loop0, during both successful and unsuccessful installations.
I don't have the 1.7.22 WINEDEBUG, but if absolutely necessary I can re-generate it.
In addition, at lines 1194-1195 a CDROM_SyncCache (ISO) error occurs. I don't know whether the 1.7.22 WINDEBUG contained this.
I haven't had time to perform a bisect, but since 1.7.22 a change was made in 1.7.45 to the handling of CABs and so I have highlighted the commit which I anticipate is the cause of the issue.
I haven't investigated any changes between 1.7.22 and 1.7.48 to the cdrom module.
https://bugs.winehq.org/show_bug.cgi?id=39146
--- Comment #1 from Matthew Millar mattmill30@googlemail.com --- To clarify the 1.7.22 WINEDEBUG recorded two accesses to ProPsWW2.CAB, whilst in 1.7.48 ProPsWW2.CAB is only accessed once.
https://bugs.winehq.org/show_bug.cgi?id=39146
Matthew Millar mattmill30@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #52171|WINEDEBUG=+all,-relay |1.7.48 description|extract |WINEDEBUG=+all,-relay | |extract
https://bugs.winehq.org/show_bug.cgi?id=39146
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression CC| |hans@meelstraat.net, | |sebastian@fds-team.de Severity|blocker |normal
https://bugs.winehq.org/show_bug.cgi?id=39146
--- Comment #2 from Sebastian Lackner sebastian@fds-team.de --- To make sure that the commit you pointed out is really the right one, please try to compile Wine with this patch reverted. If not possible, I fear you'll have to do a full bisect to be sure.
https://bugs.winehq.org/show_bug.cgi?id=39146
Matthew Millar mattmill30@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://profile.microsoft.c | |om/RegSysProfileCenter/wiza | |rd.aspx?wizid=ae0653e5-0b00 | |-41d5-b3f4-1a7d5ea4b9c8&lci | |d=2057
--- Comment #3 from Matthew Millar mattmill30@googlemail.com --- I've attached a URL to download the Microsoft Office 2013 Trial.
This issue was experienced on the 64bit version installer. I anticipate the issue will be present on the 32bit aswell, since MSIs aren't compiled against architecture specific DLLs.
I won't have time to complete a testing or a bisect before 1.8 is released. Since this is the only blocker for successful installation of Microsoft Office, someone else may wish to perform the testing.
I'm working on instructions for the manual installation sequence of the MSIs, which will be attached to the 64bit Microsoft Office 2013 installer AppDB page - https://appdb.winehq.org/objectManager.php?sClass=version&iId=28170.
https://bugs.winehq.org/show_bug.cgi?id=39146
Matthew Millar mattmill30@googlemail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #52171|1.7.48 |wine64 1.7.48 description|WINEDEBUG=+all,-relay |WINEDEBUG=+all,-relay |extract |extract
https://bugs.winehq.org/show_bug.cgi?id=39146
--- Comment #4 from Hans Leidekker hans@meelstraat.net --- (In reply to Matthew Millar from comment #3)
I've attached a URL to download the Microsoft Office 2013 Trial.
This issue was experienced on the 64bit version installer. I anticipate the issue will be present on the 32bit aswell, since MSIs aren't compiled against architecture specific DLLs.
I won't have time to complete a testing or a bisect before 1.8 is released. Since this is the only blocker for successful installation of Microsoft Office, someone else may wish to perform the testing.
I'm working on instructions for the manual installation sequence of the MSIs, which will be attached to the 64bit Microsoft Office 2013 installer AppDB page - https://appdb.winehq.org/objectManager.php?sClass=version&iId=28170.
If I do this on Windows:
cd d:\proplusr.ww msiexec /i proplusrww.msi
(32-bit installer) I get an error. Even if it worked on Wine at some point we can't support this manual installation method. And it should no longer be necessary either.
https://bugs.winehq.org/show_bug.cgi?id=39146
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #5 from winetest@luukku.com ---
https://appdb.winehq.org/objectManager.php?sClass=version&iId=28170.
If I do this on Windows:
cd d:\proplusr.ww msiexec /i proplusrww.msi
(32-bit installer) I get an error. Even if it worked on Wine at some point we can't support this manual installation method. And it should no longer be necessary either.
Is this then wontfix? Somehow already fixed?
https://bugs.winehq.org/show_bug.cgi?id=39146
--- Comment #6 from Hans Leidekker hans@meelstraat.net --- (In reply to winetest from comment #5)
https://appdb.winehq.org/objectManager.php?sClass=version&iId=28170.
If I do this on Windows:
cd d:\proplusr.ww msiexec /i proplusrww.msi
(32-bit installer) I get an error. Even if it worked on Wine at some point we can't support this manual installation method. And it should no longer be necessary either.
Is this then wontfix? Somehow already fixed?
The steps described here are a workaround for the Office 2013 installer, which may have been useful when Wine didn't support it. It regressed, but the steps never worked on Windows, and now Wine can install Office 2013 (note that we're talking about the classic or MSI version of the installer).
I think we can close this as wontfix.
https://bugs.winehq.org/show_bug.cgi?id=39146
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com, | |dimesio@earthlink.net
https://bugs.winehq.org/show_bug.cgi?id=39146
--- Comment #7 from winetest@luukku.com --- (In reply to Hans Leidekker from comment #6)
The steps described here are a workaround for the Office 2013 installer, which may have been useful when Wine didn't support it. It regressed, but the steps never worked on Windows, and now Wine can install Office 2013 (note that we're talking about the classic or MSI version of the installer).
I think we can close this as wontfix.
https://bugs.winehq.org/show_bug.cgi?id=39146
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED
--- Comment #8 from Rosanne DiMesio dimesio@earthlink.net --- Marking WONTFIX per comment 6.
https://bugs.winehq.org/show_bug.cgi?id=39146
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #9 from Austin English austinenglish@gmail.com --- Closing.