http://bugs.winehq.org/show_bug.cgi?id=36697
Bug ID: 36697 Summary: PlayOn won't install Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: lyriclover@gmail.com
Created attachment 48743 --> http://bugs.winehq.org/attachment.cgi?id=48743 Backtrace log for PlayOn error
I paid for a lifetime of PlayOn before Windows crashed on me for the last time. Now I'm strictly a Linux Lady :-) Wine won't successfully open PlayOn It starts to install but then fails.
http://bugs.winehq.org/show_bug.cgi?id=36697
Allison lyriclover@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lyriclover@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=36697
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE Summary|PlayOn won't install |PlayOn won't install in a | |64-bit WINEPREFIX
--- Comment #1 from Bruno Jesus 00cpxxx@gmail.com --- Hi, this is a duplicate of a known issue. Please use a 32-bit WINEPREFIX and try again, also be sure to use the latest development version of wine (currently 1.7.19) when you submit new bugs. The problem you are facing was fixed in wine 1.7.6.
*** This bug has been marked as a duplicate of bug 24611 ***
http://bugs.winehq.org/show_bug.cgi?id=36697
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |matteo.mystral@gmail.com
--- Comment #2 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Bruno Jesus from comment #1)
The problem you are facing was fixed in wine 1.7.6.
Notice though that the log mentions wine-1.7.18.
http://bugs.winehq.org/show_bug.cgi?id=36697
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Version|unspecified |1.7.18 URL| |http://www.playon.tv/downlo | |ads/playon/ Keywords| |download, Installer, win64 CC| |focht@gmx.net Resolution|DUPLICATE |--- Ever confirmed|0 |1 Summary|PlayOn won't install in a |64-bit InstallShield engine |64-bit WINEPREFIX |COM server 'ISBEW64.exe' | |occasionally crashes on OLE | |teardown (32-bit | |InstallShield based | |installers in 64-bit | |WINEPREFIX)
--- Comment #3 from Anastasius Focht focht@gmx.net --- Hello folks,
actually bug 24611 had multiple issues mixed together. I didn't explicitly mention this there since that bug was targeting WoW64 COM registry views synchronization (the main blocker).
Your backtrace highlights a shutdown race that occasionally happens in 64-bit InstallShield engine COM server which talks over standard marshaller to the 32-bit installer part.
The crash is harmless in the end as it happens in OLE server teardown phase (typelib/refcounting) but of course it scares people because it triggers 'winedbg'.
--- snip --- Unhandled exception: page fault on read access to 0x00000007 in 64-bit code (0x00007f11f0b1e5ec). Register dump: rip:00007f11f0b1e5ec rsp:000000000023f760 rbp:000000000004ef80 eflags:00010246 ( R- -- I Z- -P- ) rax:000000000005f850 rbx:0000000000000007 rcx:0000000000000007 rdx:0000000000000008 rsi:0000000000000000 rdi:0000000000000000 r8:0000000000000000 r9:000000000023f5a8 r10:000000000023f578 r11:0000000000000000 r12:000000000004efa0 r13:000000000005f0f0 r14:0000000000000000 r15:0000000000000000 ... Backtrace: =>0 0x00007f11f0b1e5ec VariantClear+0xdc() in oleaut32 (0x000000000004ef80) 1 0x00007f11f0b0c875 in oleaut32 (+0x4c874) (0x000000000004ef80) 2 0x00007f11f0b057ad in oleaut32 (+0x457ac) (0x0000000000000000) 3 0x0000000000401440 in isbew64 (+0x143f) (0x000000000041b960) 4 0x0000000000406486 in isbew64 (+0x6485) (0x000000000041b960) ... 0x00007f11f0b1e5ec VariantClear+0xdc in oleaut32: movzwl (%rbx),%eax Modules: Module Address Debug info Name (56 modules) PE 400000- 420000 Export isbew64 ELF 7b800000- 7bc73000 Dwarf kernel32<elf> -PE 7b820000- 7bc73000 \ kernel32 ELF 7be00000- 7c103000 Dwarf <wine-loader> ... Threads: process tid prio (all id:s are in hex) ... 0000002a (D) C:\users\lyriclover\Temp{336BCF94-D575-4E52-AA73-85C4B02D0543}\ISBEW64.exe 00000040 0 0000003e 0 0000002d 0 0000002b 0 <== --- snip ---
Anyway, your app needs .NET Framework 3.5 SP1 and Windows Media Player 9+
These prerequisites are not properly installed in 64-bit WINEPREFIX due to other known Wine bugs.
Even if .NET Framework installers report success in WoW64 environment (without 'winetricks') they are still broken in the end.
For WMP 9 you need a bi-arch installer because the installer detects WoW64 environment.
Various issues that only experts can properly diagnose and work around - it's not for the faint-hearted.
So yes, please use a 32-bit WINEPREFIX (WINEARCH=win32) to avoid all the mess.
I'll rechristen the bug because it still highlights a problem with Wine (albeit non-critical).
Regards
http://bugs.winehq.org/show_bug.cgi?id=36697
--- Comment #4 from Bruno Jesus 00cpxxx@gmail.com --- (In reply to Matteo Bruni from comment #2) (In reply to Anastasius Focht from comment #3)
Sorry for the rushed conclusion.
http://bugs.winehq.org/show_bug.cgi?id=36697
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW
--- Comment #5 from Anastasius Focht focht@gmx.net --- Hello Bruno,
--- quote --- Sorry for the rushed conclusion. --- quote ---
actually it was my fault to not clear this up earlier.
If you look at all the duplicates in bug 24611, almost every bug refers to the same crash/backtrace. The backtrace signature is very easy to recognize but technically unrelated to the main problem of bug 24611.
All dupes really suffered from bug 24611 before Wine 1.7.6 and it was easier to resolve them using the "marker" backtrace that accompanied the main problem.
Technically it's a different issue but explain that to the users :|
Regards
https://bugs.winehq.org/show_bug.cgi?id=36697
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |s.lopiano@gmail.com
--- Comment #6 from Nikolay Sivov bunglehead@gmail.com --- *** Bug 37733 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cruiseoveride@gmail.com
--- Comment #7 from Anastasius Focht focht@gmx.net --- *** Bug 37236 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |imwellcushtymelike@gmail.co | |m
--- Comment #8 from Anastasius Focht focht@gmx.net --- *** Bug 38794 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh@gmail.com
--- Comment #9 from Anastasius Focht focht@gmx.net --- *** Bug 39050 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |p.lemonnier1@free.fr
--- Comment #10 from Bruno Jesus 00cpxxx@gmail.com --- *** Bug 40647 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |robert.munteanu@gmail.com
--- Comment #11 from Bruno Jesus 00cpxxx@gmail.com --- *** Bug 29889 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wa2pux@gmail.com
--- Comment #12 from Rosanne DiMesio dimesio@earthlink.net --- *** Bug 41822 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |stevedonato@gmail.com
--- Comment #13 from Bruno Jesus 00cpxxx@gmail.com --- *** Bug 42143 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
--- Comment #14 from steve donato stevedonato@gmail.com --- the duplicate bug said it was fixed in wine 1.7.6. I'm running wine 1.9.23?
The other comment of the duplicate bug fixed said something about installing a new release of .net.
Am I missing something?
https://bugs.winehq.org/show_bug.cgi?id=36697
--- Comment #15 from Bruno Jesus 00cpxxx@gmail.com --- *** Bug 42178 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
--- Comment #16 from steve donato stevedonato@gmail.com --- How do you "use a 32-bit WINEPREFIX" ?
as suggested
https://bugs.winehq.org/show_bug.cgi?id=36697
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |_Wanderer_@outlook.com
--- Comment #17 from Jeff Zaroyko jeffz@jeffz.name --- *** Bug 42499 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
--- Comment #18 from Wanderer _Wanderer_@outlook.com --- The bug is still present in Wine 2.2. Until upgrading to 2.2, I used 1.6.2, which did not have this problem, also without using a 32-bit prefix.
https://bugs.winehq.org/show_bug.cgi?id=36697
--- Comment #19 from Wanderer _Wanderer_@outlook.com --- Created attachment 57387 --> https://bugs.winehq.org/attachment.cgi?id=57387 backtrace for the Far Cry 2 installer
https://bugs.winehq.org/show_bug.cgi?id=36697
--- Comment #20 from Nikolay Sivov bunglehead@gmail.com --- *** Bug 41646 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=36697
S. Christian Collins s_chriscollins@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |s_chriscollins@hotmail.com
https://bugs.winehq.org/show_bug.cgi?id=36697
C. Leu kle@bluewin.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kle@bluewin.ch
--- Comment #21 from C. Leu kle@bluewin.ch --- Hi to all
I don't know why this bug-report is linked to the 3Dmark06 benchmark program.
Whatever, the problems reported here no longer exist. All 32bit 3Dmark-installer are running great also in a 64bit Wine prefix!
I can confirm this for Wine 6.0 stable. The benchmarks 3Dmark03, 3Dmark05, 3Dmark06 including 3Dmark2001SE are installing and running all fine. (This should be also true for a 32bit prefix.)
3Dmark06 requires that native d3dcompiler_47.dll and d3dx9_28.dll are installed, winetricks -q d3dx9_28 and winetricks -q d3dcompiler_47. After this, 3Dmark06 runs fully error-free.
The only troublesome benchmark may be 3Dmark05 which doesn't starts properly because the "system information component" seems missing. However, it starts to work after 3Dmark06 is installed. So it looks that the "system information component" of 3Dmark06 is also functional in 3Dmark05.
With these tweaks, everything is working GREAT, especially if Gallium Nine (winetricks -q galliumnine) is installed. (It may bring similar performance to DX9VK).
Finally, from my point of view, this bug report can be closed. ;-)
https://bugs.winehq.org/show_bug.cgi?id=36697
--- Comment #22 from Ken Sharp imwellcushtymelike@gmail.com --- I doubt this is fixed.
https://bugs.winehq.org/show_bug.cgi?id=36697
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|http://www.playon.tv/downlo |https://web.archive.org/web |ads/playon/ |/20210302110846/http://dl15 | |.afterdawn.com/download/7a5 | |e997ae708ddd2f9550663dc4d40 | |cd/603e1ca1/n-z/PlayOnSetup | |.3.9.14.exe Status|NEW |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |09e98be24350a7a8306cc6cd730 | |2f94eae770afc Component|-unknown |rpc Summary|64-bit InstallShield engine |64-bit InstallShield engine |COM server 'ISBEW64.exe' |COM server 'ISBEW64.exe' |occasionally crashes on OLE |crashes or hangs (32-bit |teardown (32-bit |InstallShield based |InstallShield based |installers in 64-bit |installers in 64-bit |WINEPREFIX) |WINEPREFIX) |
--- Comment #23 from Anastasius Focht focht@gmx.net --- Hello folks,
the problems were indeed fixed some years ago. There were different manifestations of the problems with 64-bit InstallShield engine COM server 'ISBEW64.exe'.
* COM server crashes consistently at early point of installation (page fault or stack overflow) * COM server crashes at late point but not consistently (page fault or stack overflow) * COM server hangs/zombifies due to preceding unhandled exceptions
It varies between apps (linked duplicate tickets). The initial crash was definitely the most common visible symptom up to Wine 2.4
I tested several installers linked from the duplicate bug reports with Wine 2.x releases.
* https://web.archive.org/web/20210302122901/http://dl15.afterdawn.com/downloa...
* https://web.archive.org/web/20140407232928/http://www.downloads.netgear.com/...
* https://web.archive.org/web/20140822001235mp_/http://d1heja5wzvsadj.cloudfro...
Wine 2.0 - 2.4
--- snip --- fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x33f1dc L"C:\users\focht\Temp\{F11A34B6-CBA7-402B-B50E-65CFF56F31D7}\Disk1\data1.hdr" err:rpc:I_RpcReceive we got fault packet with status 0x3e6 fixme:ole:NdrClearOutParameters (0x33e4d0,0x7e150e7c,0x33e800): stub fixme:ole:NdrClearOutParameters (0x33e4d0,0x7e150ea6,0x33e6e4): stub fixme:ole:NdrClearOutParameters (0x33e4d0,0x7e150eaa,0x33e704): stub fixme:ole:NdrClearOutParameters (0x33e4d0,0x7e150ece,0x33e800): stub wine: Unhandled page fault on write access to 0x00000007 at address 0x7bc5bd3f (thread 005d), starting debugger... --- snip ---
Wine 2.5 - 2.9
--- snip --- fixme:ole:NdrClearOutParameters (0x33e260,0x7e14710e,0x33e59c): stub fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0x33f1dc L"C:\users\focht\Temp\{889CFF4A-1836-421C-A590-CC109D3653A0}\Disk1\data1.hdr" err:seh:setup_exception stack overflow 1680 bytes in thread 0070 eip 000000007bc9481c esp 0000000000750f80 stack 0x750000-0x751000-0x850000 --- snip ---
Wine 2.10 -> works for most app installers.
The following series of commits between Wine 2.9 and Wine 2.10 release were responsible for fixing the early crash.
* https://source.winehq.org/git/wine.git/commitdiff/5c81f8295e379bf09b51466eb3... ("rpcrt4: Store server thread handle in RpcServerProtseq.")
* https://source.winehq.org/git/wine.git/commitdiff/5c2083fd22d252c1d1c082d585... ("rpcrt4: Store listening pipe name in RpcConnection_np.")
* https://source.winehq.org/git/wine.git/commitdiff/10a6b33a93cd4ea33032077b8e... ("rpcrt4: Recreate listening pipe in rpcrt4_protseq_np_get_wait_array if needed.")
* https://source.winehq.org/git/wine.git/commitdiff/e98c7a59c26bdff7bad27e5864... ("rpcrt4: Wait for all active connections to be released before quiting server thread.")
* https://source.winehq.org/git/wine.git/commitdiff/09e98be24350a7a8306cc6cd73... ("rpcrt4: Wait for server threads to finish in RpcMgmtWaitServerListen.")
Unfortunately I've still encountered a small set of app installers which ran into hangs or stack overflows in 64-bit InstallShield engine process past Wine 2.10 release.
Example:
https://web.archive.org/web/20140822001235mp_/http://d1heja5wzvsadj.cloudfro...
Prerequisite: killing all (zombified) processes from previous runs and using a new WINEPREFIX.
Not every installer run resulted in a stack overflow which is a bit annoying.
I've identified another set of changes between Wine 3.0 and 3.1 release for fixing this problem. I will de-duplicate some linked bug reports as needed to document this.
$ wine --version wine-2.10
Regards
https://bugs.winehq.org/show_bug.cgi?id=36697
--- Comment #24 from C. Leu kle@bluewin.ch --- Thanks Anastasius Focht for this super detailed answer. Here follows a little addition to that topic.
The only MadOnion / Futuremark benchmark which cannot be directly installed at a 64bit Wine 6.0 prefix is 3DMark99 MAX. The installer crashes shortly after it's started. Maybe this is a different problem. And maybe this installer is 16bit and not 32bit (it really looks old).
My workaround was to extract (with 7zip) the content of the installer (it's effectively a ZIP based self-extractor) into a temporary 3DMark99MAX called directory. After that, the setup can be started properly and the installation finishes also correctly.
However, there is a warning (known problem) that Direct X 6.1 is not installed and therefore the program refuses to start. All mentioned tweaks don't work for me in a 64bit Wine 6.0 prefix. So for the moment the status of that program is garbage. ;-)
Will try this out in a 32bit Wine 6.0 prefix.
https://bugs.winehq.org/show_bug.cgi?id=36697
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #25 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 6.4.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla