https://bugs.winehq.org/show_bug.cgi?id=43852
Bug ID: 43852 Summary: Monkey Island Special Edition Collection: White screen and crash when starting Monkey1.exe Product: Wine Version: 2.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: cweiske@cweiske.de Distribution: ---
Created attachment 59408 --> https://bugs.winehq.org/attachment.cgi?id=59408 wine terminal output
After successfully installing "Monkey Island Special Edition Collection" from DVD (bug #43851), running Monkey1.exe fails:
1. The main display (or wine's virtual desktop) only shows a white screen 2. Terminal shows some errors, the last ones are below 3. Wine's in-built backtrace collector does not seem to work
err:ole:COMPOBJ_DllList_Add couldn't load in-process dll L"C:\windows\system32\XAudio2_4.dll" err:ole:CoGetClassObject no class object {03219e78-5bc3-44d1-b92e-f63d89cc6526} could be created for context 0x1 wine: Unhandled page fault on read access to 0x00000000 at address 0x441192 (thread 0009), starting debugger...
https://bugs.winehq.org/show_bug.cgi?id=43852
Christian Weiske cweiske@cweiske.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu
https://bugs.winehq.org/show_bug.cgi?id=43852
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- Sounds like Bug 43852, but that's supposed to be fixed.
Does it work in a clean wineprefix? Or does it work with "winetricks xact"?
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #2 from Fabian Maurer dark.shadow4@web.de --- Sorry, of course I mean Bug 26833.
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #3 from Christian Weiske cweiske@cweiske.de --- I completely removed ~/.wine/ if that's what you mean with "wineprefix" before installing this game.
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #4 from Fabian Maurer dark.shadow4@web.de --- Yes, WINEPREFIX sets your .wine folder. There isn't a demo by any chance?
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #5 from Fabian Maurer dark.shadow4@web.de --- Also, does it work with "winetricks xact"?
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #6 from Christian Weiske cweiske@cweiske.de --- It seems to be installed already:
$ winetricks xact Executing w_do_call xact xact already installed, skipping
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #7 from Fabian Maurer dark.shadow4@web.de --- Does "winetricks --force xact" help?
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #8 from Christian Weiske cweiske@cweiske.de --- No, forcing the xact installation does not help.
The OLE error is gone, but "err:rpc:I_RpcGetBuffer no binding" and the page fault are still there.
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #9 from Fabian Maurer dark.shadow4@web.de --- If that fixes the
no class object {03219e78-5bc3-44d1-b92e-f63d89cc6526} could be created for context 0x1
that means the original issue is fixed, no? Can you provide a new log with that configuration?
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #10 from Christian Weiske cweiske@cweiske.de --- Created attachment 59438 --> https://bugs.winehq.org/attachment.cgi?id=59438 wine terminal output after winetricks --force xact
New log.
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #11 from Fabian Maurer dark.shadow4@web.de --- Can you attach a log including backtrace?
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #12 from Christian Weiske cweiske@cweiske.de --- When trying to use the backtrace view in the application crash window, nothing happens even when waiting half an hour ("Loading detailled information, please wait...").
When running the application through winedbg, the program complains that "a required security module cannot be activated". It links to http://www.securom.com/message.asp?m=module&c=2000&l=ge
Note that the application does run fine with wine when using a nodvd crack. So it's maybe a problem with SecuROM.
https://bugs.winehq.org/show_bug.cgi?id=43852
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #13 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-4.2?
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #14 from Christian Weiske cweiske@cweiske.de --- Created attachment 63768 --> https://bugs.winehq.org/attachment.cgi?id=63768 backtrace wine 4.3
With wine 4.3, the white screen and the crash still occurs. What we get now is a proper backtrace that I attach here.
https://bugs.winehq.org/show_bug.cgi?id=43852
Christian Weiske cweiske@cweiske.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #59408|0 |1 is obsolete| |
--- Comment #15 from Christian Weiske cweiske@cweiske.de --- Created attachment 63769 --> https://bugs.winehq.org/attachment.cgi?id=63769 wine 4.3 terminal output
https://bugs.winehq.org/show_bug.cgi?id=43852
Christian Weiske cweiske@cweiske.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #59438|0 |1 is obsolete| |
--- Comment #16 from Christian Weiske cweiske@cweiske.de --- Created attachment 63770 --> https://bugs.winehq.org/attachment.cgi?id=63770 wine 4.3 terminal output after winetricks --force xact
https://bugs.winehq.org/show_bug.cgi?id=43852
rtentser@yandex.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rtentser@yandex.ru
--- Comment #17 from rtentser@yandex.ru --- Have similar problem, but it looks more like https://bugs.winehq.org/show_bug.cgi?id=37676.
https://bugs.winehq.org/show_bug.cgi?id=43852
--- Comment #18 from rtentser@yandex.ru --- Looks like this bug was fixed: the game starts with 'winetricks d3dcompiler_47' (which is a workaround for #37676) in latest git (6.0rc4.r17.g784cb2060ab), but not with 5.0.3.
https://bugs.winehq.org/show_bug.cgi?id=43852
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |z.figura12@gmail.com Resolution|--- |FIXED
--- Comment #19 from Zebediah Figura z.figura12@gmail.com --- (In reply to rtentser from comment #18)
Looks like this bug was fixed: the game starts with 'winetricks d3dcompiler_47' (which is a workaround for #37676) in latest git (6.0rc4.r17.g784cb2060ab), but not with 5.0.3.
Marking fixed then; thanks for testing.
https://bugs.winehq.org/show_bug.cgi?id=43852
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #20 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 6.0-rc5.