https://bugs.winehq.org/show_bug.cgi?id=52882
Bug ID: 52882 Summary: Improve software components also for using “GPU Caps Viewer 1.54” Product: Wine Version: 7.7 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 have tried the tool “GPU Caps Viewer 1.54” out together with the software “Wine 7.7-1449.4”.
Markus_Elfring@Sonne:~> wine /home/altes_Heim2/elfring/geladen/Freeware/GPU_Caps_Viewer/GPU_Caps_Viewer.exe 00c4:err:ntoskrnl:ZwLoadDriver failed to create driver L"\Registry\Machine\System\CurrentControlSet\Services\SecDrv": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"SecDrv" failed to start: 1114 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0024:fixme:imm:ImeSetActiveContext (0x28bf30, 1): stub 0024:fixme:imm:ImmReleaseContext (0001004E, 0028BF30): stub 0070:fixme:imm:ImeSetActiveContext (0x5b4b0, 0): stub … 0024:err:wgl:X11DRV_wglGetPixelFormatAttribivARB (0xb010064): unexpected iPixelFormat(0) vs nFormats(247), returns FALSE wine: Unhandled page fault on read access to 00000320 at address 00484738 (thread 0024), starting debugger... … Unhandled exception: page fault on read access to 0x00000320 in 32-bit code (0x00484738). …
See also: https://appdb.winehq.org/objectManager.php?sClass=application&iId=17257
How will the chances evolve to fix remaining open issues?
https://bugs.winehq.org/show_bug.cgi?id=52882
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://geeks3d.com/downloa | |ds/2021p/GPU_Caps_Viewer_Se | |tup_v1.54.0.0.exe Keywords| |download Summary|Improve software components |GPU Caps Viewer 1.54 |also for using “GPU Caps |crashes on start |Viewer 1.54” |
--- Comment #1 from Gijs Vermeulen gijsvrm@gmail.com --- GPU Caps Viewer 1.54 starts just fine for me with wine-7.9-153-gd3378c1441c, can you confirm?
$ sha1sum GPU_Caps_Viewer_Setup_v1.54.0.0.exe b2ec62e58aad18622600d461ffc59717ec29ad7e GPU_Caps_Viewer_Setup_v1.54.0.0.exe
$ du -sh GPU_Caps_Viewer_Setup_v1.54.0.0.exe 12M GPU_Caps_Viewer_Setup_v1.54.0.0.exe
https://bugs.winehq.org/show_bug.cgi?id=52882
--- Comment #2 from Markus Elfring Markus.Elfring@web.de --- (In reply to Gijs Vermeulen from comment #1) I stumbled on remaining open issues also together with the software “Wine 7.9-1455.11”.
Markus_Elfring@Sonne:/home/altes_Heim2/elfring/geladen/Freeware/GPU_Caps_Viewer> wine GPU_Caps_Viewer.exe 00c4:err:ntoskrnl:ZwLoadDriver failed to create driver L"\Registry\Machine\System\CurrentControlSet\Services\SecDrv": c0000142 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"SecDrv" failed to start: 1114 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0024:fixme:imm:ImeSetActiveContext (0028DB38, 1): stub 0024:fixme:imm:ImmReleaseContext (0001004E, 0028DB38): stub 007c:fixme:imm:ImeSetActiveContext (000000000005ABB0, 0): stub 007c:fixme:imm:ImmReleaseContext (0000000000010020, 000000000005ABB0): stub 0024:err:vulkan:wine_vkCreateInstance Failed to create instance, res=-9 0024:err:wgl:X11DRV_WineGL_InitOpenglInfo couldn't initialize OpenGL, expect problems 0024:err:wgl:set_pixel_format Invalid format 0 0024:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFA, 0148FE98
Will corresponding software adjustments trigger any more collateral evolution? https://www.geeks3d.com/20220516/gpu-caps-viewer-1-55-released/
https://bugs.winehq.org/show_bug.cgi?id=52882
--- Comment #3 from Gijs Vermeulen gijsvrm@gmail.com --- (In reply to Markus Elfring from comment #2) - snip -
These messages are not necessarily bugs. Do you actually experience any problems running the software?
https://bugs.winehq.org/show_bug.cgi?id=52882
--- Comment #4 from Markus Elfring Markus.Elfring@web.de --- (In reply to Gijs Vermeulen from comment #3)
These messages are not necessarily bugs.
Do they point details out for further development considerations?
Do you actually experience any problems running the software?
It seems that OpenGL support (for example) evolved into an undesirable direction recently.
https://bugs.winehq.org/show_bug.cgi?id=52882
--- Comment #5 from Gijs Vermeulen gijsvrm@gmail.com --- (In reply to Markus Elfring from comment #4)
(In reply to Gijs Vermeulen from comment #3)
These messages are not necessarily bugs.
Do they point details out for further development considerations?
No.
It seems that OpenGL support (for example) evolved into an undesirable direction recently.
What do you mean by that?
https://bugs.winehq.org/show_bug.cgi?id=52882
--- Comment #6 from Markus Elfring Markus.Elfring@web.de --- (In reply to Gijs Vermeulen from comment #5)
Do they point details out for further development considerations?
No.
I find this view strange.
It seems that OpenGL support (for example) evolved into an undesirable direction recently.
What do you mean by that?
* I would appreciate if the attention will grow also according to mentioned error messages (and not only “program crashes”).
* Do you find the current display status acceptable for this system information tool?
https://bugs.winehq.org/show_bug.cgi?id=52882
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|https://geeks3d.com/downloa |https://www.geeks3d.com/dl/ |ds/2021p/GPU_Caps_Viewer_Se |show/679 |tup_v1.54.0.0.exe | Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #7 from Gijs Vermeulen gijsvrm@gmail.com --- (In reply to Markus Elfring from comment #6)
- I would appreciate if the attention will grow also according to mentioned
error messages (and not only “program crashes”).
Why would that be interesting if the message don't lead to actual problems?
- Do you find the current display status acceptable for this system
information tool?
I'm still not sure what you mean by this.
In any case, for discussion go to https://forum.winehq.org/.
The original crash in this bug is fixed, so marking FIXED.
https://bugs.winehq.org/show_bug.cgi?id=52882
Markus Elfring Markus.Elfring@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |UNCONFIRMED
--- Comment #8 from Markus Elfring Markus.Elfring@web.de --- (In reply to Gijs Vermeulen from comment #7)
I'm still not sure what you mean by this.
I find a display like “OpenGL 1.1 ( with 0 ext.)” inappropriate by this system information tool at the moment. Further display gaps should be reconsidered, shouldn't they?
https://bugs.winehq.org/show_bug.cgi?id=52882
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #9 from Gijs Vermeulen gijsvrm@gmail.com --- (In reply to Markus Elfring from comment #8)
(In reply to Gijs Vermeulen from comment #7)
I'm still not sure what you mean by this.
I find a display like “OpenGL 1.1 ( with 0 ext.)” inappropriate by this system information tool at the moment. Further display gaps should be reconsidered, shouldn't they?
Yes, further bugs in the application should be reported. However, we have a one bug per report policy here and this bug was about the app crashes, which is fixed.
So please open a new bug report for the next issue.
https://bugs.winehq.org/show_bug.cgi?id=52882
--- Comment #10 from Markus Elfring Markus.Elfring@web.de --- (In reply to Gijs Vermeulen from comment #9)
So please open a new bug report for the next issue.
I am curious how the clarification will be continued.
Improve software components also for using “GPU Caps Viewer 1.55” https://bugs.winehq.org/show_bug.cgi?id=53062
https://bugs.winehq.org/show_bug.cgi?id=52882
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #11 from Zeb Figura z.figura12@gmail.com --- (In reply to Markus Elfring from comment #6)
(In reply to Gijs Vermeulen from comment #5)
Do they point details out for further development considerations?
No.
I find this view strange.
Wine error and fixme messages are meant *solely* as diagnostic tools, that point out *potential* problems with a program. If it was important that users read them, we wouldn't put them somewhere they might never be seen (after all, most users aren't even running Wine from terminal).
https://bugs.winehq.org/show_bug.cgi?id=52882
--- Comment #12 from Markus Elfring Markus.Elfring@web.de --- (In reply to Zeb Figura from comment #11)
Wine error and fixme messages are meant *solely* as diagnostic tools,
I am trying also to treat the provided information in this way.
that point out *potential* problems with a program.
I reported problematic software behaviour accordingly.
If it was important that users read them,
Some software developers found it relevant and potentially helpful to log special data.
we wouldn't put them somewhere they might never be seen
Does this wording contain a contradiction?
(after all, most users aren't even running Wine from terminal).
It can be checked if presented data would indicate further improvement possibilities, can't it?
https://bugs.winehq.org/show_bug.cgi?id=52882
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #13 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 7.10.
-
WineHQ Bugzilla