[Bug 45832] New: Windower (Final Fantasy XI tool) Security Token Exception
https://bugs.winehq.org/show_bug.cgi?id=45832 Bug ID: 45832 Summary: Windower (Final Fantasy XI tool) Security Token Exception Product: Wine Version: 3.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: conmanx360(a)gmail.com Distribution: --- Created attachment 62292 --> https://bugs.winehq.org/attachment.cgi?id=62292 Terminal output of Windower Windower crashes before starting with a security token error. Don't know enough about Mono to fix it, but any explanation on what's wrong would be helpful. Can do different wine debug traces if necessary. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 Connor McAdams <conmanx360(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |conmanx360(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com --- Comment #1 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Hi, could you please add downloadlink to exact version you used I found something here http://windower.net/ but I get a different error when using mono. Thanks in advance -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #2 from Connor McAdams <conmanx360(a)gmail.com> --- http://files.windower.net/5/core/test/windower.portable.zip This is the portable version, so it doesn't need the installer. I figured that would eliminate any sort of issue that's only installer related. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 Connor McAdams <conmanx360(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Windower (Final Fantasy XI |Windower 5 beta (Final |tool) Security Token |Fantasy XI tool) Security |Exception |Token Exception -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #3 from Connor McAdams <conmanx360(a)gmail.com> --- (In reply to Connor McAdams from comment #2)
http://files.windower.net/5/core/test/windower.portable.zip
This is the portable version, so it doesn't need the installer. I figured that would eliminate any sort of issue that's only installer related.
Also, forgot to mention, this is the v5 version of Windower that's currently in beta. They said it should be more compatible with Wine than v4, but, it doesn't seem to work so far. Sorry for not specifying that. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |http://files.windower.net/5 | |/core/test/windower.portabl | |e.zip Keywords| |download --- Comment #4 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Hi thanks for reporting back I still get a different error when trying to start in a new WINEPREFIX . However, the application seems to need PresentationFramework so Mono is not going to work here anyway. I ran in a WINEPREFIX where I had dotnet472 installed and then it crashes apparently because of bug in dwmapi. Disabling dwmapi makes a window appear that is unfortunately black. However, using wine-staging 3.15 and disabling dwampi makes the window come up, telling me i don`t have Final Fantasy installed To summarize: Could you try winetricks -q dotnet472 WINEDLLOVERRIDES=dwmapi=d wine windower.exe launch (if window is black, try Staging) I post hack hereafter that prevents the app from crashing, when dwmapi is not disabled: diff --git a/dlls/dwmapi/dwmapi_main.c b/dlls/dwmapi/dwmapi_main.c index 0e6ba3bed1..bf8c670328 100644 --- a/dlls/dwmapi/dwmapi_main.c +++ b/dlls/dwmapi/dwmapi_main.c @@ -82,7 +82,7 @@ HRESULT WINAPI DwmExtendFrameIntoClientArea(HWND hwnd, const MARGINS* margins) { FIXME("(%p, %p) stub\n", hwnd, margins); - return E_NOTIMPL; + return 0;E_NOTIMPL; } /********************************************************************** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #5 from Connor McAdams <conmanx360(a)gmail.com> --- (In reply to Louis Lenders from comment #4)
Hi thanks for reporting back
I still get a different error when trying to start in a new WINEPREFIX .
However, the application seems to need PresentationFramework so Mono is not going to work here anyway.
I ran in a WINEPREFIX where I had dotnet472 installed and then it crashes apparently because of bug in dwmapi. Disabling dwmapi makes a window appear that is unfortunately black. However, using wine-staging 3.15 and disabling dwampi makes the window come up, telling me i don`t have Final Fantasy installed
To summarize:
Could you try
winetricks -q dotnet472
WINEDLLOVERRIDES=dwmapi=d wine windower.exe launch
(if window is black, try Staging)
I post hack hereafter that prevents the app from crashing, when dwmapi is not disabled:
diff --git a/dlls/dwmapi/dwmapi_main.c b/dlls/dwmapi/dwmapi_main.c index 0e6ba3bed1..bf8c670328 100644 --- a/dlls/dwmapi/dwmapi_main.c +++ b/dlls/dwmapi/dwmapi_main.c @@ -82,7 +82,7 @@ HRESULT WINAPI DwmExtendFrameIntoClientArea(HWND hwnd, const MARGINS* margins) { FIXME("(%p, %p) stub\n", hwnd, margins);
- return E_NOTIMPL; + return 0;E_NOTIMPL; }
/**********************************************************************
So, I'm getting a black screen, and tried staging like you said. Staging seems to have made it worse. Now it just crashes when moving the screen, and otherwise is just an image of whatever was on the screen before. It crashes with references to PresentationFramework. I can't find an ubuntu package for 3.15 staging, maybe it's an issue with my compilation, or Wine-staging. Do you know the specific wine-staging patches that fix the black screen? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #6 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Created attachment 62348 --> https://bugs.winehq.org/attachment.cgi?id=62348 Staging patch fixing black window Do
you know the specific wine-staging patches that fix the black screen? It looks like the Multimonitor patch (attached as one diff here)
In current git however it seems to crash after openeningswindow, maybe there is a regression since last days??? I` ll have a look later -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #7 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Created attachment 62350 --> https://bugs.winehq.org/attachment.cgi?id=62350 bunch of hacks I did a bit more testing and i think the staging-patch is not needed after all. Maybe the window was black because the app crashed. I got something running with a bunch of hacks attached here. Maybe you could try the hacks, and if it works for you, each bug should go into it`s own bugreport i guess. Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #8 from Connor McAdams <conmanx360(a)gmail.com> --- (In reply to Louis Lenders from comment #7)
Created attachment 62350 [details] bunch of hacks
I did a bit more testing and i think the staging-patch is not needed after all. Maybe the window was black because the app crashed. I got something running with a bunch of hacks attached here. Maybe you could try the hacks, and if it works for you, each bug should go into it`s own bugreport i guess.
Regards
I may still be doing something wrong... I don't know. I put all the hacks you had in the second post into my wine build, compiled it, and still what I get is a window that's transparent and basically copies whatever it was started on top of. Moving the Window causes it to crash. I can attach my terminal here in a second. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #9 from Connor McAdams <conmanx360(a)gmail.com> --- Created attachment 62356 --> https://bugs.winehq.org/attachment.cgi?id=62356 Terminal of crash with transparent window. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #10 from Louis Lenders <xerox.xerox2000x(a)gmail.com> ---
I may still be doing something wrong... I don't know.
No i guess not, I found out that I had a native d3dcompiler_47.dll lying around in my ~/.wine/drive_c/windows/system32 When I run with forcing d3dcompiler_47.dll to builtin I get a similar output as you: 0031:fixme:d3dcompiler:make_assignment Check for casts in the lhs. 0031:err:d3dcompiler:compile_shader HLSL shader parsing failed. 0031:fixme:wer:WerRegisterMemoryBlock (0x5752e40 6144) stub 0031:fixme:wer:WerRegisterMemoryBlock (0x5752df4 4) stub 0031:err:ntdll:vDbgPrintExWithPrefix 65: MIL FAILURE: Unexpected HRESULT 0x88760b59 in caller: intermediate rendering error 0031:err:ntdll:vDbgPrintExWithPrefix 65: MIL FAILURE: Unexpected HRESULT 0x88760b59 in caller: The render thread failed unexpectedly. AFAICT looks like yet another bug... Anyway, if you could put a native d3dcompiler_47.dll (i copied it from my windowspartition) into ~/.wine/drive_c/windows/system32 i think that particular error should be gone (hopefully) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #11 from Connor McAdams <conmanx360(a)gmail.com> --- Created attachment 62357 --> https://bugs.winehq.org/attachment.cgi?id=62357 Terminal of crash after adding in d3d compiler. Okay, added the .dll file and set it to native. Now it's got a different crash. Looks like it might be related to .net version being 4.0 something? Not sure. I did winetricks and installed 4.7.2 like you said earlier. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #12 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Created attachment 62364 --> https://bugs.winehq.org/attachment.cgi?id=62364 hacks + staging multimonitor patch Hi Connor, I started all over again testing in fresh wineprefix, to avoid running into side-issues. I think the staging multi-monitor patch is needed after all (it`s included in attached patch which contains also the rest of the hacks). I got it running by - apply the attached patch - remove ~/.wine //rm -rf ~/.wine or use new WINEPREFIX - winetricks -q dotnet45 - winetricks win7 unzip ~/Downloads/windower.portable.zip wine windower.exe -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #13 from Connor McAdams <conmanx360(a)gmail.com> --- (In reply to Louis Lenders from comment #12)
Created attachment 62364 [details] hacks + staging multimonitor patch
Hi Connor, I started all over again testing in fresh wineprefix, to avoid running into side-issues.
I think the staging multi-monitor patch is needed after all (it`s included in attached patch which contains also the rest of the hacks).
I got it running by
- apply the attached patch
- remove ~/.wine //rm -rf ~/.wine or use new WINEPREFIX
- winetricks -q dotnet45
- winetricks win7
unzip ~/Downloads/windower.portable.zip
wine windower.exe
Awesome! applied the patch and the program now runs properly. The the application crashes internally (meaning not a Wine crash, it reports it's own crash) after launching the game, so that's something to report to the developers of Windower, I'd guess. Thanks for the help. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #14 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (In reply to Connor McAdams from comment #13)
Thanks for the help.
Thanks for testing. AFAICT that counts then up to 5 wine-bugs to solve... Let`s address this one for the dwmapi issue. I think just returning S_OK for DwmExtendFrameIntoClientArea seems quite harmless, I`ll send a patch for that. I`ll also open bugreport for other issue in shell32 (SHGetStockIconInfo) As for the other two hacks for user32.QueryDisplayConfig and user32.GetDisplayConfigBufferSizes: I don`t know how and if they are related to the Multimonitor patch from Staging. It might be better to wait until Multimonitor patch is upstream somehow, and then see how the app behaves. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet Status|UNCONFIRMED |NEW Component|mscoree |dwmapi Ever confirmed|0 |1 Summary|Windower 5 beta (Final |Windower 5 beta (FF XI |Fantasy XI tool) Security |tool) crash: Unhandled |Token Exception |Exception: | |System.NotImplementedExcept | |ion at | |Windower.UI.Views.RootView. | |OnSourceInitialized | |(DwmExtendFrameIntoClientAr | |ea should return S_OK) --- Comment #15 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Change title and set component to dotnet, the Mono error is not useful to track down imo, the app uses PresentationFramework so Mono won`t work Output after dotnet45 installed: 0030:fixme:advapi:RegisterEventSourceW ((null),L".NET Runtime"): stub 0030:fixme:advapi:ReportEventW (0xcafe4242,0x0001,0x0000,0x00000402,(nil),0x0001,0x00000000,0x513dde4,(nil)): stub 0030:err:eventlog:ReportEventW L"Application: windower.exe\nFramework Version: v4.0.30319\nDescription: The process was terminated due to an unhandled exception.\nException Info: System.NotImplementedException\nStack:\n at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32, IntPtr)\n at Windower.UI.Views.Ro"... 0030:fixme:advapi:DeregisterEventSource (0xcafe4242) stub Unhandled Exception: System.NotImplementedException: The method or operation is not implemented. at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo) at Windower.UI.Views.RootView.OnSourceInitialized(EventArgs e) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 --- Comment #16 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- This should be fixed by: https://source.winehq.org/git/wine.git/commit/a1f5a7699e7138a76cb9dc50e3cda1... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |a1f5a7699e7138a76cb9dc50e3c | |da1c8c5ffae57 --- Comment #17 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- yes it is fixed -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #18 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.17. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |3.0.x -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45832 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.0.x |--- --- Comment #19 from Michael Stefaniuc <mstefani(a)winehq.org> --- Removing the 3.0.x milestone from bug fixes included in 3.0.5. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org