March 2009 - Wine-Bugs - list.winehq.org

[Bug 16946] New: Calling CloseServiceHandle() multiple times on same client side service handle corrupts heap
by wine-bugs＠winehq.org March 19, 2021

March 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=16946 Summary: Calling CloseServiceHandle() multiple times on same client side service handle corrupts heap Product: Wine Version: 1.1.12 Platform: Other URL: http://www.nbc.com/Video/NBCDirectInstaller.exe OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, I've seen this some time ago but forgot about it until encountering it again recently while investigating bug 16626 (this is follow up bug). Prerequisite: --- snip --- $ rm -rf ~/.wine $ winetricks -q wmp10 dotnet20 mdac28 $ wine NBCDirectInstaller.exe --- snip --- The installer uses managed (.NET) wrapper for SCM to fetch a list of current services using EnumServicesStatus(). First call to EnumServicesStatus() to query for buffer size and second time to get the real list. Although M$ .NET Framework error handling is somewhat questionable (it doesn't even check for failure on first call), it's actually Wine's management of client side service handles that causes the breakage. --- snip --- ... 0009:Call advapi32.OpenSCManagerW(00000000,00000000,00000004) ret=03f72620 0009:trace:service:OpenSCManagerW ((null),(null),0x00000004) 0009:trace:service:sc_handle_alloc sc_handle type=0 -> 0x1b1fc0 ... 0013:trace:service:svcctl_OpenSCManagerW ((null), (null), 4) ... 0009:trace:service:OpenSCManagerW returning 0x1b1fc0 (access : 0x00000004) 0009:Ret advapi32.OpenSCManagerW() retval=001b1fc0 ret=03f72620 ... 0009:Call advapi32.EnumServicesStatusW(001b1fc0,00000030,00000003,00000000,00000000,0032f32c,0032f328,0032f324) ret=03f726df 0009:fixme:service:EnumServicesStatusW 0x1b1fc0 type=30 state=3 (nil) 0 0x32f32c 0x32f328 0x32f324 0009:Ret advapi32.EnumServicesStatusW() retval=00000000 ret=03f726df 0009:Call KERNEL32.GetLastError() ret=03f726e5 0009:Ret KERNEL32.GetLastError() retval=00000005 ret=03f726e5 0009:Call KERNEL32.LocalAlloc(00000000,00000000) ret=04248243 0009:Ret KERNEL32.LocalAlloc() retval=03ec9988 ret=04248243 0009:Call advapi32.EnumServicesStatusW(001b1fc0,00000030,00000003,03ec9988,00000000,0032f32c,0032f328,0032f324) ret=03f726df 0009:fixme:service:EnumServicesStatusW 0x1b1fc0 type=30 state=3 0x3ec9988 0 0x32f32c 0x32f328 0x32f324 0009:Ret advapi32.EnumServicesStatusW() retval=00000000 ret=03f726df 0009:Call KERNEL32.GetLastError() ret=03f726e5 0009:Ret KERNEL32.GetLastError() retval=00000005 ret=03f726e5 ... 0009:Call advapi32.CloseServiceHandle(001b1fc0) ret=007aa722 0009:trace:service:CloseServiceHandle 0x1b1fc0 ... 0009:trace:service:sc_handle_destroy_manager destroying SC Manager 0x1b1fc0 0009:Ret advapi32.CloseServiceHandle() retval=00000001 ret=007aa722 ... --- snip --- Releasing the same client handle again: --- snip --- 0009:Call advapi32.CloseServiceHandle(001b1fc0) ret=007aa722 0009:trace:service:CloseServiceHandle 0x1b1fc0 0009:Call rpcrt4.NdrClientInitializeNew(0032ef8c,0032f06c,60376640,00000000) ret=60366f60 0009:Ret rpcrt4.NdrClientInitializeNew() retval=0032f06c ret=60366f60 0009:Call rpcrt4.NdrGetBuffer(0032f06c,00000018,00000000) ret=60366fbe 0009:err:rpc:I_RpcGetBuffer no binding 0009:Call KERNEL32.RaiseException(000006a6,00000000,00000000,00000000) ret=60b21399 0009:trace:seh:raise_exception code=6a6 flags=0 addr=0x7b844f6c ip=0x7b844fef tid=0009 0009:trace:seh:raise_exception eax=7b82cca9 ebx=7b8c3940 ecx=00000000 edx=00000010 esi=0032ee90 edi=0032ee10 0009:trace:seh:raise_exception ebp=0032edf8 esp=0032ed94 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000246 0009:trace:seh:call_stack_handlers calling handler at 0x60366cec code=6a6 flags=0 0009:trace:seh:call_stack_handlers handler at 0x60366cec returned 1 0009:trace:seh:call_stack_handlers calling handler at 0x6036266f code=6a6 flags=0 0009:Call rpcrt4.I_RpcExceptionFilter(000006a6) ret=60360fdd 0009:Ret rpcrt4.I_RpcExceptionFilter() retval=00000001 ret=60360fdd 0009:trace:seh:__regs_RtlUnwind code=6a6 flags=2 0009:trace:seh:__regs_RtlUnwind calling handler at 0x7bc3b2ec code=6a6 flags=2 0009:trace:seh:__regs_RtlUnwind handler at 0x7bc3b2ec returned 1 0009:trace:seh:__regs_RtlUnwind calling handler at 0x60366cec code=6a6 flags=2 0009:Call rpcrt4.NdrFreeBuffer(0032f06c) ret=60366e7f 0009:Ret rpcrt4.NdrFreeBuffer() retval=00000000 ret=60366e7f 0009:trace:seh:__regs_RtlUnwind handler at 0x60366cec returned 1 0009:Ret advapi32.CloseServiceHandle() retval=00000000 ret=007aa722 --- snip --- Even if RPC code correctly detects invalid SCM handles, the latter sc_handle_free() will eventually corrupt heap which will later lead to breakage. This needs to be avoided at all costs. Second allocation returns garbage sub block due to corrupted heap lists, causing exception. --- snip --- ... 0009:Call ntdll.RtlAllocateHeap(00110000,00000000,0000001c) ret=79e78360 0009:Ret ntdll.RtlAllocateHeap() retval=001b1fc0 ret=79e78360 0009:Call KERNEL32.GetLastError() ret=79e71862 0009:Ret KERNEL32.GetLastError() retval=000006a6 ret=79e71862 0009:Call ntdll.RtlTryEnterCriticalSection(0013cedc) ret=79e74811 0009:Ret ntdll.RtlTryEnterCriticalSection() retval=00000001 ret=79e74811 0009:Call KERNEL32.GetLastError() ret=79e783fb 0009:Ret KERNEL32.GetLastError() retval=000006a6 ret=79e783fb 0009:Call ntdll.RtlAllocateHeap(00110000,00000000,0000003c) ret=79e78360 0009:Ret ntdll.RtlAllocateHeap() retval=03ec9988 ret=79e78360 0009:Call KERNEL32.GetLastError() ret=79e71862 0009:Ret KERNEL32.GetLastError() retval=000006a6 ret=79e71862 0009:Call KERNEL32.InitializeCriticalSection(03ec9998) ret=79e7a501 0009:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7bc450bd ip=0x7bc450bd tid=0009 0009:trace:seh:raise_exception info[0]=00000000 0009:trace:seh:raise_exception info[1]=00001796 0009:trace:seh:raise_exception eax=00001796 ebx=7bc9bd90 ecx=7bc9bd90 edx=00110078 esi=00110070 edi=0032f0e4 0009:trace:seh:raise_exception ebp=0032efe8 esp=0032ef80 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010206 0009:trace:seh:call_stack_handlers calling handler at 0x7a322c04 code=c0000005 flags=0 --- snip --- --- snip dlls/advapi32/service.c --- BOOL WINAPI CloseServiceHandle( SC_HANDLE hSCObject ) { struct sc_handle *obj; DWORD err; TRACE("%p\n", hSCObject); if (hSCObject == NULL) { SetLastError(ERROR_INVALID_HANDLE); return FALSE; } obj = (struct sc_handle *)hSCObject; __TRY { err = svcctl_CloseServiceHandle(&obj->server_handle); } __EXCEPT(rpc_filter) { err = map_exception_code(GetExceptionCode()); } __ENDTRY sc_handle_free( obj ); // <---- will eventually corrupt heap! if (err != ERROR_SUCCESS) { SetLastError(err); return FALSE; } return TRUE; } --- snip dlls/advapi32/service.c --- Change the way how client side service handles are managed to avoid heap corruption and allow for multiple service handle close calls. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 8

[Bug 16626] New: NBC Direct installer requires installation of Windows Installer 3.1 redist
by wine-bugs＠winehq.org March 19, 2021

March 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=16626 Summary: NBC Direct installer requires installation of Windows Installer 3.1 redist Product: Wine Version: 1.1.11 Platform: PC URL: http://www.nbc.com/Video/NBCDirectInstaller.exe OS/Version: Linux Status: NEW Keywords: dotnet, download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com CC: focht(a)gmx.net, yolande(a)haneder.biz Created an attachment (id=18188) --> (http://bugs.winehq.org/attachment.cgi?id=18188) terminal output in git Continuing from bug 12477, NBC installer doesn't yet work. Prereq's: $ rm -rf ~/.wine $ winetricks -q wmp10 dotnet20 mdac28 $ wine NBCDirectInstaller.exe Fails with an error box: SetupManager Error 'Failed to update Select Dialog resources from an external resource file. Please verify that the SetupManagerResource.resx files resides beside executable and is valid. Error details: No access to memory location OK Anastasius suggested to file the bug, saying it probably affects more dotnet apps. Terminal output attached. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 12

[Bug 10467] New: Making Microsoft .NET 2.0 to work in wine, based on example app FastMD5 1.4 for NET 2.0
by wine-bugs＠winehq.org March 19, 2021

March 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=10467 Summary: Making Microsoft .NET 2.0 to work in wine, based on example app FastMD5 1.4 for NET 2.0 Product: Wine Version: CVS/GIT Platform: PC URL: http://www.paehl.de/english.php OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-dotnet AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, this bug id exists for the sole purpose of showing my little journey of getting .NET 2.0 to work in wine. This topic does *NOT* cover the MONO project in any way. The windows version of MONO is covered by other bug reports. DISCLAIMER: This is just a first step which aims at major show stoppers. There are *many* issues left when it comes to managed (JIT) vs. unmanaged (native) API code bridging. To iron out all the bugs, many different applications are needed which cover the whole range of .NET Framework. I randomly chose a simple .NET 2.0 app which uses plain system.windows.forms stuff (no fancy controls/interop). --- snip --- http://www.paehl.de/fastmd5_net20.zip FASTMD5 create very fast with low CPU use a MD5 hash. Required .NET 1.1 or 2.0 --- snip --- Just as foreword: yes, it plain sucks to debug mixed code in wine (managed + unmanaged) because the tools required don't work reliable (or at all) due to several wine bugs/design problems. Prerequisite: successful installation of .NET 2.0 Framework and wine-0.9.49 (or GIT) ---------- If you start .NET apps they will fail with stack overflows and some exceptions thrown. The exception type tells us what we are dealing with: 0xe0434f4d For the uninitiated: this an exception type exclusively thrown by .NET common language runtime (CLR). Using my specially hacked wine to run tools like windbg one can get a raw estimate by looking at native method callstack: --- snip --- 0:000> sxe clr .. 0:000> .load clr20\sos.dll .. 0:000> g .. 0:000> kb ChildEBP RetAddr Args to Child WARNING: Stack unwind information not available. Following frames may be wrong. 0034efb8 79f97065 e0434f4d 00000001 00000001 KERNEL32!RaiseException+0x78 0034f018 7a0945a4 00a11cb4 00000000 00000000 mscorwks!RaiseTheExceptionInternalOnly+0x226 0034f0dc 02fa364b 00000000 0000007f 0034f138 mscorwks!JIT_Throw+0xd0 0034f1d8 79e88f63 00000000 0012e0f8 0034f22c 0x2fa364b 0034f1f8 79e88f63 00000000 00000000 0016b200 mscorwks!CallDescrWorker+0x33 0034f210 79e88ee4 0034f2e8 00000002 0034f2b0 mscorwks!CallDescrWorker+0x33 .. --- snip --- JIT code is at 0x2fa364b which transfers managed exceptions using mscorwks!JIT_Throw() to native code/OS. Lets look at CLR exception info... --- snip --- 0:000> !PrintException Exception object: 00a11cb4 Exception type: System.TypeInitializationException Message: The type initializer for 'System.Globalization.TextInfo' threw an exception. InnerException: <none> StackTrace (generated): <none> StackTraceString: <none> HResult: 80131534 --- snip --- And the managed code callstack... --- snip --- 0:000> !ClrStack OS Thread Id: 0xf (0) ESP EIP 0034f040 7b8414d8 [HelperMethodFrame: 0034f040] 0034f0e4 02fa364b System.Globalization.TextInfo.GetNativeTextInfo(Int32) 0034f114 02fa3511 System.Globalization.TextInfo.get_InvariantNativeTextInfo() 0034f140 02fa193d System.String.Compare(System.String, Int32, System.String, Int32, Int32, System.StringComparison) 0034f16c 02fa15a1 System.Security.Util.URLString.PreProcessForExtendedPathRemoval(System.String, Boolean) 0034f184 02fa10b0 System.AppDomainSetup.NormalizePath(System.String, Boolean) 0034f1a4 02fa06d6 System.AppDomainSetup.SetupDefaultApplicationBase(System.String) 0034f1bc 02fa02cc System.AppDomain.SetupFusionStore(System.AppDomainSetup) 0034f1d4 02fa01fa System.AppDomain.SetupDomain(Boolean, System.String, System.String) 0034f42c 79e88f63 [GCFrame: 0034f42c] 0034f9e0 79e88f63 [DebuggerClassInitMarkFrame: 0034f9e0] --- snip --- Some native method call in GetNativeTextInfo() seems to be the culprit. For many (string) resource based stuff to work, a unicode OS casing table is required. The table for the invariant version is built from external .NLS file. To make story short: wine does not ship the default case mapping table for unicode characters: "l_intl.nls". This is a "must" requirement and failure results in early TypeInitializationException while setting up default application domain. Short fix: copy the file from your windows system32 directory to wine system32. Long run fix: let wine generate/install this file. Not a big deal. Now simple .NET _console_ based apps (like "Hello World") will work. --------------------------------------- Stay tuned, more goodies to come ... Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 109

[Bug 15437] New: Company of Heroes Opposing Fronts: Installer fails
by wine-bugs＠winehq.org March 19, 2021

March 19, 2021

http://bugs.winehq.org/show_bug.cgi?id=15437 Summary: Company of Heroes Opposing Fronts: Installer fails Product: Wine Version: 1.1.5 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: xvachon(a)gmail.com Created an attachment (id=16303) --> (http://bugs.winehq.org/attachment.cgi?id=16303) log Installation of the game is not possible. Exception EAccessViolation error in module GameInst.exe happens. According to test data the game had to be installed from a Windows installation in order to be played. A log is attached. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 66

[Bug 12099] New: .NET Framework 1.1 installer requires loadperf. dll in case of AeDebug -> Auto=0 (unhandled exception dialog)
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=12099 Summary: .NET Framework 1.1 installer requires loadperf.dll in case of AeDebug -> Auto=0 (unhandled exception dialog) Product: Wine Version: CVS/GIT Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=11486) --> (http://bugs.winehq.org/attachment.cgi?id=11486) example patch to add loadperf.dll and simple UnloadPerfCounterTextStringsW stub preventing .NET 1.1 installer exception Hello, VS.NET 7.x installers modify AeDebug which results in error message box from .NET Framework 1.1 installer due to an unhandled exception. With default AeDebug Auto=1 and standalone .NET 1.1 installation you won't notice it because this exception doesn't affect overall "success" result of installer. You can capture output from console to see winedbg actually spawned. VS.NET 7.x installers add/modify the following JIT debugging keys: --- snip --- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger Auto: 1 -> 0 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger Default: cordbg.exe !a 0x%x8 --- snip --- Extract from .msi file: --- snip --- _FldbVs7eve_RegFile_887_00017.3643236F_FC70_11D3_A536_0090278A1BB8 2 SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug Auto 0 _VS_Debugging___VS7JIT_____X86.3643236F_FC70_11D3_A536_0090278A1BB8) .. --- snip --- You can simulate the behaviour on clean ~/.wine if you manually set AeDebug/Auto=0 (default is 1) and then execute the standalone .NET 1.1 installer. --- snip --- 002d:Call KERNEL32.lstrlenA(0034f55c "2008-03-17 21:20:25\t\tStarting\tUninstalling performance counters\r\n") ret=79e88b92 .. 002d:Call KERNEL32.LoadLibraryA(79e61310 "loadperf.dll") ret=79e907ed 002d:Ret KERNEL32.LoadLibraryA() retval=00000000 ret=79e907ed 002d:Call KERNEL32.GetLastError() ret=79e907f9 002d:Ret KERNEL32.GetLastError() retval=0000007e ret=79e907f9 002d:Call KERNEL32.RaiseException(c06d007e,00000000,00000001,0034f960) ret=79e9082c 002d:trace:seh:raise_exception code=c06d007e flags=0 addr=0x7b8419a0 002d:trace:seh:raise_exception info[0]=0034f910 002d:trace:seh:raise_exception eax=7b82c3e9 ebx=7b8af3e4 ecx=00000000 edx=0034f904 esi=0034f904 edi=0034f880 002d:trace:seh:raise_exception ebp=0034f868 esp=0034f804 cs=0073 ds=007b es=007b fs=0033 gs=003b flags=00200212 002d:trace:seh:call_stack_handlers calling handler at 0x402518 code=c06d007e flags=0 .. 002d:Call KERNEL32.UnhandledExceptionFilter(0034f350) ret=7c34c456 wine: Unhandled exception 0xc06d007e at address 0x7b8419a0 (thread 002d), starting debugger... 002d:Call user32.MessageBoxA(00000000,0034efd8 "Unhandled exception 0xc06d007e at address 0x7b8419a0.\nDo you wish to debug it?",7b8a3e47 "Exception raised",00000014) ret=7b841deb --- snip --- The message box is shown with the option to dismiss the exception or to debug it. This can be pretty confusing to users who have no knowledge how to deal with this. Well, actually this exception should never occur. Wine can prevent this problem by providing a simple loadperf.dll and UnloadPerfCounterTextStringsW stub. Output after patch: --- snip --- 0041:Ret KERNEL32.LoadLibraryA() retval=607d0000 ret=79e907ed 0041:Call KERNEL32.InterlockedExchange(79e96fa8,607d0000) ret=79e9083e 0041:Ret KERNEL32.InterlockedExchange() retval=00000000 ret=79e9083e 0041:Call KERNEL32.GetProcAddress(607d0000,79e919b4 "UnloadPerfCounterTextStringsW") ret=79e908c4 0041:Ret KERNEL32.GetProcAddress() retval=607d8808 ret=79e908c4 0041:Call loadperf.UnloadPerfCounterTextStringsW(0034f9d0 L"u \"ASP.NET_1.1.4322\"",00000001) ret=79e86e64 0041:fixme:loadperf:UnloadPerfCounterTextStringsW (L"u \"ASP.NET_1.1.4322\"", 1): stub! 0041:Ret loadperf.UnloadPerfCounterTextStringsW() retval=00000000 ret=79e86e64 --- snip --- Please add this dll and the UnloadPerfCounterTextStringsW stub. The attached patch is provided as example to quickly validate the problem solution. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 13

[Bug 11990] New: Script and Field Lists in FileMaker Pro are blank
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=11990 Summary: Script and Field Lists in FileMaker Pro are blank Product: Wine Version: 0.9.57. Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dempsey(a)weirdfish.net Created an attachment (id=11316) --> (http://bugs.winehq.org/attachment.cgi?id=11316) Manage Databases Comparison I've installed FileMaker Advanced 9 fine using the latest Wine but when trying to view both fields and scripts it shows all the lines, but doesn't show the text which should be showing the name. I guess the problem occurs in all three places as they use the same control for : Field Listing in Manage Database Script Listing in Manage Scripts Script Steps in Edit Script http://magicbadger.com/dump/images/wine/FM_Manage_Database.png http://magicbadger.com/dump/images/wine/FM_Manage_Scripts.png http://magicbadger.com/dump/images/wine/FM_Edit_Script.png -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 7

[Bug 13463] New: 000
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=13463 Summary: 000 Product: WineHQ Bugzilla Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P5 Component: bugzilla-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: maty1206(a)maryanlinux.com Wine can't uninstall the trial of Filemaker Pro. Please, improve this feature. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 6

[Bug 14844] New: Filemaker 9- freezes when loading .fmx plugins
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=14844 Summary: Filemaker 9- freezes when loading .fmx plugins Product: WineHQ Apps Database Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: appdb-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mosborne(a)ashs.school.nz Filemaker 9 runs perfectly in Wine until it tries to load plugins, such as Troi_*.fmx Normally these extensions are (I think) located in the Application data folder in windows so Wine might be looking for them in the wrong place. Ideas? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 12

[Bug 12356] New: FileMaker 8.5 and 9 crash after a few second on startup
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=12356 Summary: FileMaker 8.5 and 9 crash after a few second on startup Product: Wine Version: 0.9.58. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winedbg AssignedTo: wine-bugs(a)winehq.org ReportedBy: mihael.krauth(a)gmail.com FileMaker 8.5 and 9 crash after a few second on startup, just afer displaying the splash screen. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 6

[Bug 14963] New: Filemaker pro 8.5 apps crash easily (version 6.0 didn't)
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=14963 Summary: Filemaker pro 8.5 apps crash easily (version 6.0 didn't) Product: Wine Version: 1.0.0 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: julien.puydt(a)laposte.net Created an attachment (id=15570) --> (http://bugs.winehq.org/attachment.cgi?id=15570) Crash trace A small app (named rech_pb.exe) to query a database "written" with filemaker pro 8.5 shows empty dropdown menus, and can crash pretty easily when used ; it shows many : fixme:ole:OleQueryLinkFromData (0x13a448),stub! and many : fixme:font:SetMapperFlags (0x8258, 0x00000000): stub - harmless An older version of the same app "written" with filemaker pro 6.0 works correctly, but shows many : fixme:ole:OleQueryLinkFromData (0x13a448),stub! so I guess those warnings are pretty harmless, but the "harmless" ones aren't that much. See the attached log of a crash of the newer version. Hope that helps. PS: I'm using debian unstable's 1.0.0-1 package, in case the precision can help PS2: I'm probably tech-savvy enough to install svn+patch if needed -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 7