wine-bugs February 2021

wine-bugs@winehq.org

1 participants
6834 discussions

[Bug 44907] New: BattlEye 'BEDaisy' kernel service crashes on unimplemented function ' fltmgr.sys.FltGetRoutineAddress'
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=44907 Bug ID: 44907 Summary: BattlEye 'BEDaisy' kernel service crashes on unimplemented function 'fltmgr.sys.FltGetRoutineAddress' Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: fltmgr Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, already mentioned in bug 44500 It seems the author of the BattlEye driver is actively working on it, adding new API dependencies/imports every week ;-) Prerequisite: * bug 44837 -> missing 'ntoskrnl.exe.Ps{Acquire,Release}ProcessExitSynchronization' * bug 44906 -> missing 'ntoskrnl.exe.ExfUnblockPushLock' There is now an additional one: --- snip --- $ WINEDEBUG=+seh,+relay,+ntoskrnl wine net start BEDaisy >>log.txt 2>&1 ... 0035:Call ntoskrnl.exe.MmGetSystemRoutineAddress(0065ecac) ret=008560ad ... 0035:Call KERNEL32.GetProcAddress(7ec00000,0011d528 "IoDriverObjectType") ret=7ec18587 0035:Ret KERNEL32.GetProcAddress() retval=7ec0700c ret=7ec18587 ... 0035:trace:ntoskrnl:MmGetSystemRoutineAddress L"IoDriverObjectType" -> 0x7ec0700c ... 0035:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=7ec0700c ret=008560ad ... 0035:Call KERNEL32.RaiseException(80000100,00000001,00000002,0065eb78) ret=f7dd1b0f 0035:trace:seh:raise_exception code=80000100 flags=1 addr=0x7b446c33 ip=7b446c33 tid=0035 0035:trace:seh:raise_exception info[0]=f7dd1b28 0035:trace:seh:raise_exception info[1]=f7dd228b wine: Call from 0x7b446c33 to unimplemented function fltmgr.sys.FltGetRoutineAddress, aborting --- snip --- $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe $ wine --version wine-3.5-106-g182c12c403 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.

2 5

[Bug 44497] New: BattlEye 'BEDaisy' kernel service crashes on unimplemented ntoskrnl.exe ObCallback ( object manager) functions
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=44497 Bug ID: 44497 Summary: BattlEye 'BEDaisy' kernel service crashes on unimplemented ntoskrnl.exe ObCallback (object manager) functions Product: Wine Version: 3.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 44496 The kernel driver uses object manager callbacks in order to implement process protection. * ObRegisterCallbacks * ObUnRegisterCallbacks * ObGetFilterVersion Example kernel driver code to show how the API is being used: https://github.com/Microsoft/Windows-driver-samples/tree/master/general/obc… --- quote --- ObCallback Callback Registration Driver The ObCallback sample driver demonstrates the use of registered callbacks for process protection. The driver registers control callbacks which are called at process creation. Design and Operation The sample exercises both the PsSetCreateProcessNotifyRoutineEx and the ObRegisterCallbacks routines. The first example uses the ObRegisterCallbacks routine and a callback to restrict requested access rights during a open process action. The second example uses the PsSetCreateProcessNotifyRoutineEx routine to reject a process creation by examining the command line. --- quote --- Another article: https://malwaretips.com/threads/av-self-protection-process-c-c.66200/ BattlEye 'BEDaisy' needs semi-stubs. Pure stubs returning 'STATUS_NOT_IMPLEMENTED' is not enough. The driver init routine will fail. * ObRegisterCallbacks -> return STATUS_SUCCESS (and fake handle) * ObUnRegisterCallbacks -> just empty stub is enough * ObGetFilterVersion -> return OB_FLT_REGISTRATION_VERSION Also mentioned in tps://bugs.winehq.org/show_bug.cgi?id=41039#c0 ("Virtualbox crashes with access violation, needs ntoskrnl.exe.FsRtlIsNameInExpression") although not the problem there. --- snip --- fixme:ntoskrnl:MmGetSystemRoutineAddress L"ObRegisterCallbacks" not found fixme:ntoskrnl:MmGetSystemRoutineAddress L"ObUnRegisterCallbacks" not found --- snip --- With these things fixed, the driver runs further - into next problems. $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe $ wine --version wine-3.1-193-g354fa7eb79 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.

2 6

[Bug 44500] New: BattlEye 'BEDaisy' kernel service crashes on unimplemented fltmgr.sys functions ( FltRegisterFilter, FltStartFiltering, FltUnregisterFilter)
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=44500 Bug ID: 44500 Summary: BattlEye 'BEDaisy' kernel service crashes on unimplemented fltmgr.sys functions (FltRegisterFilter, FltStartFiltering, FltUnregisterFilter) Product: Wine Version: 3.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: fltmgr Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 44499 The kernel driver uses multiple methods to implement process protection/supervision. * ObRegisterCallbacks * ObUnRegisterCallbacks * ObGetFilterVersion -> covered by bug 44497 * PsSetCreateProcessNotifyRoutineEx -> covered by bug 44499 * FltRegisterFilter * FltStartFiltering * FltUnregisterFilter BattlEye 'BEDaisy' needs semi-stubs. Pure stubs returning 'STATUS_NOT_IMPLEMENTED' is not enough. The driver init routine will fail. * FltRegisterFilter -> return STATUS_SUCCESS and some dummy handle as "out" * FltStartFiltering -> return STATUS_SUCCESS * FltUnregisterFilter -> just empty stub is enough (needed when driver unloads) With this and all previous bug reports fixed/worked around, the driver init routine runs to completion and the kernel service starts successfully. Proof: --- snip --- ... 0048:trace:winedevice:load_driver loading driver L"C:\\Program Files\\Common Files\\BattlEye\\BEDaisy.sys" ... 0048:trace:module:process_attach (L"BEDaisy.sys",(nil)) - END 0048:Ret KERNEL32.LoadLibraryW() retval=00780000 ret=7effaa20 ... 0048:trace:winedevice:load_driver_module L"C:\\Program Files\\Common Files\\BattlEye\\BEDaisy.sys": relocating from 0x400000 to 0x780000 ... 0048:Call driver init 0x7fdf6e (obj=0x11cb58,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") 0048:Call --- snip --- Map the driver image via Mdl in order to hot-patch. --- snip --- ... ntoskrnl.exe.IoAllocateMdl(00780000,00040409,00000000,00000000,00000000) ret=0080bf37 0048:trace:ntoskrnl:IoAllocateMdl (0x780000, 263177, 0, 0, (nil)) 0048:Call ntdll.RtlAllocateHeap(00110000,00000008,00000120) ret=7ecdf800 0048:Ret ntdll.RtlAllocateHeap() retval=0011cd38 ret=7ecdf800 0048:fixme:ntoskrnl:IoGetCurrentProcess () semi-stub 0048:Ret ntoskrnl.exe.IoAllocateMdl() retval=0011cd38 ret=0080bf37 0048:Call ntoskrnl.exe.MmProbeAndLockPages(0011cd38,00000000,00000001) ret=0080bf37 0048:fixme:ntoskrnl:MmProbeAndLockPages (0x11cd38, 0, 1): stub 0048:Ret ntoskrnl.exe.MmProbeAndLockPages() retval=0000003f ret=0080bf37 0048:Call ntoskrnl.exe.MmMapLockedPagesSpecifyCache(0011cd38,00000000,00000000,00000001,00000000,00000000) ret=0080bf37 0048:fixme:ntoskrnl:MmMapLockedPagesSpecifyCache (0x11cd38, 0, 0, 0x1, 0, 0): stub 0048:Call ntdll.RtlAllocateHeap(00110000,00000000,00040409) ret=7ece28a9 0048:Ret ntdll.RtlAllocateHeap() retval=0011d978 ret=7ece28a9 0048:Call KERNEL32.OpenProcess(001fffff,00000000,00000042) ret=7ece28d4 0048:Ret KERNEL32.OpenProcess() retval=00000040 ret=7ece28d4 0048:Call KERNEL32.ReadProcessMemory(00000040,00780000,0011d978,00040409,00000000) ret=7ece2907 0048:Ret KERNEL32.ReadProcessMemory() retval=00000001 ret=7ece2907 0048:Call KERNEL32.CloseHandle(00000040) ret=7ece2929 0048:Ret KERNEL32.CloseHandle() retval=00000001 ret=7ece2929 0048:fixme:ntoskrnl:MmMapLockedPagesSpecifyCache Success! 0048:Ret ntoskrnl.exe.MmMapLockedPagesSpecifyCache() retval=0011d978 ret=0080bf37 --- snip --- Manually resolve 'ntoskrnl.exe' and other module imports. Most activity is invisible from any trace log (walking in-memory lists, obfuscated strings). --- snip --- 0048:Call ntdll.NtQuerySystemInformation(0000000b,008100a0,00001400,0065f350) ret=008034e1 0048:Ret ntdll.NtQuerySystemInformation() retval=00000000 ret=008034e1 ... 0048:Call ntdll.NtQuerySystemInformation(0000000b,0065f39c,00000000,0065f398) ret=0080732b 0048:Ret ntdll.NtQuerySystemInformation() retval=c0000004 ret=0080732b 0048:Call ntoskrnl.exe.ExAllocatePool(00000000,00001400) ret=007fe2fc 0048:Call ntdll.RtlAllocateHeap(00110000,00000000,00001400) ret=7ece16d9 0048:Ret ntdll.RtlAllocateHeap() retval=008100a0 ret=7ece16d9 0048:trace:ntoskrnl:ExAllocatePoolWithTag 5120 pool 0 -> 0x8100a0 0048:Ret ntoskrnl.exe.ExAllocatePool() retval=008100a0 ret=007fe2fc 0048:Call ntdll.NtQuerySystemInformation(0000000b,008100a0,00001400,0065f398) ret=008034e1 0048:Ret ntdll.NtQuerySystemInformation() retval=00000000 ret=008034e1 ... --- snip --- Commit the changes to the memory image -> 'MmUnlockPages'. --- snip --- ... 0048:Call ntoskrnl.exe.MmUnlockPages(0011cd38) ret=0080bf37 0048:fixme:ntoskrnl:MmUnlockPages (0x11cd38): stub 0048:Call KERNEL32.OpenProcess(001fffff,00000000,00000042) ret=7ece2be8 0048:Ret KERNEL32.OpenProcess() retval=00000040 ret=7ece2be8 0048:Call KERNEL32.WriteProcessMemory(00000040,00780000,0011d978,00040409,00000000) ret=7ece2c17 0048:Ret KERNEL32.WriteProcessMemory() retval=00000001 ret=7ece2c17 0048:Call KERNEL32.CloseHandle(00000040) ret=7ece2c25 0048:Ret KERNEL32.CloseHandle() retval=00000001 ret=7ece2c25 0048:Call ntdll.RtlFreeHeap(00110000,00000000,0011d978) ret=7ece2c45 0048:Ret ntdll.RtlFreeHeap() retval=00000001 ret=7ece2c45 0048:fixme:ntoskrnl:MmUnlockPages Success! 0048:Ret ntoskrnl.exe.MmUnlockPages() retval=0000002b ret=0080bf37 0048:Call ntoskrnl.exe.IoFreeMdl(0011cd38) ret=0080bf37 0048:trace:ntoskrnl:IoFreeMdl 0x11cd38 0048:Call ntdll.RtlFreeHeap(00110000,00000000,0011cd38) ret=7ecdf8fa 0048:Ret ntdll.RtlFreeHeap() retval=00000001 ret=7ecdf8fa 0048:Ret ntoskrnl.exe.IoFreeMdl() retval=00000001 ret=0080bf37 ... --- snip --- Register object manager/process/mini driver callbacks and create driver symlinks. --- snip --- ... 0048:Call ntoskrnl.exe.ObGetFilterVersion() ret=0078c6be 0048:fixme:ntoskrnl:ObGetFilterVersion stub 0048:Ret ntoskrnl.exe.ObGetFilterVersion() retval=00000100 ret=0078c6be 0048:Call ntoskrnl.exe.KeInitializeMutex(00785020,00000000) ret=0079e1f6 0048:fixme:ntoskrnl:KeInitializeMutex stub: 0x785020, 0 0048:Ret ntoskrnl.exe.KeInitializeMutex() retval=00000038 ret=0079e1f6 0048:Call ntoskrnl.exe.IoCreateDevice(0011cb58,00000000,0065f1a8,00000022,00000000,00000000,0065f1e8) ret=007a2653 0048:trace:ntoskrnl:IoCreateDevice (0x11cb58, 0, L"\\Device\\BattlEye", 34, 0, 0, 0x65f1e8) ... 0048:Ret ntoskrnl.exe.IoCreateDevice() retval=00000000 ret=007a2653 0048:Call ntoskrnl.exe.IoCreateSymbolicLink(0065f1cc,0065f1a8) ret=007a2834 0048:trace:ntoskrnl:IoCreateSymbolicLink L"\\DosDevices\\BattlEye" -> L"\\Device\\BattlEye" 0048:Call ntdll.NtCreateSymbolicLinkObject(0065f064,000f0001,0065f04c,0065f1a8) ret=7ece06af 0048:Ret ntdll.NtCreateSymbolicLinkObject() retval=00000000 ret=7ece06af 0048:Ret ntoskrnl.exe.IoCreateSymbolicLink() retval=00000000 ret=007a2834 0048:Call ntoskrnl.exe.KeWaitForSingleObject(00785020,00000000,00000000,00000000,00000000) ret=007b8643 0048:fixme:ntoskrnl:KeWaitForSingleObject stub: 0x785020, 0, 0, 0, (nil) 0048:Ret ntoskrnl.exe.KeWaitForSingleObject() retval=c0000002 ret=007b8643 0048:Call ntdll.RtlInitUnicodeString(0065f0c8,00783a7c L"363220") ret=00794e44 0048:Ret ntdll.RtlInitUnicodeString() retval=0065f0c8 ret=00794e44 0048:Call ntoskrnl.exe.ObRegisterCallbacks(0065f0c4,00785040) ret=007b869d 0048:fixme:ntoskrnl:ObRegisterCallbacks : stub 0048:Ret ntoskrnl.exe.ObRegisterCallbacks() retval=00000000 ret=007b869d 0048:Call ntoskrnl.exe.KeReleaseMutex(00785020,00000000) ret=007a4ee7 0048:fixme:ntoskrnl:KeReleaseMutex stub: 0x785020, 0 0048:Ret ntoskrnl.exe.KeReleaseMutex() retval=c0000002 ret=007a4ee7 0048:Call ntoskrnl.exe.PsSetLoadImageNotifyRoutine(007817a0) ret=00797911 0048:fixme:ntoskrnl:PsSetLoadImageNotifyRoutine (0x7817a0) stub 0048:Ret ntoskrnl.exe.PsSetLoadImageNotifyRoutine() retval=00000000 ret=00797911 0048:Call ntoskrnl.exe.PsSetCreateThreadNotifyRoutine(007811c4) ret=0079e1fb 0048:fixme:ntoskrnl:PsSetCreateThreadNotifyRoutine stub: 0x7811c4 0048:Ret ntoskrnl.exe.PsSetCreateThreadNotifyRoutine() retval=00000000 ret=0079e1fb 0048:Call ntoskrnl.exe.memset(0065f108,00000000,00000038) ret=007b63ab 0048:Ret ntoskrnl.exe.memset() retval=0065f108 ret=007b63ab 0048:Call fltmgr.sys.FltRegisterFilter(0011cb58,0065f108,00785500) ret=007afad8 0048:fixme:fltmgr:FltRegisterFilter (0x11cb58, 0x65f108): stub ... 0048:Ret fltmgr.sys.FltRegisterFilter() retval=00000000 ret=007afad8 0048:Call fltmgr.sys.FltStartFiltering(0011d978) ret=00795697 0048:fixme:fltmgr:FltStartFiltering (0x11d978): stub 0048:Ret fltmgr.sys.FltStartFiltering() retval=00000000 ret=00795697 0048:Call ntoskrnl.exe.PsSetCreateProcessNotifyRoutineEx(00781aba,00000000) ret=0079d0f5 0048:fixme:ntoskrnl:PsSetCreateProcessNotifyRoutineEx stub: 0x781aba 0 0048:Ret ntoskrnl.exe.PsSetCreateProcessNotifyRoutineEx() retval=00000000 ret=0079d0f5 ... --- snip --- Driver init successful return: --- snip --- ... 0048:Call ntdll.RtlInitUnicodeString(0065f190,0065f444 L"\\Driver") ret=0078ee45 0048:Ret ntdll.RtlInitUnicodeString() retval=0065f190 ret=0078ee45 0048:Call ntdll.ZwOpenDirectoryObject(0065f1c8,00000001,0065f1b0) ret=0079a425 0048:Ret ntdll.ZwOpenDirectoryObject() retval=00000000 ret=0079a425 0048:Call ntdll.ZwQueryDirectoryObject(00000048,0065f1f4,00000100,00000001,00000000,0065f458,00000000) ret=007a78fb 0048:Ret ntdll.ZwQueryDirectoryObject() retval=8000001a ret=007a78fb 0048:Call ntdll.ZwClose(00000048) ret=00795dcc 0048:Ret ntdll.ZwClose() retval=00000000 ret=00795dcc 0048:Ret driver init 0x7fdf6e (obj=0x11cb58,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") retval=00000000 0048:trace:winedevice:init_driver init done for L"BEDaisy" obj 0x11cb58 0048:trace:winedevice:init_driver - DriverInit = 0x7fdf6e 0048:trace:winedevice:init_driver - DriverStartIo = (nil) 0048:trace:winedevice:init_driver - DriverUnload = 0x781de8 0048:trace:winedevice:init_driver - MajorFunction[0] = 0x781dc4 0048:trace:winedevice:init_driver - MajorFunction[1] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[2] = 0x781d54 0048:trace:winedevice:init_driver - MajorFunction[3] = 0x7820c2 0048:trace:winedevice:init_driver - MajorFunction[4] = 0x7829b4 0048:trace:winedevice:init_driver - MajorFunction[5] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[6] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[7] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[8] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[9] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[10] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[11] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[12] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[13] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[14] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[15] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[16] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[17] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[18] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[19] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[20] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[21] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[22] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[23] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[24] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[25] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[26] = 0x7ecdfeb0 0048:trace:winedevice:init_driver - MajorFunction[27] = 0x7ecdfeb0 0048:Ret ntoskrnl.exe.IoCreateDriver() retval=00000000 ret=7effb7c8 0048:Call ntoskrnl.exe.ObReferenceObjectByName(0065fdc0,00000040,00000000,00000000,00000000,00000000,00000000,0065fdc8) ret=7effb852 0048:trace:ntoskrnl:ObReferenceObjectByName mostly-stub:L"\\Driver\\BEDaisy" 64 (nil) 0 (nil) 0 (nil) 0x65fdc8 ... 0048:Ret ntoskrnl.exe.ObReferenceObjectByName() retval=00000000 ret=7effb852 ... 0048:Call advapi32.SetServiceStatus(0011b788,0065fd84) ret=7effb41b ... 0048:Ret advapi32.SetServiceStatus() retval=00000001 ret=7effb41b --- snip --- NOTE: This doesn't really make BattlEye functional. It enables both services to run and prevents the initial driver service crashes/errors (2). The "Tibia" client I used to test with (http://static.tibia.com/download/Tibia_Setup.exe) still reports BattlEye not working properly. --- snip --- ... [ 11:53:26,282 ] BattlEye: "Initialized (v1.243)" [ 11:53:26,374 ] Request connection to gameserver "tcp://tibia-ip-eu.ciproxy.com:7171" (unprotected: "tcp://tibia-pool-eu.ciproxy.com:7171" ) requested (Charakter "Da Beef" ) [ 11:53:26,374 ] Request connection to gameserver "tcp://tibia-ip-eu.ciproxy.com:7171" "Damora" [ 11:53:26,405 ] Connected to gameserver "tcp://tibia-ip-eu.ciproxy.com:7171" "Damora" [ 11:53:26,637 ] QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State) [ 11:53:26,691 ] QObject::connect: Cannot connect (null)::stateChanged(QNetworkSession::State) to QNetworkReplyHttpImpl::_q_networkSessionStateChanged(QNetworkSession::State) [ 11:53:27,317 ] BattlEye: "Restarting client is necessary, service isn't running properly" [ 11:53:27,318 ] BattlEye: "Restarting client is necessary, update required" ... --- snip --- I have no intention to look further unless there is some progress on previous tickets. $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe $ wine --version wine-3.1-193-g354fa7eb79 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.

2 5

[Bug 44837] New: BattlEye 'BEDaisy' kernel service fails in driver entry point due to missing ' ntoskrnl.exe.PsAcquireProcessExitSynchronization'
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=44837 Bug ID: 44837 Summary: BattlEye 'BEDaisy' kernel service fails in driver entry point due to missing 'ntoskrnl.exe.PsAcquireProcessExitSynchronization' Product: Wine Version: 3.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 44811 --- snip --- ... 0052:Call KERNEL32.GetModuleHandleW(7ec246fc L"ntoskrnl.exe") ret=7ec1a2f6 0052:Ret KERNEL32.GetModuleHandleW() retval=7ec00000 ret=7ec1a2f6 0052:Call KERNEL32.GetProcAddress(7ec00000,0011d4b8 "PsAcquireProcessExitSynchronization") ret=7ec1a30b 0052:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec1a30b 0052:Call KERNEL32.GetModuleHandleW(7ec24718 L"hal.dll") ret=7ec1a324 0052:Ret KERNEL32.GetModuleHandleW() retval=f7ac0000 ret=7ec1a324 0052:Call KERNEL32.GetProcAddress(f7ac0000,0011d4b8 "PsAcquireProcessExitSynchronization") ret=7ec1a33f 0052:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec1a33f 0052:Call ntdll.RtlFreeAnsiString(0065eb30) ret=7ec1a351 0052:Ret ntdll.RtlFreeAnsiString() retval=0065eb30 ret=7ec1a351 0052:fixme:ntoskrnl:MmGetSystemRoutineAddress L"PsAcquireProcessExitSynchronization" not found 0052:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=00000000 ret=007da46e 0052:Ret driver init 0x78d000 (obj=0x11caa0,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") retval=c0000001 0052:trace:winedevice:init_driver init done for L"BEDaisy" obj 0x11caa0 ... 0052:Ret ntoskrnl.exe.IoCreateDriver() retval=c0000001 ret=7effb786 0052:err:winedevice:async_create_driver failed to create driver L"BEDaisy": c0000001 ... --- snip --- Discussion of this API (potential use) here https://forum.sysinternals.com/discussion-howto-enumerate-handles_topic1940… https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/windows-ke… https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/run-down-p… https://www.geoffchappell.com/studies/windows/km/ntoskrnl/api/index.htm (PsAcquireProcessExitSynchronization 6.0 and higher ) $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe $ wine --version wine-3.4-192-gd7430abd40 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.

2 9

[Bug 44906] New: BattlEye 'BEDaisy' kernel service fails in driver entry point due to missing ' ntoskrnl.exe.ExfUnblockPushLock'
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=44906 Bug ID: 44906 Summary: BattlEye 'BEDaisy' kernel service fails in driver entry point due to missing 'ntoskrnl.exe.ExfUnblockPushLock' Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, ticket dedicated to: https://github.com/wine-staging/wine-staging/blob/master/patches/ntoskrnl-S… Prerequisite: * bug 44837 --- snip --- $ WINEDEBUG=+seh,+relay,+ntoskrnl wine net start BEDaisy >>log.txt 2>&1 ... 0035:Call KERNEL32.GetModuleHandleW(7ec229dc L"ntoskrnl.exe") ret=7ec18512 0035:Ret KERNEL32.GetModuleHandleW() retval=7ec00000 ret=7ec18512 0035:Call KERNEL32.GetProcAddress(7ec00000,0011d630 "PsAcquireProcessExitSynchronization") ret=7ec18527 0035:Ret KERNEL32.GetProcAddress() retval=7ec0e468 ret=7ec18527 ... 0035:trace:ntoskrnl:MmGetSystemRoutineAddress L"PsAcquireProcessExitSynchronization" -> 0x7ec0e468 0035:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=7ec0e468 ret=007da46e 0035:Call ntoskrnl.exe.MmGetSystemRoutineAddress(0065ecac) ret=00868d6d ... 0035:Call KERNEL32.GetModuleHandleW(7ec229dc L"ntoskrnl.exe") ret=7ec18512 0035:Ret KERNEL32.GetModuleHandleW() retval=7ec00000 ret=7ec18512 0035:Call KERNEL32.GetProcAddress(7ec00000,0011d630 "PsReleaseProcessExitSynchronization") ret=7ec18527 ... 0035:trace:ntoskrnl:MmGetSystemRoutineAddress L"PsReleaseProcessExitSynchronization" -> 0x7ec0e540 0035:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=7ec0e540 ret=00868d6d 0035:Call ntoskrnl.exe.MmGetSystemRoutineAddress(0065ecac) ret=0084d372 ... 0035:Call KERNEL32.GetModuleHandleW(7ec229dc L"ntoskrnl.exe") ret=7ec18512 0035:Ret KERNEL32.GetModuleHandleW() retval=7ec00000 ret=7ec18512 0035:Call KERNEL32.GetProcAddress(7ec00000,0011d630 "ExfUnblockPushLock") ret=7ec18527 0035:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec18527 0035:Call KERNEL32.GetModuleHandleW(7ec229f8 L"hal.dll") ret=7ec18540 0035:Ret KERNEL32.GetModuleHandleW() retval=f79f0000 ret=7ec18540 0035:Call KERNEL32.GetProcAddress(f79f0000,0011d630 "ExfUnblockPushLock") ret=7ec1855b 0035:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec1855b ... 0035:fixme:ntoskrnl:MmGetSystemRoutineAddress L"ExfUnblockPushLock" not found 0035:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=00000000 ret=0084d372 0035:Ret driver init 0x78d000 (obj=0x11cc00,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") retval=c0000001 ... 0035:Ret ntoskrnl.exe.IoCreateDriver() retval=c0000001 ret=7effb832 0035:err:winedevice:async_create_driver failed to create driver L"BEDaisy": c0000001 --- snip --- $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe 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.

2 4

[Bug 44910] New: BattlEye 'BEDaisy' kernel service fails in driver entry point due to ' ntoskrnl.exe.ObReferenceObjectByHandle' stub (needs STATUS_SUCCESS)
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=44910 Bug ID: 44910 Summary: BattlEye 'BEDaisy' kernel service fails in driver entry point due to 'ntoskrnl.exe.ObReferenceObjectByHandle' stub (needs STATUS_SUCCESS) Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 44907 Prerequisite: * bug 44837 -> missing 'ntoskrnl.exe.Ps{Acquire,Release}ProcessExitSynchronization' * bug 44906 -> missing 'ntoskrnl.exe.ExfUnblockPushLock' * bug 44907 -> missing 'fltmgr.sys.FltGetRoutineAddress' Unlike the other bug reports, I added +server debug channel to show which handle is being dereferenced. --- snip --- $ WINEDEBUG=+seh,+relay,+ntoskrnl,+server wine net start BEDaisy >>log.txt 2>&1 ... 0033:Call driver init 0x78d000 (obj=0x11cb00,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") ... 0033:Call ntoskrnl.exe.PsCreateSystemThread(0065ec4c,001fffff,0065ec50,00000000,00000000,0078308e,00000000) ret=0080858c 0033:Call ntdll.RtlCreateUserThread(ffffffff,00000000,00000000,00000000,00000000,00000000,0078308e,00000000,0065ec4c,00000000) ret=7ec1823e 0033: *fd* 21 <- 145 0033: new_thread( access=001fffff, attributes=00000000, suspend=0, request_fd=21 ) 0033: new_thread() = 0 { tid=0035, handle=0040 } 0033:Ret ntdll.RtlCreateUserThread() retval=00000000 ret=7ec1823e 0033:Ret ntoskrnl.exe.PsCreateSystemThread() retval=00000000 ret=0080858c 0033:Call ntoskrnl.exe.ObReferenceObjectByHandle(00000040,001fffff,00000000,00000000,0078b55c,00000000) ret=007840d4 0033:fixme:ntoskrnl:ObReferenceObjectByHandle stub: 0x40 1fffff (nil) 0 0x78b55c (nil) 0033:Ret ntoskrnl.exe.ObReferenceObjectByHandle() retval=c0000002 ret=007840d4 0033:Call ntoskrnl.exe.KeSetEvent(0078b3f4,00000000,00000000) ret=00790914 0033:fixme:ntoskrnl:KeSetEvent (0x78b3f4, 0, 0): stub 0033:Ret ntoskrnl.exe.KeSetEvent() retval=00000000 ret=00790914 0033:Call ntoskrnl.exe.ZwClose(00000040) ret=007f2c73 0033:Call ntdll.NtClose(00000040) ret=7bc803ab 0033: close_handle( handle=0040 ) 0033: close_handle() = 0 0033:Ret ntdll.NtClose() retval=00000000 ret=7bc803ab 0033:Ret ntoskrnl.exe.ZwClose() retval=00000000 ret=007f2c73 0033:Call fltmgr.sys.FltUnregisterFilter(deadbeaf) ret=007fd488 0033:fixme:fltmgr:FltUnregisterFilter (0xdeadbeaf): stub 0033:Ret fltmgr.sys.FltUnregisterFilter() retval=00000039 ret=007fd488 0033:Call ntoskrnl.exe.PsRemoveCreateThreadNotifyRoutine(0078130c) ret=0082f2bc 0033:fixme:ntoskrnl:PsRemoveCreateThreadNotifyRoutine stub: 0x78130c 0033:Ret ntoskrnl.exe.PsRemoveCreateThreadNotifyRoutine() retval=00000000 ret=0082f2bc 0033:Call ntoskrnl.exe.PsRemoveLoadImageNotifyRoutine(00781dc6) ret=008242ab 0033:fixme:ntoskrnl:PsRemoveLoadImageNotifyRoutine stub: 0x781dc6 0033:Ret ntoskrnl.exe.PsRemoveLoadImageNotifyRoutine() retval=00000000 ret=008242ab 0033:Call ntoskrnl.exe.KeWaitForSingleObject(0078b530,00000000,00000000,00000000,00000000) ret=0080b669 0033:fixme:ntoskrnl:KeWaitForSingleObject stub: 0x78b530, 0, 0, 0, (nil) 0033:Ret ntoskrnl.exe.KeWaitForSingleObject() retval=c0000002 ret=0080b669 0033:Call ntoskrnl.exe.ObUnRegisterCallbacks(deadbeaf) ret=007ac56b 0033:fixme:ntoskrnl:ObUnRegisterCallbacks stub: 0xdeadbeaf 0033:Ret ntoskrnl.exe.ObUnRegisterCallbacks() retval=0000003b ret=007ac56b 0033:Call ntoskrnl.exe.KeReleaseMutex(0078b530,00000000) ret=00839822 0033:fixme:ntoskrnl:KeReleaseMutex stub: 0x78b530, 0 0033:Ret ntoskrnl.exe.KeReleaseMutex() retval=c0000002 ret=00839822 0033:Call ntoskrnl.exe.IoDeleteSymbolicLink(0065ec74) ret=0080d6dc 0033:Call ntdll.NtOpenSymbolicLinkObject(0065eb40,00000000,0065eb28) ret=7ec158ab 0033: open_symlink( access=00000000, attributes=00000040, rootdir=0000, name=L"\\DosDevices\\BattlEye" ) 0033: open_symlink() = 0 { handle=0044 } 0033:Ret ntdll.NtOpenSymbolicLinkObject() retval=00000000 ret=7ec158ab 0033: unlink_object( handle=0044 ) 0033: unlink_object() = 0 0033:Call ntdll.NtClose(00000044) ret=7ec15924 0033: close_handle( handle=0044 ) 0033: close_handle() = 0 0033:Ret ntdll.NtClose() retval=00000000 ret=7ec15924 0033:Ret ntoskrnl.exe.IoDeleteSymbolicLink() retval=00000000 ret=0080d6dc 0033:Call ntoskrnl.exe.IoDeleteDevice(0011cce0) ret=00867fef 0033:trace:ntoskrnl:IoDeleteDevice 0x11cce0 0033: delete_device( handle=0038 ) 0033: delete_device() = 0 0033:Call ntdll.NtClose(00000038) ret=7ec15773 0033: close_handle( handle=0038 ) 0033: close_handle() = 0 0033:Ret ntdll.NtClose() retval=00000000 ret=7ec15773 ... 0033:Ret ntoskrnl.exe.IoDeleteDevice() retval=00000001 ret=00867fef 0033:Ret driver init 0x78d000 (obj=0x11cb00,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") retval=c0000002 ... 0033:Ret ntoskrnl.exe.IoCreateDriver() retval=c0000002 ret=7effb832 0033:err:winedevice:async_create_driver failed to create driver L"BEDaisy": c0000002 --- snip --- MSDN: https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/wdm/n… One of MS official kernel driver examples, illustrating how the API is meant to be used here (general pattern for getting thread object pointer): https://github.com/Microsoft/Windows-driver-samples/blob/master/general/can… --- snip --- ... status = PsCreateSystemThread(&threadHandle, (ACCESS_MASK)0, NULL, (HANDLE) 0, NULL, CsampPollingThread, deviceObject ); if ( !NT_SUCCESS( status )) { IoDeleteSymbolicLink( &unicodeDosDeviceName ); IoDeleteDevice( deviceObject ); return status; } // // Convert the Thread object handle into a pointer to the Thread object // itself. Then close the handle. // ObReferenceObjectByHandle(threadHandle, THREAD_ALL_ACCESS, NULL, KernelMode, &devExtension->ThreadObject, NULL ); ZwClose(threadHandle); ... --- snip --- NOTE: Unlike the snippet shown above, 'BEDaisy' driver checks the return value of 'ObReferenceObjectByHandle' and initiates teardown on failure. For testing I simply returned 'STATUS_SUCCESS' but also set the object pointer to a magic value (if ptr is non-NULL). The idea is when the driver tries to access/dereference the pointer we can easily see that a "poor" man's "succeed" stub is not enough. It seems it doesn't need a real thread object for now and runs much further. $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe $ wine --version wine-3.5-107-gf4573adb0f 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.

2 5

[Bug 44908] New: BattlEye 'BEDaisy' kernel service wants ' ntoskrnl.exe.ObGetObjectType'
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=44908 Bug ID: 44908 Summary: BattlEye 'BEDaisy' kernel service wants 'ntoskrnl.exe.ObGetObjectType' Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 4907 Prerequisite: * bug 44837 -> missing 'ntoskrnl.exe.Ps{Acquire,Release}ProcessExitSynchronization' * bug 44906 -> missing 'ntoskrnl.exe.ExfUnblockPushLock' * bug 44907 -> missing 'fltmgr.sys.FltGetRoutineAddress' --- snip --- $ WINEDEBUG=+seh,+relay,+ntoskrnl wine net start BEDaisy >>log.txt 2>&1 ... 0035:Call driver init 0x78d000 (obj=0x11cbf8,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") ... 0035:Call ntoskrnl.exe.RtlGetVersion(0078b270) ret=0080750a 0035:Call ntdll.RtlGetVersion(0078b270) ret=7bc803ab 0035:Ret ntdll.RtlGetVersion() retval=00000000 ret=7bc803ab 0035:Ret ntoskrnl.exe.RtlGetVersion() retval=00000000 ret=0080750a 0035:Call ntoskrnl.exe.MmGetSystemRoutineAddress(0065ec68) ret=007a8561 0035:Call ntdll.RtlUnicodeStringToAnsiString(0065eb30,0065ec68,00000001) ret=7ec1855e 0035:Ret ntdll.RtlUnicodeStringToAnsiString() retval=00000000 ret=7ec1855e 0035:Call KERNEL32.GetModuleHandleW(7ec22a9c L"ntoskrnl.exe") ret=7ec18572 0035:Ret KERNEL32.GetModuleHandleW() retval=7ec00000 ret=7ec18572 0035:Call KERNEL32.GetProcAddress(7ec00000,0011d610 "ObGetObjectType") ret=7ec18587 0035:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec18587 0035:Call KERNEL32.GetModuleHandleW(7ec22ab8 L"hal.dll") ret=7ec185a0 0035:Ret KERNEL32.GetModuleHandleW() retval=f7b10000 ret=7ec185a0 0035:Call KERNEL32.GetProcAddress(f7b10000,0011d610 "ObGetObjectType") ret=7ec185bb 0035:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec185bb 0035:Call ntdll.RtlFreeAnsiString(0065eb30) ret=7ec185cd 0035:Ret ntdll.RtlFreeAnsiString() retval=0065eb30 ret=7ec185cd 0035:fixme:ntoskrnl:MmGetSystemRoutineAddress L"ObGetObjectType" not found 0035:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=00000000 ret=007a8561 ... 0035:Ret driver init 0x78d000 (obj=0x11cbf8,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") retval=c0000002 ... 0035:Ret ntoskrnl.exe.IoCreateDriver() retval=c0000002 ret=7effb832 0035:err:winedevice:async_create_driver failed to create driver L"BEDaisy": c0000002 --- snip --- NOTE: I didn't mention "crashes" or "fails in entry point" in this ticket summary on purpose. The failure from the log snippet is actually a different problem. $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe $ wine --version wine-3.5-107-gf4573adb0f 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.

2 4

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

18 Mar '21

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 26600] New: Filemaker Pro2 under Wine
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=26600 Summary: Filemaker Pro2 under Wine Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gilles.l.auger(a)gmail.com The program winevdm.exe has encountered a serious problem and must be closed. We are sorry for this situation. This may be caused by an error in the program or a default in Wine. This problem does not occur under Windows. Le programme winevdm.exe a rencontré un problème sérieux et doit être fermé. Nous sommes désolés pour le désagrément subi. Cela peut être causé par une erreur dans le programme ou un défaut dans Wine. Se problème ne se produit pas sous Windows. -- 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 13463] New: 000
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

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 18 Mar '21

18 Mar '21

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 18 Mar '21

18 Mar '21

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 18 Mar '21

18 Mar '21

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

[Bug 35586] New: Filemaker 8.5 v2 crashes
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=35586 Bug ID: 35586 Summary: Filemaker 8.5 v2 crashes Product: Wine Version: 1.5.27 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cb750nice(a)free.fr Classification: Unclassified Created attachment 47517 --> http://bugs.winehq.org/attachment.cgi?id=47517 Backtrace.txt I use Wine only to use FileMaker Pro. It works ordinarly quite good. But sometimes it crashes. It never arrived when I was working on it. It never arrived under Windows XP on the same computer. -- 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 9773] New: FileMaker crashes
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=9773 Summary: FileMaker crashes Product: WineHQ Apps Database Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: website-bugs AssignedTo: wine-bugs(a)winehq.org ReportedBy: hhalvors(a)princeton.edu Created an attachment (id=8211) --> (http://bugs.winehq.org/attachment.cgi?id=8211) partial backtrace Wine 0.9.39, trying to run FileMaker Pro 8.5. Installation went great. I can start FileMaker, and I can open a database. However, when I click on the screen, FileMaker crashes. I have attached a partial backtrace. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 12

[Bug 33452] New: Can't type after entering pop-up list in Filemaker Pro 5
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=33452 Bug #: 33452 Summary: Can't type after entering pop-up list in Filemaker Pro 5 Product: Wine Version: 1.5.28 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: DonJaime(a)freenet.de Classification: Unclassified After entering a pop-up list in FileMaker Pro 5.0v3 it is no longer possible to enter text, either in the pop-up list field itself or in any other field after leaving it. After running a script, changing to another window and back again or to layout mode and back again you can type again. Control keys do not stop working. The tab key works to leave a pop-up field but not once you have entered a normal text field. -- 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 9

[Bug 21974] New: FileMaker v10.0v1 - Crash when loading a new datatable
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=21974 Summary: FileMaker v10.0v1 - Crash when loading a new datatable Product: Wine Version: 1.1.38 Platform: x86 URL: http://www.filemaker.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: newsletter(a)Schiermeier-Software.de Created an attachment (id=26679) --> (http://bugs.winehq.org/attachment.cgi?id=26679) some databases for testing - use 'tanzkalender.fp7' Regression since wine-v1.1.38 up to now (v1.1.40) - in wine-v1.1.37 was working: result of my regression test: --- aa6c4d4e92cdb944e53a0c36819621a6875f1e61 is the first bad commit commit aa6c4d4e92cdb944e53a0c36819621a6875f1e61 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Sat Jan 23 14:15:43 2010 +0100 configure: Add specific creation macros for the various types of makefiles. :100644 100644 ce3941e561ec8f3cde50ca78bf170eb1babb05e6 b30e41e0b5c3af75186553099a0053025ca95f9a M aclocal.m4 :100644 100644 01cf3a78f71cf0d4762dae97e30efa57d9068ea0 7d5a29a821c2d5a4d9855274718df77ed12085f1 M configure.ac :040000 040000 d1bd1e023c24afddd345582dd59cb421b57397da 795ce110d7a0c2500740bb09508ee2f5c4f0fb02 M tools --- (I don't trust realy in this result - so I include some screenshots and some testdatas.) The application was working with the databases until the wine-version v1.1.37. Steps to reproduce the crash: 1.) database 'tanzkalender' (description is in English, data in German) 2.) click on the button 'call HTML-Export' 3.) crash - you can see the new, just loaded layout in the background. The button 'call HTML-Export' calls a script which load a new layout with the datas of the actual datatable. -- 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 15

[Bug 25461] New: Filemaker 11 crashes sometimes - Database window gets permanent focus (stays forced in foreground)
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=25461 Summary: Filemaker 11 crashes sometimes - Database window gets permanent focus (stays forced in foreground) Product: Wine Version: 1.3.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: emerson.prado.eng(a)gmail.com Created an attachment (id=32411) --> (http://bugs.winehq.org/attachment.cgi?id=32411) Terminal log beginning in an exception Filemaker Pro 11 is crashing during normal use. It's intermittent - sometimes I can use it the whole day without problems, sometimes it halts in less than 10 minutes. But I still can't tell whether a specific activity causes it. When it crashes, even if Filemaker isn't focused, the database window always stays on top, until Filemaker is forcefully closed. There is a pop-up error message, which can only be read by manually setting it on top (right-clicking its taskbar icon and selecting "always on top"). I'm attaching a partial Terminal log. I can't get it full because it's bigger than the Terminal buffer. But I was lucky to apparently get everything from the exception on, and this is what I attached here. -- 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 10

[Bug 25377] New: Filemaker 11 can't access / doesn't show remote databases / servers - both in "Local hosts" and "Favorite hosts"
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=25377 Summary: Filemaker 11 can't access / doesn't show remote databases / servers - both in "Local hosts" and "Favorite hosts" Product: Wine Version: 1.2.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: emerson.prado.eng(a)gmail.com Created an attachment (id=32277) --> (http://bugs.winehq.org/attachment.cgi?id=32277) Full terminal output from running FM 11 When I try to open a remote db, my server doesn't appear in the "Local hosts". If I manually add my server in the "Favorite hosts", the remote files aren't shown. I tried all Windows versions from XP up. The attachment is the full terminal output from running Filemaker (the main menu icon doesn't work, so I run FM from Terminal). -- 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 23

[Bug 25448] New: Filemaker Pro 11 can't be started from Linux main menu icon - Invalid or incorrect link
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=25448 Summary: Filemaker Pro 11 can't be started from Linux main menu icon - Invalid or incorrect link Product: Wine Version: 1.3.8 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: emerson.prado.eng(a)gmail.com Created an attachment (id=32388) --> (http://bugs.winehq.org/attachment.cgi?id=32388) Filemaker Pro 11 starter link inside "Windows" Start menu Clicking in the Filemaker icon in the main menu just brings in an error message window saying "File not found". Starting from Terminal works OK. The link in the main menu points to: env WINEPREFIX="/home/<user>/.wine" wine C:\\windows\\command\\start.exe /Unix /home/<user>/.wine/dosdevices/c:/users/<user>/Menu\ Iniciar/Programas/FileMaker\ Pro.lnk I'm sending attached the Filemaker Pro.lnk file. -- 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 22469] New: FileMaker Pro 11: Text is upside down when builtin gdiplus is used
by wine-bugs＠winehq.org 18 Mar '21

18 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=22469 Summary: FileMaker Pro 11: Text is upside down when builtin gdiplus is used Product: Wine Version: 1.1.43 Platform: x86 URL: http://www.filemaker.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus AssignedTo: wine-bugs(a)winehq.org ReportedBy: wylda(a)volny.cz Created an attachment (id=27526) --> (http://bugs.winehq.org/attachment.cgi?id=27526) Filemaker pro 11 Text in boxes is upside down, when the box is selected. This doesn't happen when native gdiplus is used. Attachment shows that better. To reproduce: 1. Download the trial version 2. Download demo data http://bugs.winehq.org/attachment.cgi?id=26679 3. Run "wine FileMaker\ Pro.exe" and load data from step 2. 4. Click on any textbox, to make it upside down -- 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 42

[Bug 45962] New: FileMaker Pro 16 crashes on startup
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=45962 Bug ID: 45962 Summary: FileMaker Pro 16 crashes on startup Product: Wine Version: 3.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: larrycoleman.email(a)gmail.com Distribution: --- Created attachment 62513 --> https://bugs.winehq.org/attachment.cgi?id=62513 The "Show Details" from when FileMaker crashes I am running on Ubuntu 16.04. I installed WineHQ 3.17. FileMaker Pro requires .Net Framework. I used Winetricks to install .NET Framework 4.6.1. I then installed FileMaker Pro 16. When trying to run FileMaker, I get a "Program Error" message "The program FileMaker Pro.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience." -- 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 42443] New: MyDiff Program doesn't launch
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=42443 Bug ID: 42443 Summary: MyDiff Program doesn't launch Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: le.pocher.julien(a)gmail.com Distribution: --- Created attachment 57275 --> https://bugs.winehq.org/attachment.cgi?id=57275 Bug backtrace The executable MyDiff.exe file won't run. See backtrace. -- 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 33287] New: Filemaker Pro12 crashes when opening database file
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

http://bugs.winehq.org/show_bug.cgi?id=33287 Bug #: 33287 Summary: Filemaker Pro12 crashes when opening database file Product: Wine Version: 1.4.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jmeador(a)momentapharma.com Classification: Unclassified I can install Filemaker Pro 12 with a valid serial number into BioLinux 7, which is Ubuntu 12.04. Wine was installed as 4.1 via the Ubuntu Software Center and I cannot get the dev version of 1.5 to install via this or the commandline. It says that the binaries are not available. When running from the commandline, I get this output: :~$ wine "c:\program files (x86)\FileMaker\FileMaker Pro 12\FileMaker Pro.exe" p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory When I look for this directory in /usr/lib/i386-linux-gnu/ there are no files or folders called pkcs11 so perhaps this is missing from the wine1.4 installer? When installing, the installer gets to the end and then crashes and says the registration program cannot run, however, the program will start and appears to run ok until you open a database file, and I have tried several. Once I try to open a file, it crashes. The FileMaker Pro binary and other files are installed into /Program File (x86)/FileMaker/... I am attaching the backtrace file as well which was obtained from running the program from the graphical method. The computer is an HP Xeon processor with 64-bit Ubuntu 12.04 and 128 GB ram Thanks for any help you can provide. -- 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 16

[Bug 39288] New: Filemaker Pro 12 crashes when trying to open a Filemaker database file
by wine-bugs＠winehq.org 17 Mar '21

17 Mar '21

https://bugs.winehq.org/show_bug.cgi?id=39288 Bug ID: 39288 Summary: Filemaker Pro 12 crashes when trying to open a Filemaker database file Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ben(a)berwers.org Distribution: --- Created attachment 52366 --> https://bugs.winehq.org/attachment.cgi?id=52366 Filemaker Pro 12 crashes when trying to open a Filemaker file. Filemaker Pro 12 has a serious problem and stops when I try to open any file. Please see attached backtrace report when opening a testfile. By the way Filemaker Pro 6 works fine. Unfortunately I cannot switch back to the 6-version. Hope you can help me, what goes wrong. Thanks in advance, Ben Berwers -- 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 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs February 2021