[Bug 56299] New: imm32.dll: CtfImmIsGuidMapEnable could not be located in the dynamic link library
https://bugs.winehq.org/show_bug.cgi?id=56299 Bug ID: 56299 Summary: imm32.dll: CtfImmIsGuidMapEnable could not be located in the dynamic link library Product: Wine Version: 9.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: imm32 Assignee: wine-bugs(a)winehq.org Reporter: yafoce6821(a)giratex.com Distribution: --- Impacted Application: PL9.exe (Parashara's Light 9.0 from Geovision Software) When trying to run, in a MessageBox application displays 'The procedure entry point CtfImmIsGuidMapEnable could not be located in the dynamic link library imm32.dll' and shutting down. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 yafoce6821(a)giratex.com changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://parasharaslight.com | |/parasharas-light/ -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com --- Comment #1 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Hi, This function seems totally undocumented, so I wonder if the program really would call this. Have you installed and set any native dlls alongside this program? Maybe you could attach a WINEDEBUG=+loaddll,+msgbox log to shed a light on this (run WINEDEBUG=+loaddll,+msgbox wine program_name.exe &>log.txt and attach log.txt to this bugreport) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #2 from yafoce6821(a)giratex.com --- Created attachment 76043 --> https://bugs.winehq.org/attachment.cgi?id=76043 Requested log file got the log from: WINEPREFIX=~/wine/win10ltc WINEARCH=win32 WINEDEBUG=+loaddll,+msgbox wine ./drive_c/GeoVision/PL9/PL9.exe &>log.txt @Louis Lenders This function seems totally undocumented, so I wonder if the program really would call this. Have you installed and set any native dlls alongside this program? No. I did not. This is all I have tried prior to posting here: https://forum.winehq.org/viewtopic.php?t=38465 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #3 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Created attachment 76067 --> https://bugs.winehq.org/attachment.cgi?id=76067 add CtfImmIsGuidMapEnable to spec Hi, the log you posted seems normal (no native dlls) so I guess that call comes from the program itsself then or one of the loaded dlls (libgcc_s_dw2-1.dll or libstdc++-6.dll?). The attached patch just adds the entrypoint; Maybe it's enough to get the program going. Any possibility you could try out the patch (you'd have to compile wine yourself)? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 Vijay Kamuju <infyquest(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |infyquest(a)gmail.com --- Comment #4 from Vijay Kamuju <infyquest(a)gmail.com> --- There are lot of CtfImm* function entries are missing in the spec file, can you please add them and send a MR. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #5 from yafoce6821(a)giratex.com --- @Louis Lenders OK, I'll try out the patch and will let you know how it went. Please allow me some time. Quote @Louis Lenders "the log you posted seems normal (no native dlls) so I guess that call comes from the program itsself then or one of the loaded dlls (libgcc_s_dw2-1.dll or libstdc++-6.dll?)." Actually, it loads it from imm32.dll itself. I had decompiled the PE executable (PL9.exe) in ghidra to understand it. As @Vijay Kamuju noted, the exe was referencing all the CtfImm* references from imm32.dll itself. You can see that when you decompile the imm32 native dll itself. Hope this clears the confusion! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #6 from yafoce6821(a)giratex.com --- Created attachment 76071 --> https://bugs.winehq.org/attachment.cgi?id=76071 fixed_log.txt It works after patch! However, after starting up splash screen, during GUI launch it crashes. I can confirm the imm32 CtfImmIsGuidMapEnable issue is resolved. However, the program crashes due to other issues (and the wine debugger pops up), unrelated to imm32.dll missing stub issue. I think I have identified the problem; the program is made to run in both windows and mac and as you can see from the log file, the only dlls that it loads by itself are, libgcc_s_dw2-1.dll libstdc++-6.dll libwinpthread-1.dll All of which are Mingw dlls. Can I override the unix variants of the dlls with wine? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #7 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Hi, thanks for reporting back, I sent a patch. For the follow up crash you could best attach a +relay,+seh debug log: WINEPREFIX=~/wine/win10ltc WINEARCH=win32 WINEDEBUG=+relay,+seh wine ./drive_c/GeoVision/PL9/PL9.exe &>log.txt and attach compressed (bzipped2) file log.txt to this bugreport -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #8 from yafoce6821(a)giratex.com --- Created attachment 76074 --> https://bugs.winehq.org/attachment.cgi?id=76074 WINEDEBUG=+relay,+seh I have attached the requested log file generated using, WINEPREFIX=~/wine/win10ltsc WINEARCH=win32 WINEDEBUG=+relay,+seh ../../wine-src/wine start /d "C:\Geovision\PL9" "C:\Geovision\PL9\PL9.exe" &>~/wine/log.txt Some irrelevant observation: - If I do not supply wine start the application's base dir, then PL9.exe could not find its own files. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #9 from yafoce6821(a)giratex.com --- (In reply to Louis Lenders from comment #7)
Hi, thanks for reporting back, I sent a patch.
For the follow up crash you could best attach a +relay,+seh debug log:
WINEPREFIX=~/wine/win10ltc WINEARCH=win32 WINEDEBUG=+relay,+seh wine ./drive_c/GeoVision/PL9/PL9.exe &>log.txt
and attach compressed (bzipped2) file log.txt to this bugreport
One more thing, I did not see any attachment for a patch. Were you intending to send the patch to me, or were you talking about upstream patching? Just asking to clarify. Thanks. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #10 from Louis Lenders <xerox.xerox2000x(a)gmail.com> ---
Were you intending to send the patch to me, or were you talking about upstream patching?
Just asking to clarify. Thanks.
Hi, I sent i t upstream. I had a quick look at the debuglog, one thing that's interesting is that it fires up wmic.exe, afaict without any arguments. No clue what the purpose is of that. Does it change anything if you disable wmic.exe: WINEPREFIX=~/wine/win10ltc WINEARCH=win32 WINEDLLOVERRIDES=wmic.exe=d wine ./drive_c/GeoVision/PL9/PL9.exe -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #11 from yafoce6821(a)giratex.com --- Created attachment 76075 --> https://bugs.winehq.org/attachment.cgi?id=76075 WINEDEBUG=+relay,+seh WINEDLLOVERRIDES=wmic.exe=d (In reply to Louis Lenders from comment #10)
I had a quick look at the debuglog, one thing that's interesting is that it fires up wmic.exe, afaict without any arguments. No clue what the purpose is of that.
Does it change anything if you disable wmic.exe:
WINEPREFIX=~/wine/win10ltc WINEARCH=win32 WINEDLLOVERRIDES=wmic.exe=d wine ./drive_c/GeoVision/PL9/PL9.exe
When I disabled wmic.exe, the application started upto the splash screen like previously, and then shut down like previously. But this time it did it gracefully without spinning up the wine debugger. I've attached another log Log generated using: WINEPREFIX=~/wine/win10ltsc WINEARCH=win32 WINEDEBUG=+relay,+seh WINEDLLOVERRIDES=wmic.exe=d ./wine-src/wine start /d "C:\Geovision\PL9" "C:\Geovision\PL9\PL9.exe" &> log.txt -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #12 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Created attachment 76080 --> https://bugs.winehq.org/attachment.cgi?id=76080 keep wmic alive for 10 secs Hi, patch for initial bug is now in git as commit 7a92a33b27b3e362c12539d6382dfe6444ed77cf About the followup bug: in the 2nd log you attached it just exits with error 3, which seems 'path not found' which seems reasonable as wmic is disabled. It's all kind of guess work and this wmic thing just might be a red herring but maybe you could try with attached hack (which should keep wmic alive for 10 secs) if anything changes. (reason behind hack: on windows, if you just fire up wmic without arguments it will fire up the wmic commander. I haven't got a clue why a program would want this. Anyway, wine will just return an error which is not like how windows does it. As mentioned before: might just be a red herring but maybe worth a try) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #13 from Vijay Kamuju <infyquest(a)gmail.com> --- Can we have separate bugs for each of the issue? As they tend to have separate bug fixes and kinda hard to track the fixes. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 --- Comment #14 from yafoce6821(a)giratex.com --- (In reply to Vijay Kamuju from comment #13)
Can we have separate bugs for each of the issue? As they tend to have separate bug fixes and kinda hard to track the fixes.
Sure. I have opened a new bug relating to this issue. Bug56361. I can confirm the CtfImmIsGuidMapEnable stub issue is fixed. (In reply to Louis Lenders from comment #12)
Created attachment 76080 [details] keep wmic alive for 10 secs
Hi, patch for initial bug is now in git as commit 7a92a33b27b3e362c12539d6382dfe6444ed77cf
About the followup bug: in the 2nd log you attached it just exits with error 3, which seems 'path not found' which seems reasonable as wmic is disabled. It's all kind of guess work and this wmic thing just might be a red herring but maybe you could try with attached hack (which should keep wmic alive for 10 secs) if anything changes.
(reason behind hack: on windows, if you just fire up wmic without arguments it will fire up the wmic commander. I haven't got a clue why a program would want this. Anyway, wine will just return an error which is not like how windows does it. As mentioned before: might just be a red herring but maybe worth a try)
It was a try. But did not solve the crashing part, unfortunately. In fact the sleep period on the splash screen was equal to the splash screen display time. I tried some different numbers too.This is what it actually did. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |7a92a33b27b3e362c12539d6382 | |dfe6444ed77cf Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #15 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- this was fixed by 7a92a33b27b3e362c12539d6382dfe6444ed77cf -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=56299 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #16 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 9.4. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla