https://bugs.winehq.org/show_bug.cgi?id=51673
Bug ID: 51673 Summary: Installation issues in The Settlers: Heritage of Kings Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: Markus.Elfring@web.de Distribution: ---
I could install the game “The settlers (gold edition)” once more by components from the software package “wine-6.13-1.fc34”.
Some information was logged for further development considerations.
[Markus_Elfring@fedora SHOK_GOLD]$ wine start setup.exe 002c:fixme:winediag:LdrInitializeThunk wine-staging 6.13 is a testing version containing experimental patches. … 0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. … 011c:err:ole:TLB_ReadTypeLib Loading of typelib L"C:\Program Files (x86)\Common Files\InstallShield\Professional\RunTime\IsProBE.tlb" failed with error 2 011c:fixme:file:NtLockFile I/O completion on lock not implemented yet 011c:fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0061DDAC L"Z:\run\media\Markus_Elfring\SHOK_GOLD\data1.hdr" 011c:err:richedit:ReadStyleSheet skipping optional destination … 0138:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0138:fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030 0138:fixme:wbemprox:enum_class_object_Next timeout not supported 0138:fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. 011c:fixme:sfc:SRSetRestorePointA 01F6E900 01F6E9A8 … 0224:err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-2401-000018010000} 0220:err:rpc:I_RpcReceive we got fault packet with status 0x80010108 … 0218:fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. … 0250:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x44da8b 026c:fixme:advapi:RegisterEventSourceA ((null)," "): stub 026c:fixme:advapi:RegisterEventSourceW (L"",L" "): stub 026c:fixme:advapi:ReportEventA (CAFE4242,0x0001,0x0000,0x00000000,00000000,0x0001,0x00000060,00FAFAF4,00FF3D2A): stub 026c:fixme:advapi:ReportEventW (CAFE4242,0x0001,0x0000,0x00000000,00000000,0x0001,0x00000060,006DE4E8,00FF3D2A): stub 026c:err:eventlog:ReportEventW L"6" … 026c:fixme:advapi:DeregisterEventSource (CAFE4242) stub
Unfortunately, the start attempt of the game (as it was offered by the installation program from an original CD) failed. Now I am curious how the affected software will evolve accordingly.
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #1 from Markus Elfring Markus.Elfring@web.de --- (In reply to comment #0) I could install the game “The settlers (gold edition)” once more by components from the software package “wine 7.0-1417.4”.
Some information was logged for further development considerations.
Markus_Elfring@Sonne:/run/media/Markus_Elfring/SHOK_GOLD> wine setup.exe 0070:fixme:imm:ImeSetActiveContext (0x400a0, 0): stub 0070:fixme:imm:ImmReleaseContext (0000000000010020, 00000000000400A0): stub 0104:fixme:imm:ImeSetActiveContext (0x43ce48, 1): stub 0104:fixme:imm:ImmReleaseContext (00020042, 0043CE48): stub 0100:err:ole:TLB_ReadTypeLib Loading of typelib L"C:\Program Files (x86)\Common Files\InstallShield\Professional\RunTime\IsProBE.tlb" failed with error 2 0100:fixme:file:NtLockFile I/O completion on lock not implemented yet 0100:fixme:apphelp:ApphelpCheckInstallShieldPackage stub: 0032DDAC L"Z:\run\media\Markus_Elfring\SHOK_GOLD\data1.hdr" 0100:err:richedit:ReadStyleSheet skipping optional destination 011c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 011c:fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030 011c:fixme:wbemprox:enum_class_object_Next timeout not supported 011c:fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. 011c:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work. wine: Read access denied for device L"\??\Z:\", FS volume label and serial are not available. 0100:fixme:sfc:SRSetRestorePointA 0218D7F8 0218D8A0 … 0208:err:ole:dispatch_rpc no apartment found for ipid {ffffffff-ffff-ffff-0801-0000fc000000} 0204:err:rpc:I_RpcReceive we got fault packet with status 0x80010108 … 01fc:fixme:wbemprox:enum_class_object_Next timeout not supported 01fc:fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. 01fc:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work. … 0240:err:ole:CoUninitialize Mismatched CoUninitialize 0234:fixme:dbghelp_dwarf:dwarf2_read_range no entry found … 0234:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x44da8b 024c:fixme:advapi:RegisterEventSourceA ((null)," "): stub 024c:fixme:advapi:RegisterEventSourceW (L"",L" "): stub 024c:fixme:advapi:ReportEventA (CAFE4242,0x0001,0x0000,0x00000000,00000000,0x0001,0x00000060,00F5FAF4,00FA313A): stub 024c:fixme:advapi:ReportEventW (CAFE4242,0x0001,0x0000,0x00000000,00000000,0x0001,0x00000060,004253F0,00FA313A): stub 024c:err:eventlog:ReportEventW L"6" …
https://bugs.winehq.org/show_bug.cgi?id=51673
Sven Grewe svengrewe@posteo.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |svengrewe@posteo.de
--- Comment #2 from Sven Grewe svengrewe@posteo.de --- According to other reports from you I would guess that an installation issue doesn't appear any more in the latest WINE development release, am I right?
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #3 from Markus Elfring Markus.Elfring@web.de --- (In reply to Sven Grewe from comment #2) It is likely that some messages will remain for further software development considerations.
https://bugs.winehq.org/show_bug.cgi?id=51673
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1
--- Comment #4 from Gijs Vermeulen gijsvrm@gmail.com --- Do you experience any issues with this app with wine-9.0rc1? Because it seems the original problem was not an installation issue at all, judging by your comment:
"Unfortunately, the start attempt of the game (as it was offered by the installation program from an original CD) failed."
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #5 from Markus Elfring Markus.Elfring@web.de --- (In reply to Gijs Vermeulen from comment #4) Would any more contributors become interested to take another look at previously shown messages which I found questionable anyhow?
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #6 from Gijs Vermeulen gijsvrm@gmail.com --- (In reply to Markus Elfring from comment #5)
(In reply to Gijs Vermeulen from comment #4) Would any more contributors become interested to take another look at previously shown messages which I found questionable anyhow?
Logged messages do not necessarily indicate a problem and don't need to be reported. I just want to know if the issue of the game not working for you is fixed.
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #7 from Markus Elfring Markus.Elfring@web.de --- (In reply to Gijs Vermeulen from comment #6)
Logged messages do not necessarily indicate a problem and don't need to be reported.
I suggest to reconsider this view.
The shown messages indicated open issues of varying importance, didn't they?
I just want to know if the issue of the game not working for you is fixed.
The game support was improved for some technical details in the meantime.
Example: Memory allocation difficulties were reported during runs of the Settlers: Heritage of Kings. https://bugs.winehq.org/show_bug.cgi?id=55524
But I guess that further issues remain also for safer software installations.
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #8 from Alexandre Julliard julliard@winehq.org --- Please describe the actual issue you are having with the game installation, if any.
Error messages by themselves are not bugs, and if there's no other issue with the app they can be safely ignored.
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #9 from Markus Elfring Markus.Elfring@web.de --- (In reply to Alexandre Julliard from comment #8)
Error messages by themselves are not bugs,
I tend to interpret such messages in the way that mentioned implementation details can be improved further.
and if there's no other issue with the app they can be safely ignored.
Were affected technical details actually fixed by any recent contributions?
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #10 from Sven Grewe svengrewe@posteo.de --- Created attachment 75666 --> https://bugs.winehq.org/attachment.cgi?id=75666 Console Output with WINE 9.0rc1 containing at least some of the FIXMEs
I tested the installer (setup.exe not autorun.exe) with the newest development version (9.0rc1) and can reproduce at least some(?) FIXMEs. The installation end without an error dialog.
https://bugs.winehq.org/show_bug.cgi?id=51673
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEEDINFO |RESOLVED
--- Comment #11 from Alexandre Julliard julliard@winehq.org --- (In reply to Markus Elfring from comment #9)
(In reply to Alexandre Julliard from comment #8)
Error messages by themselves are not bugs,
I tend to interpret such messages in the way that mentioned implementation details can be improved further.
That would be a waste of time. There are many things in the Windows API that are not actually used by applications, so we only implement things once it turns out that they are truly necessary.
I'll close this report then, feel free to reopen if I misunderstood and there was some real issue apart from the debug messages.
https://bugs.winehq.org/show_bug.cgi?id=51673
Markus Elfring Markus.Elfring@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Status|RESOLVED |REOPENED
--- Comment #12 from Markus Elfring Markus.Elfring@web.de --- (In reply to Alexandre Julliard from comment #11)
That would be a waste of time. There are many things in the Windows API that are not actually used by applications, so we only implement things once it turns out that they are truly necessary.
There is probably a conflict because of limited development resources.
I'll close this report then, feel free to reopen if I misunderstood and there was some real issue apart from the debug messages.
Some messages indicated: * Missing and incomplete functionality which could influence software installation attempts in undesirable ways.
* Software crashes
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #13 from Alexandre Julliard julliard@winehq.org --- (In reply to Markus Elfring from comment #12)
Some messages indicated:
- Missing and incomplete functionality which could influence software
installation attempts in undesirable ways.
- Software crashes
Ignoring the messages, did the app install successfully or not?
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #14 from Zeb Figura z.figura12@gmail.com --- (In reply to Markus Elfring from comment #12)
(In reply to Alexandre Julliard from comment #11)
That would be a waste of time. There are many things in the Windows API that are not actually used by applications, so we only implement things once it turns out that they are truly necessary.
There is probably a conflict because of limited development resources.
If we had infinite development resources, sure, we could implement everything without caring whether it was used or not. But that's not the case, and implementing things that aren't use not only takes time but has a cost in terms of maintenance burden.
As such it's not even useful to keep bugs open to track every FIXME. If we even had a reason to track FIXMEs, which we don't, the FIXME messages in the code themselves are good enough for that.
Trying to argue otherwise will not get you very far in this bug tracker.
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #15 from Markus Elfring Markus.Elfring@web.de --- (In reply to Alexandre Julliard from comment #13) I got the impression that doubts can occur for the “software installation success” when the first game start (which can be usually performed also by the installation program) triggers an immediate software crash (according to an “unhandled exception”).
See also another related report. https://bugs.winehq.org/show_bug.cgi?id=54277
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #16 from Markus Elfring Markus.Elfring@web.de --- (In reply to Zeb Figura from comment #14) Do any developers tend to mark source code places in mentioned ways because specific functionality should actually be used? https://en.wikipedia.org/wiki/Comment_%28computer_programming%29#Tags
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #17 from Sven Grewe svengrewe@posteo.de --- https://wiki.winehq.org/Wine_Developer%27s_Guide/Debug_Logging
As an example you can get the following console line when you start the setup.exe :
0100:err:ole:TLB_ReadTypeLib Loading of typelib L"C:\Program Files (x86)\Common Files\InstallShield\Professional\RunTime\IsProBE.tlb" failed with error 2
This is an output from the following code I guess:
https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/oleaut32/typelib.c
I'm not a developer though and the installer isn't broken. Is there any difference in how THIS one installer works on WINE and on Windows if you turn off WINE-specific logs?
https://bugs.winehq.org/show_bug.cgi?id=51673
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #18 from Zeb Figura z.figura12@gmail.com --- (In reply to Markus Elfring from comment #16)
(In reply to Zeb Figura from comment #14) Do any developers tend to mark source code places in mentioned ways because specific functionality should actually be used? https://en.wikipedia.org/wiki/Comment_%28computer_programming%29#Tags
I'm having trouble parsing your sentence (using simpler English in general would be appreciated), but if I understand your implication correctly, that's not what FIXME means in Wine, at least not when it's used in logging.
Even in other projects, a comment saying "this code should be fixed" is not grounds to file a bug for fixing the code. It is especially not grounds to argue with developers after they have told you to stop filing such bugs.
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #19 from Markus Elfring Markus.Elfring@web.de --- (In reply to Zeb Figura from comment #18) We came along different expectations for the application of setup program versions. It is probably known that their support can be challenging for the Wine run time environment.
I guess that it can be more likely to achieve a nice subsequent game run if it could be assured that the needed software was really successfully installed.
https://bugs.winehq.org/show_bug.cgi?id=51673
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be Status|REOPENED |RESOLVED Resolution|--- |INVALID
--- Comment #20 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
(In reply to Markus Elfring from comment #16)
(In reply to Zeb Figura from comment #14) Do any developers tend to mark source code places in mentioned ways because specific functionality should actually be used? https://en.wikipedia.org/wiki/Comment_%28computer_programming%29#Tags
Yes. There are a lot of TODOs & FIXMEs and other notes in the wine source code. You may find them by searching the source code with a combination of 'find' and 'grep' commands.
(In reply to Sven Grewe from comment #17)
I'm not a developer though and the installer isn't broken. Is there any difference in how THIS one installer works on WINE and on Windows if you turn off WINE-specific logs?
No. The differences between WINE and Windows remains the same whether the logs are on or off, though, admittedly, some channels can be very verbose and cause performance degradation because the terminal doesn't scroll fast enough for such amount of text and that delays wine operation. That's why those channels are off by default.
Now back to topic;
According to the bug description and comment 13, the crash happened when starting the application and not when running the installer.
Since there is no information about the crash in this bug, I assume that the mentioned crash is the same as bug 54277 which the OP has never responded to.
Whether the crash from bug 54277 is caused by a bad install or not, it must be analyzed in that bug.
So please, if the application is still crashing with recent wine, provide feedback in the unresolved bug.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #21 from Markus Elfring Markus.Elfring@web.de --- (In reply to Sven Grewe from comment #17)
0100:err:ole:TLB_ReadTypeLib Loading of typelib L"C:\Program Files (x86)\Common Files\InstallShield\Professional\RunTime\IsProBE.tlb" failed with error 2
I suggest to take another look at mentioned details and corresponding background information. This error message might be another opportunity to reconsider the proper handling of such a OLE type library. It can be still unclear how relevant it would be for further execution of involved run rime components. https://en.wikipedia.org/wiki/InstallShield
https://bugs.winehq.org/show_bug.cgi?id=51673
--- Comment #22 from Markus Elfring Markus.Elfring@web.de --- (In reply to Olivier F. R. Dierick from comment #20)
Since there is no information about the crash in this bug, …
How does this feedback fit to hints according to “unhandled exception”?
https://bugs.winehq.org/show_bug.cgi?id=51673
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #23 from Austin English austinenglish@gmail.com --- Closing.
-
WineHQ Bugzilla