https://bugs.winehq.org/show_bug.cgi?id=38151
Bug ID: 38151 Summary: Final Fantasy XI doesn't launch after launch Product: Wine Version: 1.7.34 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: t3hyoshi@vivaldi.net Distribution: ---
Created attachment 50891 --> https://bugs.winehq.org/attachment.cgi?id=50891 backtrace
The client crashes after launch from the PlayOnline Launcher. The launcher runs just fine but when starting the client, I get the attached error message.
https://bugs.winehq.org/show_bug.cgi?id=38151
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #1 from Sebastian Lackner sebastian@fds-team.de --- Most likely related to https://bugs.winehq.org/show_bug.cgi?id=35361. Is it possible to disable the Steam overlay for this app somehow?
Does the patch https://github.com/wine-compholio/wine-staging/tree/master/patches/imm32-Cro... help?
https://bugs.winehq.org/show_bug.cgi?id=38151
Chiitoo escomk3@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |escomk3@hotmail.com
--- Comment #2 from Chiitoo escomk3@hotmail.com --- I'm fairly certain this is a long-standing (not Steam-related) issue which can be bypassed by using Windows 7 as the Windows version instead of Windows XP.
I forget if this is related:
https://bugs.winehq.org/show_bug.cgi?id=28861#c13
https://bugs.winehq.org/show_bug.cgi?id=38151
--- Comment #3 from Chiitoo escomk3@hotmail.com --- Probably was related. Quick traces tell me the crash happens just after imm32 stuff.
-- snip --
0037:Call imm32.ImmGetContext(00020054) ret=01404d82 0037:Call user32.IsWindow(00020054) ret=7e9236b2 0037:Ret user32.IsWindow() retval=00000001 ret=7e9236b2 0037:Call user32.GetPropW(00020054,7e926220 L"WineImmHIMCProperty") ret=7e9236c9 0037:Ret user32.GetPropW() retval=00000000 ret=7e9236c9 0037:Call user32.GetWindowThreadProcessId(00020054,0614e838) ret=7e91cb35 0037:Ret user32.GetWindowThreadProcessId() retval=00000020 ret=7e91cb35 0037:Ret imm32.ImmGetContext() retval=0350d7b0 ret=01404d82 0037:Call imm32.ImmSetCompositionStringA(0350d7b0,0000003f,0184c324,00000000,0184c325,00000000) ret=01404d9e 0037:Call KERNEL32.IsBadReadPtr(0350d7b0,00000158) ret=7e91cab8 0037:Ret KERNEL32.IsBadReadPtr() retval=00000000 ret=7e91cab8 0037:Ret imm32.ImmSetCompositionStringA() retval=00000000 ret=01404d9e 0037:Call imm32.ImmNotifyIME(0350d7b0,00000015,00000004,00000000) ret=01404daa 0037:Call KERNEL32.IsBadReadPtr(0350d7b0,00000158) ret=7e91cab8 0037:Ret KERNEL32.IsBadReadPtr() retval=00000000 ret=7e91cab8 0037:Call winex11.drv.NotifyIME(0350d7b0,00000015,00000004,00000000) ret=7e9206e1 0037:Call imm32.ImmLockIMC(0350d7b0) ret=7e243f26 0037:Call KERNEL32.IsBadReadPtr(0350d7b0,00000158) ret=7e91cab8 0037:Ret KERNEL32.IsBadReadPtr() retval=00000000 ret=7e91cab8 0037:Ret imm32.ImmLockIMC() retval=0350d7b4 ret=7e243f26 0037:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7e261994 ip=7e261994 tid=0037 0037:trace:seh:raise_exception info[0]=00000001 0037:trace:seh:raise_exception info[1]=00000014 0037:trace:seh:raise_exception eax=00000000 ebx=7e29a000 ecx=00000000 edx=00000000 esi=0012db70 edi=00020054 0037:trace:seh:raise_exception ebp=0614e7a8 esp=0614e784 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00210246 0037:trace:seh:call_stack_handlers calling handler at 0x7bc993e0 code=c0000005 flags=0 0037:Call KERNEL32.UnhandledExceptionFilter(0614e2b4) ret=7bc99443 0037:Call KERNEL32.IsBadCodePtr(00430ac4) ret=015673eb 0037:Ret KERNEL32.IsBadCodePtr() retval=00000000 ret=015673eb wine: Unhandled page fault on write access to 0x00000014 at address 0x7e261994 (thread 0037), starting debugger...
-- snip --
With less relay:
-- snip --
0032:trace:imm:ImmGetContext 0x20058 0032:trace:imm:ImmGetContext returning 0xb97e60 0032:trace:imm:ImmSetCompositionStringA (0xb97e60, 63, 0x195c324, 0, 0x195c325, 0): 0032:trace:imm:ImmNotifyIME (0xb97e60, 21, 4, 0) 0032:trace:imm:NotifyIME 0xb97e60 21 4 0 0032:trace:imm:NotifyIME CPS_CANCEL 0032:trace:seh:raise_exception code=c0000005 flags=0 addr=0x7e261994 ip=7e261994 tid=0032 0032:trace:seh:raise_exception info[0]=00000001 0032:trace:seh:raise_exception info[1]=00000014 0032:trace:seh:raise_exception eax=00000000 ebx=7e29a000 ecx=00000000 edx=00000000 esi=0015a6f0 edi=00020058 0032:trace:seh:raise_exception ebp=0619e828 esp=0619e804 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00210246 0032:trace:seh:call_stack_handlers calling handler at 0x7bc993e0 code=c0000005 flags=0 wine: Unhandled page fault on write access to 0x00000014 at address 0x7e261994 (thread 0032), starting debugger...
-- snip --
Again though, the application works with Windows 7 set as the Windows version, though in the bug I referred to, there might be something specific to OS X.
https://bugs.winehq.org/show_bug.cgi?id=38151
--- Comment #4 from Chiitoo escomk3@hotmail.com --- Forgot to add for the future when one goes and tries with Windows 7 mode selected: it will still crash, should the FFXI-window become lowered/inactive (via alt-tabbing for example).
This only happens if the opening movie is enabled though, via the configuration utility (which it by default is, and which doesn't quite work yet without gstreamer support, and still upside down and mirrored from left to right).
It can be mended by using native msctf.dll or by disabling the opening movie altogether via the configuration utility.
This is all documented on the FFXI-AppDB article.
https://bugs.winehq.org/show_bug.cgi?id=38151
jingai@floatingpenguins.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jingai@floatingpenguins.com
--- Comment #5 from jingai@floatingpenguins.com --- I'm seeing this exact problem with wine-staging 1.7.55. Version is set to Windows 7 and opening movie is disabled.
wine: Unhandled page fault on write access to 0x00000014 at address 0x7e6b7589 (thread 0032), starting debugger... Unhandled exception: page fault on write access to 0x00000014 in 32-bit code (0x7e6b7589). err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:7e6b7589 ESP:0e88e824 EBP:0e88e848 EFLAGS:00210246( R- -- I Z- -P- ) EAX:00000000 EBX:7e6f1a04 ECX:00000000 EDX:00000000 ESI:0013ba68 EDI:0002004e Stack dump: 0x0e88e824: 0abe4e80 0e88e848 7e75b91d 0abe4e80 0x0e88e834: 00000158 0e88e8a8 7e6f1a04 00000012 0x0e88e844: 0abe4e80 0e88e878 7e6c2de2 0002004e 0x0e88e854: 0e88e88c 0e88e878 7e696d05 0abe4e80 0x0e88e864: 00000000 00000000 00000000 7e6f1a04 0x0e88e874: 00000012 0e88e8c8 7e698964 0002004e 000c: sel=0067 base=00000000 limit=00000000 32-bit r-- Backtrace: =>0 0x7e6b7589 in winex11 (+0x47589) (0x0e88e848) 1 0x7e6c2de2 in winex11 (+0x52de1) (0x0e88e878) 2 0x7e698964 NotifyIME+0x253() in winex11 (0x0e88e8c8) 3 0x7e760150 ImmNotifyIME+0x7f() in imm32 (0x0e88e928) 0x7e6b7589: movl %edi,0x14(%eax)
https://bugs.winehq.org/show_bug.cgi?id=38151
--- Comment #6 from jingai jingai@floatingpenguins.com --- Same problem with WINE 1.8rc2 from Debian sid/unstable. This is with a 32-bit WINE prefix, also.
https://bugs.winehq.org/show_bug.cgi?id=38151
--- Comment #7 from jingai jingai@floatingpenguins.com --- Problem persists with wine 1.9.3.
https://bugs.winehq.org/show_bug.cgi?id=38151
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #8 from super_man@post.com --- When I did query of wine source code I found out that there only 2 places where "NotifyIME CPS_CANCEL" can be found.
That's the last thing wine executes before the crash.
http://source.winehq.org/git/wine.git/blob/9c98d632779862aae15e9e3a25f59065f...
http://source.winehq.org/git/wine.git/blob/9c98d632779862aae15e9e3a25f59065f...
The other is winex11 and other winemac driver.
I didnt try to track the other crash.
https://bugs.winehq.org/show_bug.cgi?id=38151
--- Comment #9 from jingai jingai@floatingpenguins.com --- I was able to get this working with the patch from Chiitoo over at: https://bugs.winehq.org/show_bug.cgi?id=28861#c13
I don't know what negative effects it might have, but it does allow FFXI to launch.
https://bugs.winehq.org/show_bug.cgi?id=38151
--- Comment #10 from super_man@post.com --- These bugs sounds like dupe then.
https://bugs.winehq.org/show_bug.cgi?id=38151
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com, | |winetest@luukku.com
--- Comment #11 from winetest@luukku.com --- (In reply to super_man from comment #10)
These bugs sounds like dupe then.
Dupe.
https://bugs.winehq.org/show_bug.cgi?id=38151
--- Comment #12 from winetest@luukku.com --- (In reply to jingai from comment #9)
I was able to get this working with the patch from Chiitoo over at: https://bugs.winehq.org/show_bug.cgi?id=28861#c13
I don't know what negative effects it might have, but it does allow FFXI to launch.
https://bugs.winehq.org/show_bug.cgi?id=38151
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio@earthlink.net
https://bugs.winehq.org/show_bug.cgi?id=38151
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC|dimesio@earthlink.net |
--- Comment #13 from Rosanne DiMesio dimesio@earthlink.net --- Marking duplicate per comment 9.
*** This bug has been marked as a duplicate of bug 28861 ***
https://bugs.winehq.org/show_bug.cgi?id=38151
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Bruno Jesus 00cpxxx@gmail.com --- Closing duplicate bugs.
-
wine-bugs＠winehq.org