https://bugs.winehq.org/show_bug.cgi?id=48999
Bug ID: 48999 Summary: Filemaker Advanced 18 crashes on startup Product: Wine Version: 5.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: julien.arnaud@sib-retail.com Distribution: ---
Created attachment 66970 --> https://bugs.winehq.org/attachment.cgi?id=66970 Crash dump
Installation of Filemaker Advanced 18 went well, but when trying to run it, the program craches with the attached dump.
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #1 from julien.arnaud@sib-retail.com --- Installing the winbind packet (providing ntlm_auth) on the host gets me a little bit further, but Filemaker still crashes. It seems to request the presence of wine-gecko.
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #2 from julien.arnaud@sib-retail.com --- Created attachment 66971 --> https://bugs.winehq.org/attachment.cgi?id=66971 Updated crash dump
https://bugs.winehq.org/show_bug.cgi?id=48999
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|5.0-rc3 |5.0 Keywords| |dotnet CC| |focht@gmx.net
--- Comment #3 from Anastasius Focht focht@gmx.net --- Hello julien,
the backtraces show that MS .NET Framework is installed and used. Make sure you follow the procedure for dealing with native .NET, that is uninstalling Wine-Mono, apply fixups etc. to avoid broken WINEPREFIX. It is advised to use 'winetricks' for this, which takes care of many things.
In case of .NET, the console output is more useful than the actual backtrace created by Wine crash reporting tool. Usually it shows the managed (CLR) backtrace. Please attach the full output from start of the app until the CLR exception.
Regards
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #4 from julien.arnaud@sib-retail.com --- Hi,
I've been using winetricks to install .NET I'm a little bit further, after installing wine-gecko, the related error went away. Now the following attachment is displayed is logged by wine.
It seems to be related to "HLSL compiler"
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #5 from julien.arnaud@sib-retail.com --- Created attachment 66972 --> https://bugs.winehq.org/attachment.cgi?id=66972 HLSL related logs
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #6 from Anastasius Focht focht@gmx.net --- Hello julien,
--- snip --- 0051:err:d3dcompiler:compile_shader HLSL shader parsing failed. 0051:err:ntdll:vDbgPrintExWithPrefix 65: MIL FAILURE: Unexpected HRESULT 0x88760b59 in caller: intermediate rendering error 0051:err:ntdll:vDbgPrintExWithPrefix 65: MIL FAILURE: Unexpected HRESULT 0x88760b59 in caller: The render thread failed unexpectedly. wine: Unhandled exception 0xe0434352 in thread 31 at address 000000007B02DAE6 (thread 0031), starting debugger... --- snip ---
this could be bug 45871 ("Several .NET 4.7 WPF applications crash with HLSL shader parsing failure when using builtin 'd3dcompiler_47.dll'")
Does 'winetricks -q d3dcompiler_47' help?
Regards
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #7 from julien.arnaud@sib-retail.com --- Hi again,
Thanks for the quick reply. Yes it does help as the program seems to run now. Though as soon as I try to create/open a database, it crashes (it did not get that far a few minutes ago).
Should I close this bug and other another one ?
Attached are the new backtraces.
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #8 from julien.arnaud@sib-retail.com --- Created attachment 66973 --> https://bugs.winehq.org/attachment.cgi?id=66973 Crash log upon database opening/creation
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #9 from Anastasius Focht focht@gmx.net --- Hello julien,
well the backtrace is not very useful. Always attach both, the backtrace _and_ full console output up to the crash.
If the database functionality is not working it could due to missing ADO.NET dependencies (mdac28, jet40 via winetricks).
Regards
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #10 from julien.arnaud@sib-retail.com --- I'm sorry, here is the console attached. I'll look into your last recommendations.
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #11 from julien.arnaud@sib-retail.com --- Created attachment 66974 --> https://bugs.winehq.org/attachment.cgi?id=66974 Console database opening
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #12 from julien.arnaud@sib-retail.com --- The installation of mdac28, jet40 did not seem to make a difference. The console logs being identical.
https://bugs.winehq.org/show_bug.cgi?id=48999
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Component|-unknown |imm32 Summary|Filemaker Advanced 18 |FileMaker Advanced 18 (.NET |crashes on startup |4.6 app) crashes when | |trying to create/open a | |database Keywords| |download URL| |https://web.archive.org/web | |/20200423140034/https://fmd | |l.filemaker.com/esd/fmpa_18 | |.0.3.317_x64.exe Status|UNCONFIRMED |RESOLVED
--- Comment #13 from Anastasius Focht focht@gmx.net --- Hello julien,
ok, I can reproduce the crash.
I've created stable download links to 32-bit and 64-bit FM18 via Internet Archive:
https://web.archive.org/web/20200423140034/https://fmdl.filemaker.com/esd/fm...
https://web.archive.org/web/20200423140653/https://fmdl.filemaker.com/esd/fm...
---
Looks like you're hitting bug 31157 ("Multiple programs (Filemaker Pro 12, 19 Trial, MyDiff) crash opening a sample solution ('ImmAssociateContext' should only generate 'WM_IME_SETCONTEXT' if window has focus)").
I've analysed that problem six years ago and proposed a solution. Sadly it's still in "staging" area of Wine (https://github.com/wine-staging/wine-staging/tree/master/patches/imm32-messa...).
Since you don't want to be bothered of building custom Wine from source I suggest you permanently switch to use Wine-Staging as default. Saves you some hassle in the long run. Also for me less bug reports to deal with ;-)
https://wiki.winehq.org/Download -> your distro -> 'winehq-staging'
$ sha1sum fmpa_18.0.3.317_x* 4539cf921beb0a19704df52dc223e01524c4bdb8 fmpa_18.0.3.317_x32.exe 94e56140cf0118abbb662bb73921e9bb6f664257 fmpa_18.0.3.317_x64.exe
$ du -sh fmpa_18.0.3.317_x* 283M fmpa_18.0.3.317_x32.exe 295M fmpa_18.0.3.317_x64.exe
$ wine --version wine-5.6-352-g36a553c5be
Regards
*** This bug has been marked as a duplicate of bug 31157 ***
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #14 from julien.arnaud@sib-retail.com --- Hi Anastasius,
Thanks a lot, you've been of great help. I'll look into the procedure for substituting wine by wine-staging.
Have a nice day
https://bugs.winehq.org/show_bug.cgi?id=48999
--- Comment #15 from julien.arnaud@sib-retail.com --- I can confirm that using wine-5.6 (Staging) allow Filemaker Pro 18 Advanced to run properly. Thanks again.
https://bugs.winehq.org/show_bug.cgi?id=48999
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #16 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Closing Duplicate.