- wine-bugs - winehq.org

[Bug 18556] New: Slingplayer 2.0 fails to connect to Slingbox
by wine-bugs＠winehq.org 28 May '22

28 May '22

http://bugs.winehq.org/show_bug.cgi?id=18556 Summary: Slingplayer 2.0 fails to connect to Slingbox Product: Wine Version: 1.1.21 Platform: PC URL: http://download.slingmedia.com/player/pc/SP2/SlingPlay er-2.0.3508-Setup-EMEA.exe OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: quartz AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Created an attachment (id=21217) --> (http://bugs.winehq.org/attachment.cgi?id=21217) wine-1.1.21-316-g8f33420 +quartz (ignore HTML errors) Slingplayer 2.0 throws up an error message when trying to connect to the Slingbox and refuses to connect. "Operation failed with unknown error. (Context: 0, Operation: 0, Error: 0x80040207)" To get this far, "winetricks dotnet20 gdiplus urlmon wme9" is required. Workaround is native quartz.dll. -- 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 9154] Balls of Steel demo v1.3 fails to start a game (ddraw7_WaitForVerticalBlank stub too fast, needs real implementation)
by WineHQ Bugzilla 28 May '22

28 May '22

https://bugs.winehq.org/show_bug.cgi?id=9154 Benjamin Legendre <legendre.benjamin(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |legendre.benjamin(a)gmail.com -- 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.

1 0

[Bug 53018] New: Foxit Editor crashes
by WineHQ Bugzilla 28 May '22

28 May '22

https://bugs.winehq.org/show_bug.cgi?id=53018 Bug ID: 53018 Summary: Foxit Editor crashes Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dezdigado(a)yahoo.com Distribution: --- Created attachment 72385 --> https://bugs.winehq.org/attachment.cgi?id=72385 Foxit editor log when crashing on edit object The editor works when editing text, numbers etc.. when double clicking to edit object, picture or whatever it crashes -- 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.

1 13

[Bug 52859] New: Call of Duty: Ghosts has an issue with terrain rendering
by WineHQ Bugzilla 27 May '22

27 May '22

https://bugs.winehq.org/show_bug.cgi?id=52859 Bug ID: 52859 Summary: Call of Duty: Ghosts has an issue with terrain rendering Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 72258 --> https://bugs.winehq.org/attachment.cgi?id=72258 example With setting "Terrain Detail" option to Normal or Extra 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1006 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_context_gl_reacquire Acquired context 0000000011013CA0 instead of 000000001E91E3D0. 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1010 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1014 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1018 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1000 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1004 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1128 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1018 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1004 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1128 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1154 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1133 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1128 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1006 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1014 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1018 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1004 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1000 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1154 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1023 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1032 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1045 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1136 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1139 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1058 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1166 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1143 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1062 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1067 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1072 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1124 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1168 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1077 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1081 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1085 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1158 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1130 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1146 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1090 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1058 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1062 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1162 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1093 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1149 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1172 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1101 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1103 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElements". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1104 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glUseProgram(program 1108 not linked)". 0504:err:d3d:wined3d_debug_callback 0000000011013CA0: "GL_INVALID_OPERATION in glDrawElementsInstanced". wine-7.6-324-gd141e354568 -- 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.

1 2

[Bug 52891] New: RutonyChat
by WineHQ Bugzilla 27 May '22

27 May '22

https://bugs.winehq.org/show_bug.cgi?id=52891 Bug ID: 52891 Summary: RutonyChat Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jon9097(a)gmail.com Distribution: --- Created attachment 72284 --> https://bugs.winehq.org/attachment.cgi?id=72284 Log RutonyChat does not work properly. This is a useful program that I really need. I don't know how to get its log properly. Because it only runs through steam. I attach the log I was able to get with the command: steam &> /disks/D/imLEGR/Test/RutonyChat_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.

1 4

[Bug 53050] New: Horizon Zero Dawn Crashes with DXVK enabled
by WineHQ Bugzilla 27 May '22

27 May '22

https://bugs.winehq.org/show_bug.cgi?id=53050 Bug ID: 53050 Summary: Horizon Zero Dawn Crashes with DXVK enabled Product: Wine Version: 7.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 72446 --> https://bugs.winehq.org/attachment.cgi?id=72446 Logfile To get this game started i installed MFC140 via winetricks and to get the directX Rendering of the ground i used DXVK 1.10.1 Unfortunately the game still crashes. -- 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.

1 3

[Bug 53044] New: Some Games will not start
by WineHQ Bugzilla 27 May '22

27 May '22

https://bugs.winehq.org/show_bug.cgi?id=53044 Bug ID: 53044 Summary: Some Games will not start Product: Wine Version: 7.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: slayersnet2012(a)gmail.com Distribution: --- Games crash with this error For Example: Atlantis.exe (Reflexive Arcade) 0024:err:virtual:virtual_setup_exception stack overflow 888 bytes in thread 0024 addr 0x7bc5469a stack 0x6d0c88 (0x6d0000-0x6d1000-0x7d0000) -- 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.

1 8

[Bug 53006] New: Carmageddon 2 crash on launch
by WineHQ Bugzilla 27 May '22

27 May '22

https://bugs.winehq.org/show_bug.cgi?id=53006 Bug ID: 53006 Summary: Carmageddon 2 crash on launch Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legendre.benjamin(a)gmail.com Distribution: --- Created attachment 72375 --> https://bugs.winehq.org/attachment.cgi?id=72375 execution logs Carmageddon 2 crash on launch with wine 7.7 (and maybe older ones as i have not tried this game for a long time): 0608:fixme:vxd:__wine_vxd_open Unknown/unsupported VxD L"siwvid.vxd". Try setting Windows version to 'nt40' or 'win31'. 0608:fixme:vxd:__wine_vxd_open Unknown/unsupported VxD L"ntice.vxd". Try setting Windows version to 'nt40' or 'win31'. wine: Unhandled page fault on read access to 64284CEE at address 0040D81C (thread 0608), starting debugger... 0610:fixme:imm:ImeSetActiveContext (0x141960, 1): stub 0610:fixme:imm:ImmReleaseContext (0016004E, 00141960): stub Unhandled exception: page fault on read access to 0x64284cee in 32-bit code (0x0040d81c). See attachment for full log with register dump. winearch: win32 / version: win98. Some additional notes: - Tried as well with a cue/bin image of the Europe version of the game i found on archive.org (using cdemu) with same results. - Tried to change to winnt/win3x/winxp, but the game complains it is not compatible with theses versions. - The beta version demo does works though. But this version could be hardly compared to original official release as it seems very different from the original game. The demo can be found here: <https://archive.org/details/Carmageddon2CarpocalypseNowDemo>. I suspect a bug sitting around the copy protection. This game is protected with SafeDisc 1.00.026. Just stumb upon this old 2008 closed bug which seems to describe the same issue: <https://forum.winehq.org/viewtopic.php?t=2830>. But since 2008 there have been a lot of improvment related to copy protection support and now Wine support Safedisc 1. -- 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.

1 12

[Bug 53046] New: upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors
by WineHQ Bugzilla 27 May '22

27 May '22

https://bugs.winehq.org/show_bug.cgi?id=53046 Bug ID: 53046 Summary: upgrading from WINE 5.0.3 to 7.0, winecfg throws several missing components errors Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tkocou(a)protonmail.com Distribution: --- Created attachment 72438 --> https://bugs.winehq.org/attachment.cgi?id=72438 A capture of the error messages about missing DLL components I attempted to upgrade the WINE from 5.0.3 to WINEHQ Stable 7.0. When I ran "winecfg" after the upgrade, it complained about missing DLL components. This same situation occurred after installing WINEHQ development version 7.9. Regressing to version 5.0.3 eliminated the missing DLL errors. During the installation of HQ stable, I copied the missing DLLs to WINE. "winecfg" stopped sending errors about missing DLL and complained about not being able to run "wineboot.exe" I regressed WINE to 5.0.3 for now. -- 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.

1 9

[Bug 23569] New: Certain keyboard keys don't work in Wine when using VNC
by wine-bugs＠winehq.org 26 May '22

26 May '22

http://bugs.winehq.org/show_bug.cgi?id=23569 Summary: Certain keyboard keys don't work in Wine when using VNC Product: Wine Version: 1.2-rc6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P1 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: WillWill56(a)gmail.com Bug: While connected to a computer via VNC, certain keys that work perfectly fine in native programs on the remote computer are not picked up in Wine programs on the remote computer. Example: Holding shift and pressing the keys 1234567890 in gedit produces "!@#$%^&*()", but typing the same into Wine Notepad produces "12345678", showing that the shift key and curved brackets are not getting from VNC to Wine. Speculation: Keys should be sent VNC Client --> VNC Server --> Wine, but somewhere along the line the process is broken. But when keys are sent VNC Client --> VNC Server --> Generic GNOME App it works fine. Reproduction: The VNC Client is RealVNC on Windows XP SP3, and the VNC Server is x11vnc on Ubuntu 10.04 (previously tried Ubuntu's built in VNC server, same bug occured) (this may not matter, but try an Ubuntu -> Ubuntu VNC connection and see if the bug occurs). Try holding shift and typing capital text, curved brackets, symbols etc into a simple Wine app like Notepad running on the Ubuntu computer, then try typing the same into a simple GNOME app like gedit. -- 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 24

[Bug 53048] New: red dead redemption 2
by WineHQ Bugzilla 26 May '22

26 May '22

https://bugs.winehq.org/show_bug.cgi?id=53048 Bug ID: 53048 Summary: red dead redemption 2 Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jon9097(a)gmail.com Distribution: --- Created attachment 72441 --> https://bugs.winehq.org/attachment.cgi?id=72441 Log The game won't start. Launching through the "rockstar games launcher". The game just won't start. I'm attaching the logs of the following actions: 1) WINEPREFIX=/disks/G/Games/RDR2/ wine "/disks/G/Games/RDR2/drive_c/Program Files/Rockstar Games/Launcher/Launcher.exe" &> /disks/D/imLEGR/Test/logs/rdr2.txt 2) The rockstar games launcher opens. In it I launch "red dead redemption 2" it does not start, then try again. The most annoying thing is that my friend has exactly the same computer and system (everything is exactly the same as mine). Only he uses a pirated version of the game and it all works fine. But I have a license and nothing works. -- 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.

1 7

[Bug 53036] New: PC_Connect .exe app not launching.
by WineHQ Bugzilla 26 May '22

26 May '22

https://bugs.winehq.org/show_bug.cgi?id=53036 Bug ID: 53036 Summary: PC_Connect .exe app not launching. Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: srkrishnan1989(a)gmail.com Distribution: --- Created attachment 72403 --> https://bugs.winehq.org/attachment.cgi?id=72403 backtrace.txt file and error error screen PC_Connect3.2.6.03110_release.exe app download link is https://connect.oppo.com/en-US , error popup, I have included backtrace.txt file -- 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.

1 3

[Bug 53030] New: I tried to open an app, and got this error log back, which told me to report here (and did not open the app). the app was Jurassic world on steam
by WineHQ Bugzilla 25 May '22

25 May '22

https://bugs.winehq.org/show_bug.cgi?id=53030 Bug ID: 53030 Summary: I tried to open an app, and got this error log back, which told me to report here (and did not open the app). the app was Jurassic world on steam Product: Wine Version: 0.9.3. Hardware: arm OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: halls-manga-0j(a)icloud.com Created attachment 72401 --> https://bugs.winehq.org/attachment.cgi?id=72401 Some seemingly gibberish that the Wine app gave me when it failed to load an app I am not sure what happened, I opened Jurassic world evolution through steam on crossover, I have an M1 Max Mac, and the app failed to load, and wine gave me an error message and told me to report it here, saying that it was an error caused that could not have happened on a windows machine. so I decided to report it as I was told to. (also I didn't know what the severity options meant, like they should be more specific, as in is it talking about the severity of the bug to my machine or to wine as a whole? and how severe is critical vs blocker?) -- 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.

1 3

[Bug 53043] New: DA:Inquisition - Wrong color in game with OpenGL renderer
by WineHQ Bugzilla 25 May '22

25 May '22

https://bugs.winehq.org/show_bug.cgi?id=53043 Bug ID: 53043 Summary: DA:Inquisition - Wrong color in game with OpenGL renderer Product: Wine Version: 7.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Created attachment 72429 --> https://bugs.winehq.org/attachment.cgi?id=72429 screenshot with OpenGL renderer Hi, Since the game crashes at launch with vulkan renderer, i tried it with OpenGL. The game work but there are some glitches in-game as you can see in the screenshot (sword, shield, iron boots) I compress the +d3d,+d3d11,+dxgi log (~9Gb), i'll post the mediafire link later -- 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.

1 3

[Bug 53021] New: ChemDraw 21.0 crashes on use of the Page Setup button
by WineHQ Bugzilla 25 May '22

25 May '22

https://bugs.winehq.org/show_bug.cgi?id=53021 Bug ID: 53021 Summary: ChemDraw 21.0 crashes on use of the Page Setup button Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: florian.schreiner(a)protonmail.com Distribution: --- Created attachment 72392 --> https://bugs.winehq.org/attachment.cgi?id=72392 Stacktrace of the crash If run in a fresh, unmodified wine prefix, ChemDraw will install correctly using a workaround but won't run. To remediate this gdiplus was installed via winetricks. After that all basic functionality is restored and ChemDraw can be used for simple 2D editing. On use of the page setup button ChemDraw crashes. Steps to reproduce: 1. Download ChemDraw and extract the 32-bit .msi from the .exe 3. Install gdiplus using 'winetricks gdiplus' 3. Install the .msi using 'msiexec -i PerkinElmer_ChemOffice_Suite_2021_21.0.0.msi' 4. Open ChemDraw and use the page setup button Expected behavior: A dialog opens and paper size can be set. Actual behavior: When the 'page setup' button is clicked, ChemDraw will crash (most of the times, especially if not run for the first time and a stylesheet is used) with the stacktrace indicating that comdlg32 is at fault (more precisely comdlg32\printdlg.c:3179). Additional info: This behavior can be observed using 64- and 32-bit prefixes. Wine was installed from the winehq-staging package, version 7.8-staging. System info: OS: Kubuntu 22.04 Kernel Version: 5.15.0-30-generic -- 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.

1 29

[Bug 53041] New: Foxit Editor 2.2 installer crashes
by WineHQ Bugzilla 23 May '22

23 May '22

https://bugs.winehq.org/show_bug.cgi?id=53041 Bug ID: 53041 Summary: Foxit Editor 2.2 installer crashes Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- * Assertion at /vagrant/mono/mono/metadata/object.c:4677, condition `is_ok (error)' not met, function:prepare_run_main, Could not load type of field '.:' (0) due to: Could not resolve type with token 01000001 from typeref (expected class 'GenericSetup.Program' in assembly 'GenericSetu p, Version=6.91.0.0, Culture=neutral, PublicKeyToken=null') assembly:GenericSetup, Version=6.91.0.0, Culture=neutral, PublicKeyToken=null type:GenericSetup.Program member:(null) assembly:C:\users\fabian\Temp\7zS02002E5C\GenericSetup.exe type: member:(null) Alternative is extraction with 7z. -- 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.

1 2

[Bug 53040] New: Chemdraw 21.0 installation crashes on clicking install
by WineHQ Bugzilla 23 May '22

23 May '22

https://bugs.winehq.org/show_bug.cgi?id=53040 Bug ID: 53040 Summary: Chemdraw 21.0 installation crashes on clicking install Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: florian.schreiner(a)protonmail.com Distribution: --- Created attachment 72416 --> https://bugs.winehq.org/attachment.cgi?id=72416 Error message Steps to replicate the issue: 1. WINEARCH=win32 winetricks vb6run 2. wine cos21.0.0.exe 3. accept the license agreement, click to the final dialog, click install Expected behavior: The application will be installed Actual behavior: After a few seconds a second dialog box with an error message appears reading: """ Run-time error '35601' Element not found """ -- 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.

1 2

[Bug 3548] .lnk file is created on the desktop together with the program icon...
by WineHQ Bugzilla 23 May '22

23 May '22

https://bugs.winehq.org/show_bug.cgi?id=3548 winetaste(a)gmx.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetaste(a)gmx.net -- 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.

1 0

[Bug 53039] New: WineFile cannot be opened on Windows 11 Pro
by WineHQ Bugzilla 23 May '22

23 May '22

https://bugs.winehq.org/show_bug.cgi?id=53039 Bug ID: 53039 Summary: WineFile cannot be opened on Windows 11 Pro Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: njlyf2011(a)hotmail.com Distribution: --- Created attachment 72413 --> https://bugs.winehq.org/attachment.cgi?id=72413 winefile window Its window does not correspond when opened. This happens with the winfile program in ReactOS and Wine. OS: Windows 11 Pro Builld 22621 Resolution: 2880*1800 -- 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.

1 1

[Bug 49910] New: Heroes of Might and Magic 3 crashes on startup
by WineHQ Bugzilla 22 May '22

22 May '22

https://bugs.winehq.org/show_bug.cgi?id=49910 Bug ID: 49910 Summary: Heroes of Might and Magic 3 crashes on startup Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: elk_aide(a)startmail.com Distribution: --- Created attachment 68278 --> https://bugs.winehq.org/attachment.cgi?id=68278 console log for Heroes3 crash Running Debian bullseye with the package wine/testing,testing,now 5.0-4 Heroes 3 Complete from GOG.com (This crash does not happen with the 'h3hota HD.exe' shipped with the Horn of the Abyss mod http://heroescommunity.com/viewthread.php3?TID=39830) -- 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.

1 3

[Bug 20459] New: Fallen Earth updater does not start
by wine-bugs＠winehq.org 22 May '22

22 May '22

http://bugs.winehq.org/show_bug.cgi?id=20459 Summary: Fallen Earth updater does not start Product: Wine Version: 1.1.32 Platform: PC URL: http://www.fallenearth.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: l_bratch(a)yahoo.co.uk Created an attachment (id=24327) --> (http://bugs.winehq.org/attachment.cgi?id=24327) Terminal output The installer for this game works fine, but the built in updater required to play does not start. Terminal output attached. The terminal output doesn't have any backtrace, but there is a message back produced which says: A fatal error occured in Fallen Earth Updater and it needs to close! [EXCEPTION_ACCESS_VIOLATION @ 0x7D97DF1D] -- 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 22

[Bug 42401] New: cscript.exe has no help
by wine-bugs＠winehq.org 22 May '22

22 May '22

https://bugs.winehq.org/show_bug.cgi?id=42401 Bug ID: 42401 Summary: cscript.exe has no help Product: Wine-gecko Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gecko-unknown Assignee: jacek(a)codeweavers.com Reporter: kolan_n(a)mail.ru Distribution: --- cscript.exe /? outputs nothing -- 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 17973] New: explorer: Spaces in desktop title on CLI cause both wrong window title and command
by wine-bugs＠winehq.org 21 May '22

21 May '22

http://bugs.winehq.org/show_bug.cgi?id=17973 Summary: explorer: Spaces in desktop title on CLI cause both wrong window title and command Product: Wine Version: 1.1.13 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: shacklein(a)gmail.com When using the form: $ wine explorer /desktop=Title,WxH program.exe Title currently cannot contain spaces. Example: $ wine explorer /desktop=My\ Program,800x600 myprogram.exe This correctly detects the size 800x600 for the virtual desktop, but it sets the title of the window to "My" and tries to run "Program" as the command line. I've submitted a patch to wine-patches that fixes this problem (and afaik, doesn't introduce any new ones), though I'm not sure if it's really "neat" enough. http://www.winehq.org/pipermail/wine-patches/2009-March/070776.html So far, I've had no feedback about it. At the least, I'd like to be told why it's not suitable for inclusion, or if there's any cleaning up I need to do to it :) -- 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 53025] New: Port Royale 4 crashes with IDXGISwapChain4_CheckColorSpaceSupport
by WineHQ Bugzilla 21 May '22

21 May '22

https://bugs.winehq.org/show_bug.cgi?id=53025 Bug ID: 53025 Summary: Port Royale 4 crashes with IDXGISwapChain4_CheckColorSpaceSupport Product: Wine Version: 7.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Created attachment 72397 --> https://bugs.winehq.org/attachment.cgi?id=72397 IDXGISwapChain4_CheckColorSpaceSupport backtrace - Hello, I bought Port Royale 4 on GoG and when i try to launch it with OpenGL/Vulkan renderer, the game crashes. I have a backtrace about dxgi error as you can see in the attached file. No issue with DXVK. -- 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.

1 3

[Bug 46008] New: Support CUDA 10.0 compiled apps like new mfaktc v0.21 binary..
by wine-bugs＠winehq.org 21 May '22

21 May '22

https://bugs.winehq.org/show_bug.cgi?id=46008 Bug ID: 46008 Summary: Support CUDA 10.0 compiled apps like new mfaktc v0.21 binary.. Product: Wine-staging Version: 3.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rtfss1(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 62580 --> https://bugs.winehq.org/attachment.cgi?id=62580 output Hi, just downloaded new mfaktc binary compiled with CUDA10 which adds support for new Nvidia Turing GPUs like RTX 2080.. from here: https://www.mersenneforum.org/mfaktc/mfaktc-0.21/mfaktc-0.21.win.cuda100.zip the app is a "simple" command line app so it should work OK with wine if it wasn't compiled with new CUDA10.. on Windows works ok but using latest Wine-Staging 3.18 (as staging is still required for CUDA support right?) no.. the app isn't detecting runtime version OK: CUDA runtime version 13697.32 CUDA driver version 10.0 ERROR: CUDA runtime version must match the CUDA toolkit version used during compile! full log attached.. -- 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 3548] .lnk file is created on the desktop together with the program icon...
by WineHQ Bugzilla 21 May '22

21 May '22

https://bugs.winehq.org/show_bug.cgi?id=3548 mirh <mirh(a)protonmail.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mirh(a)protonmail.ch -- 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.

1 0

[Bug 53024] New: wine-7.9 build fails in x86_64 Ubuntu 22.04
by WineHQ Bugzilla 21 May '22

21 May '22

https://bugs.winehq.org/show_bug.cgi?id=53024 Bug ID: 53024 Summary: wine-7.9 build fails in x86_64 Ubuntu 22.04 Product: Wine Version: 7.9 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net Distribution: --- Created attachment 72396 --> https://bugs.winehq.org/attachment.cgi?id=72396 OBS log for x86_64 Ubuntu 22.04 build failure The build succeeded in i586 but failed in x86_64 Ubuntu 22.04. Builds for all other Ubuntu versions succeeded. [ 564s] /usr/bin/x86_64-w64-mingw32-dlltool: failed to open temporary tail file: winmm_dll_t.o: No such file or directory [ 564s] tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o dlls/usp10/libusp10.cross.a --export dlls/usp10/usp10.spec [ 564s] winebuild: /usr/bin/x86_64-w64-mingw32-dlltool failed with status 1 [ 564s] make[1]: *** [Makefile:139207: dlls/winmm/libwinmm.delay.a] Error 1 [ 564s] make[1]: *** Waiting for unfinished jobs.... [ 565s] make[1]: Leaving directory '/usr/src/packages/BUILD' [ 565s] dh_auto_build: error: make -j8 returned exit code 2 -- 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.

1 2

[Bug 53023] New: MinecraftInstaller
by WineHQ Bugzilla 21 May '22

21 May '22

https://bugs.winehq.org/show_bug.cgi?id=53023 Bug ID: 53023 Summary: MinecraftInstaller Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jon9097(a)gmail.com Distribution: --- Created attachment 72394 --> https://bugs.winehq.org/attachment.cgi?id=72394 Log The Minecraft Installer doesn't work. It won't start. I'm attaching the logs. -- 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.

1 4

[Bug 52188] New: Could not load file or assembly 'Windows.Foundation.UniversalApiContract
by WineHQ Bugzilla 21 May '22

21 May '22

https://bugs.winehq.org/show_bug.cgi?id=52188 Bug ID: 52188 Summary: Could not load file or assembly 'Windows.Foundation.UniversalApiContract Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: julianhoyos94(a)gmail.com Distribution: --- hi everybody, i am creating scrpit for use xboxgamepass on linux, im very close but i have this error Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Windows.Foundation.UniversalApiContract, Version=7.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. file not found I would like to know if anyone has already experienced this problem, and if they have solved it since I looked on the internet, but I can't find the problem reported in wine. and I'm also looking for what it is, and I can't find anything about what program or what the error is based on, apparently it is part of Windows development libraries, I thought it was through .net but apparently it has nothing to do with it. -- 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.

1 4

[Bug 53011] New: Multithreaded compilation fails sometimes due to race conditions
by WineHQ Bugzilla 21 May '22

21 May '22

https://bugs.winehq.org/show_bug.cgi?id=53011 Bug ID: 53011 Summary: Multithreaded compilation fails sometimes due to race conditions Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 72380 --> https://bugs.winehq.org/attachment.cgi?id=72380 Sample of the two broken files Sometimes the compilation fails with a message like the following: /usr/bin/i686-w64-mingw32-dlltool: dlls/mfplat/libmfplat.cross.a: error reading mfplat_dll_t.o: No such file or directory /usr/bin/i686-w64-mingw32-dlltool: dlls/rpcrt4/librpcrt4.cross.a: error reading rpcrt4_dll_h.o: file truncated /usr/bin/i686-w64-mingw32-dlltool: dlls/rpcrt4/librpcrt4.delay.a: error reading rpcrt4_dll_t.o: No such file or directory /usr/bin/i686-w64-mingw32-dlltool: bfd_open failed reopen stub file: wintrust_dll_s00009.o: No such file or directory Or sometimes files are broken: /usr/lib/gcc/i686-w64-mingw32/11.2.0/../../../../i686-w64-mingw32/bin/ld: dlls/iphlpapi/libiphlpapi.delay.a: error adding symbols: file in wrong format /usr/lib/gcc/i686-w64-mingw32/11.2.0/../../../../i686-w64-mingw32/bin/ld: dlls/wintrust/libwintrust.cross.a: error adding symbols: file format not recognized If the file doesn't exist / is truncated, then trying again usually makes it work. For broken files, they need to be deleted and then you can try again. I usually compile wine like this: ALLFLAGS="-g -O0" PKG_CONFIG_PATH=/usr/lib32/pkgconfig CC="ccache gcc" CFLAGS="$ALLFLAGS" CROSSCC="ccache i686-w64-mingw32-gcc" CROSSCFLAGS="$ALLFLAGS" ../wine-git/configure --without-cups --enable-silent-rules make -j15 -sw I don't think ccache causes this, but possibly it exacerbates it.. -- 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.

1 2

[Bug 52969] New: mshtml:script fails on up-to-date Windows 8.1 machines
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52969 Bug ID: 52969 Summary: mshtml:script fails on up-to-date Windows 8.1 machines Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mshtml:script fails on up-to-date Windows 8.1 machines: script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [0] got 0.00" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [1] got 1,234.50" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [2] got -1,337.73" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [3] got -0.01" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [5] got 0.00" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [6] got 99.00" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [7] got 99.00" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: [8] got 65,536.50" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: called on string threw 2148144009" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: called on undefined threw 2148144009" script.c:644: Test failed: L"/index.html?es5.js:Number toLocaleString: called on nullDisp threw 2148144009" https://test.winehq.org/data/patterns.html#mshtml:script These failures only happen on the cw-gtx560 and cw-rx460 Windows 8.1 machines. I suspect this is because these have more recent Windows updates than the TestBot's w8 and w864 machines (see bug 52858). More specifically cw-rx460 has had more recent updates than cw-gtx560 for quite some time and I further updated both on 2022-05-02. I further plan to update the TestBot's VM (the rationale being that Windows 8.1 is old and we really only care about the latest version) which should make it easier to debug. In the meantime this does seem like a regression. commit 8aefdf48f9846e05aeef3c7ce2374401982b98b4 Author: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> Date: Tue May 3 18:17:06 2022 +0300 jscript: Implement Number.prototype.toLocaleString. Signed-off-by: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 5

[Bug 52892] New: The 64-bit ntdll:thread fails on w7pro64 and w864
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52892 Bug ID: 52892 Summary: The 64-bit ntdll:thread fails on w7pro64 and w864 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The 64-bit ntdll:thread fails on w7pro64 and w864: thread.c:153: Test failed: Multiple threads have TEB 000007FFFFFDC000. https://test.winehq.org/data/patterns.html#ntdll:thread The failure is hard to reproduce but the test was introduced by this commit: commit 6d4ec1255acceec7152ed98764ee29991ac04f10 Author: Brendan Shanks <bshanks(a)codeweavers.com> AuthorDate: Mon Apr 18 11:25:10 2022 -0700 Commit: Alexandre Julliard <julliard(a)winehq.org> CommitDate: Mon Apr 18 21:48:15 2022 +0200 ntdll/tests: Test that threads have unique TEBs. Signed-off-by: Brendan Shanks <bshanks(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Specifically the issue is with the line below: + ok( teb1 != teb2, "Multiple threads have TEB %p.\n", teb1 ); I think the issue is that there is no guarantee that the two test threads are running at the same time. I suspect that sometimes what happens is this [1]: * status = pNtCreateThreadEx( &threads[0], ... &teb1, ... ); A new TEB is allocated, the first thread starts, sets teb1 and terminates at which time its TEB is freed. * status = pNtCreateThreadEx( &threads[1], ... &teb2, ... ); A new TEB is allocated, hey there's a fresh TEB that has just bee freed! [2]. The second thread starts and sets teb2. * WaitForMultipleObjects( 2, threads, TRUE, INFINITE ); Wait for both threads. * ok( teb1 != teb2, "Multiple threads have TEB %p.\n", teb1 ); Hey, both threads used the same TEB! But did they do so at the same time? One hacky fix would be to at a small sleep in the test threads but that's introducing race conditions. A better fix would be for the main thread to tell the test threads when they can exit through some synchronization object. [1] This may be tied to how the scheduler behaves which may limit the issue to specific Windows versions. [2] And that's probably tied to how the memory allocator behaves: more memory locality or less chance of overwriting (incorrectly) still in use memory. Again this could limit the issue to some Windows versions. -- 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.

1 5

[Bug 52761] New: mscoree:mscoree test fails without a display or console
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52761 Bug ID: 52761 Summary: mscoree:mscoree test fails without a display or console Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- The mscoree:mscoree test fails if you run it like this: $ DISPLAY= wine mscoree_test.exe mscoree </dev/null >log 2>&1 Without the DISPLAY=, it makes a bunch of console windows. That doesn't seem to happen on Windows, but that could be caused by our csc.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.

1 46

[Bug 52937] New: msvcr110:msvcr110 fails on Windows with the UTF-8 codepage
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52937 Bug ID: 52937 Summary: msvcr110:msvcr110 fails on Windows with the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com msvcr110:msvcr110 fails on Windows with the UTF-8 codepage: msvcr110.c:135: Test failed: expected syr-SY, got LC_COLLATE=syr-SY;LC_CTYPE=EN-US;LC_MONETARY=syr-SY;LC_NUMERIC=syr-SY;LC_TIME=syr-SY https://test.winehq.org/data/patterns.html#msvcr110:msvcr110 Note that the LC_CTYPE value in the above string corresponds to the last value it was set to. So if one tests fr-FR right before syr-SY the string contains LC_CTYPE=fr-FR. This is also why the en-US case is weird. Furthermore with a non-UTF-8 codepage setlocale() does return "syr-SY". So it looks like: 1. msvcr110 returns a long string specifying the details of the locale settings whenever they have different values. 2. msvcr110 does not support setting LC_CTYPE to syr-SY, but only when the codepage is UTF-8 for whatever reason. -- 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.

1 4

[Bug 51298] New: d3d8:visual: lighting_test() fails on Windows 10 >= 2004
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51298 Bug ID: 51298 Summary: d3d8:visual: lighting_test() fails on Windows 10 >= 2004 Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d8:visual has a failure in lighting_test() on Windows 10 >= 2004: https://test.winehq.org/data/patterns.html#d3d8:visual visual.c:544: Test failed: Lit quad with singular world matrix has color 0x00000000. This happens on cw-rx460, cw-gtx560 and on those TestBot VMs that run the 32-bit tests. That means it's not a VM or graphics driver issue but a Windows version one. The test was introduced by this commit: commit 589f1072df9535104c074e5382ef7d8ce28f0f33 Author: Matteo Bruni <mbruni(a)codeweavers.com> AuthorDate: Tue Apr 21 15:11:19 2015 +0200 d3d8/tests: Add a lighting test with non-affine worldview matrix. -- 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.

1 4

[Bug 51104] New: mf:mf crashes on Windows + NVidia
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51104 Bug ID: 51104 Summary: mf:mf crashes on Windows + NVidia Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- mf:mf crashes on the cw-gtx560 and cw-rx460 machines but not on the TestBot VMs (except w7u-2qxl, but that's a different crash). https://test.winehq.org/data/patterns.html#mf:mf The crash happens on the same test_evr() line from Windows 8.1 to Windows 10 2009: hr = MFGetService((IUnknown *)stream_sink2, &MR_VIDEO_ACCELERATION_SERVICE, &IID_IMFVideoSampleAllocator, (void **)&allocator); A bisect shows that the commit causing the crash is not the one that added this line but the one below: commit 430c179fe86dd7f9b3ddfb6ef30f6359633ef0b8 Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Fri Oct 9 13:54:38 2020 +0300 mf/evr: Set stream media type to the mixer. Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 6

[Bug 34782] New: crypt32/chain tests crash with gcc-4.8.1 (win64)
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=34782 Bug #: 34782 Summary: crypt32/chain tests crash with gcc-4.8.1 (win64) Product: Wine Version: 1.7.4 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, source, win64 Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Classification: Unclassified Running: crypt32:chain (3 of 15) fixme:crypt:CertVerifyCertificateChainPolicy unimplemented for 0 fixme:crypt:CRYPT_CriticalExtensionsSupported unsupported critical extension "1.2.3" fixme:crypt:CRYPT_CriticalExtensionsSupported unsupported critical extension "1.2.3" fixme:crypt:CRYPT_CriticalExtensionsSupported unsupported critical extension "1.2.3" wine: Unhandled page fault at address 0x7f579f85aa74 (thread 0043), starting debugger... fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter) pEncodePara in function fixme:dbghelp_dwarf:dwarf2_parse_variable Unsupported constant (parameter) dwFlags in function fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at ctx(0x23aa10,L"kernel32<elf>"), for debug_info(abbrev:0x7b3c80,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x23aa10,L"kernel32<elf>"), for debug_info(abbrev:0x7b3c80,symt:(nil)) it works with gcc-4.7.3. I'll bisect gcc. -- 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 4

[Bug 28220] New: kernel32/process.ok: test fails when redirected
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=28220 Summary: kernel32/process.ok: test fails when redirected Product: Wine Version: 1.3.27 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com It's not uncommon to want to do make test > log 2>&1 but if you do this, kernel32/process.ok will fail with ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p kernel32_test.exe.so process.c && touch process.ok wine: cannot find L"C:\\windows\\system32\\doesnotexist.exe" wine: cannot find L"C:\\windows\\system32\\does.exe" process.c:1344: Test failed: Opening ConOut process.c:1347: Test failed: Getting sb info process.c:1348: Test failed: Getting console modes -- 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 53004] New: 63ce060 causes a white border line in winecfg
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=53004 Bug ID: 53004 Summary: 63ce060 causes a white border line in winecfg Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 63ce060e5b33ca4b58d508be11af4d3c214fae33 Distribution: --- Created attachment 72372 --> https://bugs.winehq.org/attachment.cgi?id=72372 example As the title says. -- 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.

1 5

[Bug 52970] New: kernelbase:process breaks lz32:lzexpand_main on Windows 1809+
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52970 Bug ID: 52970 Summary: kernelbase:process breaks lz32:lzexpand_main on Windows 1809+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com kernelbase:process breaks lz32:lzexpand_main on Windows 1809+: lzexpand_main.c:148: Test failed: LZOpenFileA returned 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' lzexpand_main.c:228: Test failed: LZOpenFileA succeeded on nonexistent file lzexpand_main.c:230: Test failed: GetLastError() returns 0 lzexpand_main.c:232: Test failed: LZOpenFileA set test.cBytes to 136 lzexpand_main.c:234: Test failed: LZOpenFileA set test.nErrCode to 0 lzexpand_main.c:236: Test failed: LZOpenFileA returned 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' or '¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' lzexpand_main.c:550: Test failed: LZOpenFileW returned 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' lzexpand_main.c:628: Test failed: LZOpenFileW succeeded on nonexistent file lzexpand_main.c:630: Test failed: GetLastError() returns 0 lzexpand_main.c:632: Test failed: LZOpenFileW set test.cBytes to 136 lzexpand_main.c:634: Test failed: LZOpenFileW set test.nErrCode to 0 lzexpand_main.c:636: Test failed: LZOpenFileW returned 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xxx', but was expected to return 'C:\Users\winetest\AppData\Local\Temp\wct\testfile.xx_' or '¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥¥' https://test.winehq.org/data/patterns.html#lz32:lzexpand_main As mentioned before, lz32:lzexpand_main succeeds on its own. It's only when kernelbase:process is run before that this test fails. The simplest way to reproduce the failures is to run: winetest.exe -c -o - -t foo kernelbase:process lz32:lzexpand_main The failure happens because kernelbase:process leaves a "testfile.xxx" file behind, file which is also used by the lz32:lzexpand_main test unit. Finally a bisect shows that these failures started with the commit below. commit 9c40a80100febb9ac23dae1e51605ba4f2f46f6f Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Wed May 4 14:55:36 2022 +0300 kernelbase: Implement MapViewOfFile3(). Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 7

[Bug 51376] New: Wine causes PC to lock or crash wine when loading more than 1 VST addon into WaveLab 6
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51376 Bug ID: 51376 Summary: Wine causes PC to lock or crash wine when loading more than 1 VST addon into WaveLab 6 Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 70232 --> https://bugs.winehq.org/attachment.cgi?id=70232 backtrace I have a number of VST add-ons I use with Wavelab, they come from a number of different software houses and work differently, for example some require vcrun libraries to work while others do not. In the main, I can load any single add-on and it works as expected but as soon as I add/open a second add-on my PC will either crash wine or it will lock up altogether requiring a hard restart. This was not an issue in wine 5.0. Backtrace is attached. Possibly a duplicate of bug 51259 or is quite similar. -- 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.

1 4

[Bug 51283] New: d3d8:device breaks evr:evr on w7u-2qxl
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51283 Bug ID: 51283 Summary: d3d8:device breaks evr:evr on w7u-2qxl Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com The WineTest reports show that evr:evr crashes on w7u-2qxl: https://test.winehq.org/data/patterns.html#evr:evr evr.c:1335: Test failed: Unexpected hr 0x80070057. evr.c:1335: this is the last test seen before the exception 07ac:evr: unhandled exception c0000005 at 0040CBD0 evr:evr:07ac done (-1073741819) in 0s Test failed: crash (c0000005) However when run on its own it succeeds consistently. It turns out that it is d3d8:device that causes evr:evr to crash. More specifically it is test_multi_adapter() that interferes with evr:evr. Also if d3d8:device succeeds then evr:evr crashes but if d3d8:device fails as shown below then evr:evr succeeds as can be seen by comparing the pattern below with the evr:evr one. https://test.winehq.org/data/patterns.html#d3d8:device device.c:4205: Test failed: Got a different mode. device.c:4208: Test failed: Got a different mode. -- 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.

1 4

[Bug 50462] New: Ulead Photo Explorer 8.5 Installed but failed on startup
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=50462 Bug ID: 50462 Summary: Ulead Photo Explorer 8.5 Installed but failed on startup Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wesley(a)merlin-eng.com Distribution: --- Created attachment 69087 --> https://bugs.winehq.org/attachment.cgi?id=69087 This is from the error window that came up when the program failed The program (Ulead Photo Explorer 8.5) appeared to install correctly. This program is designed to browse image files IE: .jpg. It installs with Ulead Photo Impact 10. I did not try to associate any files with either program (this should not be necessary). On startup Ulead Photo Explorer 8.5 failed, giving the attached back trace file. Photo Impact 10 installed at the same time and worked fine. -- 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.

1 8

[Bug 45959] New: Editpad Lite 7 GUI not rendered correctly
by wine-bugs＠winehq.org 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=45959 Bug ID: 45959 Summary: Editpad Lite 7 GUI not rendered correctly Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 62506 --> https://bugs.winehq.org/attachment.cgi?id=62506 Screenshot of GUI The command menu line (top line) is not rendered correctly, please see the attachment. It should display buttons with the following descriptions: File, Edit, Search, Go, Block, Extra, Convert, Options, View, Help. By mousing over and clicking and resizing the window they will eventually be rendered correctly. The installer can be downloaded at https://www.editpadlite.com/download.html Problem exists in both 32 and 64 bit prefixes and different Windows versions. My system: Kubuntu 18.04.01 -- 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 14841] New: ntdll: file.ok fails in OpenSolaris but not Linux
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=14841 Summary: ntdll: file.ok fails in OpenSolaris but not Linux Product: Wine Version: 1.1.2 Platform: PC OS/Version: Solaris Status: NEW Keywords: testcase Severity: enhancement Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=15384) --> (http://bugs.winehq.org/attachment.cgi?id=15384) +file in git, bzip2 -9'ed austin@opensolaris:~/wine-git/dlls/ntdll/tests$ make testclean ; rm -rf ~/.wine ; make file.ok rm -f atom.ok change.ok env.ok error.ok exception.ok generated.ok info.ok large_int.ok file.ok om.ok path.ok port.ok reg.ok rtl.ok rtlbitmap.ok rtlstr.ok string.ok time.ok ../../../tools/runtest -q -P wine -M ntdll.dll -T ../../.. -p ntdll_test.exe.so file.c && touch file.ok wine: created the configuration directory '/export/home/austin/.wine' err:iphlpapi:getNumWithOneHeader Unable to open '/proc/net/route' to count entries! err:iphlpapi:getRouteTable unimplemented! file.c:169: Test failed: wrong status deadbabe file.c:170: Test failed: wrong info 3735928559 file.c:194: Test failed: wrong status deadbabe file.c:195: Test failed: wrong info 3735928559 file.c:196: Test failed: read handle is signaled file.c:284: Test failed: wrong status deadbabe file.c:285: Test failed: wrong info 3735928559 file.c:286: Test failed: event is signaled make: *** [file.ok] Error 8 +file attached -- 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 11

[Bug 52874] New: win32u change prevents chromium from starting
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52874 Bug ID: 52874 Summary: win32u change prevents chromium from starting Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- The following commit breaks chromium: commit 0528f37fdd9b11cc95d074bb9e261d5127cb6ec3 Author: Jacek Caban <jacek(a)codeweavers.com> Date: Tue Apr 19 15:34:44 2022 +0200 win32u: Move NtUserFindWindowEx implementation from user32. Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> chromium just prints a few fixmes and then hangs, using one thread fully. This only affects the sandbox, --no-sandbox is a workaround. Reverting fixes the issue. Download for testing (chrome-win.zip): https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.h… Please use this version for testing, since it's the newest version not affected by bug 52845. -- 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.

1 9

[Bug 51827] New: d3dx10_34:d3dx10 crashes on all versions of Windows
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51827 Bug ID: 51827 Summary: d3dx10_34:d3dx10 crashes on all versions of Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3dx10_34:d3dx10 crashes on all versions of Windows: d3dx10.c:2377: this is the last test seen before the exception 00b8:d3dx10: unhandled exception c0000005 at 000000006C50064B https://test.winehq.org/data/patterns.html#d3dx10_34:d3dx10 The crash is random but pretty frequent and happens on AMD, NVidia and QEmu GPUs from Windows 8.1 to Windows 10. The other d3dx10_*:d3dx10 tests don't crash despite using the same source. So that means d3dx10_34 is different and the test fails to take that into account. This test was introduced by the following commit: commit a15527ff29d919b34ae1f599a5319a4b9678f4e2 Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Tue Sep 21 08:52:10 2021 +0300 d3dx10_34/tests: Enable tests. Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Matteo Bruni <mbruni(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 9

[Bug 51783] New: The ieframe:webbrowser output is too big in Wine
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51783 Bug ID: 51783 Summary: The ieframe:webbrowser output is too big in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ieframe:webbrowser outputs ~29kB of data. This is too much and contributes in pushing the WineTest reports above the 1.5MB limit. The traces break down as follows: 0kB failures 26kB todos 3kB traces 0kB test framework (summary lines, etc.) Time to fix Wine to reduce the number of todos! -- 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.

1 3

[Bug 19183] New: "make test" still fails on d3d9/tests/visual.c
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=19183 Summary: "make test" still fails on d3d9/tests/visual.c Product: Wine Version: 1.1.25 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com (This is a sequel to bug 10221; perhaps we closed that one too soon.) Running i=0 while test $i -lt 10 do ../../../tools/runtest -q -P wine -M d3d9.dll -T ../../.. -p d3d9_test.exe.so visual.c > visual-$i.log 2>&1 i=`expr $i + 1` sleep 1 done cat visual-*.log | grep "Test failed" | sort | uniq -c | sort -n produces 1 visual.c:9439: Test failed: stretchrect: Pixel 160,360 has color 0x00ff00ff, expected 0x00ff0000 1 visual.c:9441: Test failed: stretchrect: Pixel 480,360 has color 0x00ff00ff, expected 0x0000ff00 1 visual.c:9443: Test failed: stretchrect: Pixel 480,120 has color 0x00ff00ff, expected 0x000000ff 1 visual.c:9445: Test failed: stretchrect: Pixel 160,120 has color 0x00ff00ff, expected 0x00000000 2 visual.c:8978: Test failed: Offscreen failed for D3DFMT_A32B32G32R32F: expected no color blending but received it anyway. 3 visual.c:6883: Test failed: SRCALPHA on texture returned color 00000000, expected 0x00bf4000 3 visual.c:6887: Test failed: DSTALPHA on texture returned color 00000000, expected 0x000000ff 3 visual.c:8978: Test failed: Offscreen failed for D3DFMT_G32R32F: expected no color blending but received it anyway. 3 visual.c:8978: Test failed: Offscreen failed for D3DFMT_R32F: expected no color blending but received it anyway. 4 visual.c:8969: Test failed: Offscreen failed for D3DFMT_A16B16G16R16F: Got color 00000000, expected 0x181800. 4 visual.c:8978: Test failed: Offscreen failed for D3DFMT_G16R16F: expected no color blending but received it anyway. 5 visual.c:8326: Test failed: Pixel 14/18 has color 0x00000000, expected 0x0000ff00 5 visual.c:8329: Test failed: Pixel 18/14 has color 0x00000000, expected 0x000000ff 5 visual.c:8332: Test failed: Pixel 18/18 has color 0x00000000, expected 0x0000ffff 5 visual.c:8978: Test failed: Offscreen failed for D3DFMT_R16F: expected no color blending but received it anyway. 5 visual.c:9439: Test failed: stretchrect: Pixel 160,360 has color 0x00000000, expected 0x00ff0000 5 visual.c:9441: Test failed: stretchrect: Pixel 480,360 has color 0x00000000, expected 0x0000ff00 5 visual.c:9443: Test failed: stretchrect: Pixel 480,120 has color 0x00000000, expected 0x000000ff 7 visual.c:8800: Test failed: Texture 1(output color 1) has color 0x00000000, expected 0x0000ff00 7 visual.c:8802: Test failed: Texture 2(output color 2) has color 0x00000000, expected 0x000000ff lspci | grep -i vga says 00:10.0 VGA compatible controller: nVidia Corporation GeForce 7100/nForce 630i (rev a2) and this is on Jaunty x86-64 with the proprietary nvidia 180 driver. I'll attach the output of glxinfo. -- 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 13

[Bug 53015] New: winscp bookmark adding error
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=53015 Bug ID: 53015 Summary: winscp bookmark adding error Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gonghuiii(a)gmail.com Distribution: --- Created attachment 72382 --> https://bugs.winehq.org/attachment.cgi?id=72382 error message and then exit When using WinSCP to add a bookmark, it gives me errors when adding without checking the 'add to shared bookmark' option. -- 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.

1 7

[Bug 52914] New: mf:mf - The 64-bit test_h264_decoder() fails on 64-bit Debian 11 + Intel GPU
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52914 Bug ID: 52914 Summary: mf:mf - The 64-bit test_h264_decoder() fails on 64-bit Debian 11 + Intel GPU Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit test_h264_decoder() fails on my Debian 11 + Intel GPU machine (see fg-deb64-wow64): mf.c:6780: Test failed: SetOutputType returned 0x80004005. mf.c:6782: Test failed: Release returned 0 mf.c:6799: Test failed: got cbSize 0x3fc000 mf.c:6825: Test failed: ProcessOutput returned 0xc00d6d60 https://test.winehq.org/data/patterns.html#mf:mf configure does not mention any missing library (besides libhal) in either the 32- or the 64-bit builds. A bisect shows that the failures started with the commit below: commit 606505e5643d8df2a23a2cc074fa9b6b2ae8b05f Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Mar 28 17:35:45 2022 +0200 winegstreamer: Try creating a wg_transform in the H264 decoder. Adding H264 format support in wg_format. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45988 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=47084 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=49715 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52183 Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 4

[Bug 52821] New: Missing support of C++20 Semaphores in built-in Wine C++ runtime
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52821 Bug ID: 52821 Summary: Missing support of C++20 Semaphores in built-in Wine C++ runtime Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: kle(a)bluewin.ch Distribution: --- Hi all Right at the beginning it should be noted that the following error may have been already described. There seems to exist currently no support of C++20 Semaphores in Wines built-in C++ library. I noticed this limitation with two applications. The following "msvcp140_atomic_wait.dll" related error message is shown when this issue occurs. Both apps crash right after. CXBX-R Xbox emulator (starting with build 374ba5e): wine: Call from 7B011586 to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_wait_direct, aborting wine: Call from 7B011586 to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_notify_one_direct, aborting PCSX-Redux PSX emulator (all newer builds since 4317): wine: Call from 0000000000272B9E to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_wait_direct, aborting wine: Unimplemented function msvcp140_atomic_wait.dll.__std_atomic_wait_direct called at address 0000000000272B9E (thread 010c), starting debugger... wine: Call from 0000000000272B9E to unimplemented function msvcp140_atomic_wait.dll.__std_atomic_notify_one_direct, aborting Both applications worked before the "std::binary_semaphore" C++20 type was introduced. It is confirmed for Wine 7.0 that it can handle this situation when vcrun2019 (native MS Visual C++ 2019) is installed via winetricks. But for whatever reason this stopped to work in later Wine 7.x devel versions. A further workaround was to put a native "msvcp140_atomic_wait.dll" into the program folder. I can confirm that this helped at least for a while in conjunction with the PCSX-Redux emulator. But also here this tweak stopped to work in later Wine 7.x devel versions. More information can be found at the CXBX-R GitHub issue page: https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/issues/2347 -- 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.

1 11

[Bug 52751] New: `winetricks nocrashdialog` no longer works properly with Wine 7.5(but works with 7.4)
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52751 Bug ID: 52751 Summary: `winetricks nocrashdialog` no longer works properly with Wine 7.5(but works with 7.4) Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- In Wine 7.4 I disabled crash dialog by `winetricks nocrashdialog` command and when app crashed, then silently it just exit. In Wine 7.5 I see that now is visible console window which exit after while Screenshoot of this window https://user-images.githubusercontent.com/41945903/160272294-dd272f8b-710d-… Steps to reproduce: - Download https://github.com/qarmin/Win32Fuzzer/releases/download/1.1.0/reproducer_64 (require at least Ubuntu 21.10 or similar) - Download https://github.com/qarmin/Win32Fuzzer/releases/download/1.1.0/win_project_6… - Run command `./reproducer win_project_64.exe linux` For now I'm unable to found exact commit with regression, due problem with compilation of Wine. Related winetricks issue - https://github.com/Winetricks/winetricks/issues/1897 -- 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.

1 4

[Bug 51680] New: nsi:nsi test_ip_neighbour() fails on unreachable link local entry
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51680 Bug ID: 51680 Summary: nsi:nsi test_ip_neighbour() fails on unreachable link local entry Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com nsi:nsi has a failure on cw-rx460 from Windows 1709 to 21H1: nsi.c:680: Test failed: AF_INET: 0 vs 1 https://test.winehq.org/data/patterns.html#nsi:nsi The failing test has been introduced by the commit below and failed from the start: commit c09c65f65c188a1870d279ca793c5ad1fc15440d Author: Huw Davies <huw(a)codeweavers.com> AuthorDate: Tue Aug 10 09:20:47 2021 +0100 nsiproxy: Implement IPv4 neighbour enumerate_all. Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Adding some traces shows that the failure happens on a link local entry: AF_INET: 5 InterfaceIndex=10 state=0/0 s_addr=169.254.169.254 I have not identified the corresponding network interface. Also, given that cw-rx460 ad cw-gtx560 are very similar I would expect both to have this issue and I don't know why that's not the case. However what is interesting is that in both cases the state is NlnsUnreachable so I suspect the is_unreachable / IsUnreachable flags are not necessarily meaningful. -- 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.

1 8

[Bug 51612] New: Stellaris launcher (Paradox) does not launch
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51612 Bug ID: 51612 Summary: Stellaris launcher (Paradox) does not launch Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- The game Stellaris installs and works using the stellaris.exe file but the launcher (dowser.exe) fails to launch. I am using Kubuntu 21.04 and this is a fresh installation as it does work on a 2nd PC I have, also Kubuntu 21.04. The only difference of note between the machines is this machine has an AMD 5800X CPU. The terminal returns (duplicated lines removed): scott@scottubuntu:~/.winestella1/drive_c/GOG Games/Stellaris$ WINEPREFIX=~/.winestella1 wine dowser.exe 002c:fixme:winediag:LdrInitializeThunk wine-staging 6.15 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0034:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 006c:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 006c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 007c:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 007c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0090:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0090:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 002c:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 00f8:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 00f8:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0024:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0024:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0100:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0100:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0100:fixme:process:SetProcessPriorityBoost (FFFFFFFFFFFFFFFF,1): stub 0118:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0118:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0120:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0120:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. 0128:fixme:font:get_name_record_codepage encoding 29 not handled, platform 1. 0128:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1. scott@scottubuntu:~/.winestella1/drive_c/GOG Games/Stellaris$ wine: Unhandled page fault on write access to 0000000000000000 at address 00007F756DC2CF91 (thread 0070), starting debugger... 0070:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 96 72" (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger I attach the output of this system request. -- 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.

1 3

[Bug 28508] New: user32/monitor.ok fails rarely?
by wine-bugs＠winehq.org 20 May '22

20 May '22

http://bugs.winehq.org/show_bug.cgi?id=28508 Bug #: 28508 Summary: user32/monitor.ok fails rarely? Product: Wine Version: 1.3.29 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified Saw this once in a month of runs: ../../../tools/runtest -q -P wine -M user32.dll -T ../../.. -p user32_test.exe.so monitor.c && touch monitor.ok fixme:win:EnumDisplayDevicesW ((null),0,0x22f4d0,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),1,0x22f4d0,0x00000000), stub! monitor.c:269: Test failed: Invalid clip rect: (0 0) x (800 600) err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 0x480x0 @0! (desktop) err:x11settings:X11DRV_ChangeDisplaySettingsEx No matching mode found 640x0x0 @0! (desktop) The tests were run in a virtual desktop on os: Ubuntu 11.04, 2.6.38-11-generic, pulseaudio 0.9.22-24-g67d18, Advanced Linux Sound Architecture Driver Version 1.0.23. ram: 3963 MB cpu: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz gpu: GeForce 8500 GT/PCI/SSE2 3.3.0 NVIDIA 270.41.06 -- 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 52961] New: crypt32:str - test_CertGetNameString() fails on Windows 7
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52961 Bug ID: 52961 Summary: crypt32:str - test_CertGetNameString() fails on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com crypt32:str - test_CertGetNameString() fails on Windows 7: str.c:867: Test failed: line 951: unexpected length 10, expected 11. str.c:871: Test failed: line 951: unexpected value "localhost\x00e". str.c:885: Test failed: line 951: unexpected len 10, expected 11. str.c:894: Test failed: line 951: string is not zero terminated. str.c:867: Test failed: line 952: unexpected length 21, expected 1. str.c:871: Test failed: line 952: unexpected value "a". str.c:877: Test failed: line 952: unexpected str[1] 0x72. str.c:878: Test failed: line 952: str "ric(a)codeweavers.com", string data mismatch. str.c:885: Test failed: line 952: unexpected len 21, expected 1. str.c:886: Test failed: line 952: unexpected value L"aric(a)codeweavers.com\0000". str.c:892: Test failed: line 952: str L"aric(a)codeweavers.c", string data mismatch. str.c:894: Test failed: line 952: string is not zero terminated. str.c:867: Test failed: line 953: unexpected length 10, expected 1. str.c:871: Test failed: line 953: unexpected value "l". str.c:877: Test failed: line 953: unexpected str[1] 0x6f. str.c:878: Test failed: line 953: str "ocalhost", string data mismatch. str.c:885: Test failed: line 953: unexpected len 10, expected 1. str.c:886: Test failed: line 953: unexpected value L"localhost\0000". str.c:892: Test failed: line 953: str L"localho", string data mismatch. str.c:894: Test failed: line 953: string is not zero terminated. str.c:867: Test failed: line 976: unexpected length 8, expected 19. str.c:871: Test failed: line 976: unexpected value "ex1.org\x00n.org\x00rs.co". str.c:885: Test failed: line 976: unexpected len 8, expected 19. str.c:894: Test failed: line 976: string is not zero terminated. str.c:867: Test failed: line 978: unexpected length 8, expected 19. str.c:871: Test failed: line 978: unexpected value "ex3.org\x00n.org\x00rs.co". str.c:885: Test failed: line 978: unexpected len 8, expected 19. str.c:894: Test failed: line 978: string is not zero terminated. https://test.winehq.org/data/patterns.html#crypt32:str A bisect shows that the failures started with the commit below: commit 0c35a851cd73247cb95187acc2e22074f9ca09a3 Author: Paul Gofman <pgofman(a)codeweavers.com> Date: Fri Apr 15 14:44:32 2022 +0300 crypt32: Support CERT_NAME_SEARCH_ALL_NAMES_FLAG in CertGetNameStringW(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 6

[Bug 52908] New: mf:mf - The 64-bit test_wma_decoder() fails on 64-bit Debian 11 + Intel
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=52908 Bug ID: 52908 Summary: mf:mf - The 64-bit test_wma_decoder() fails on 64-bit Debian 11 + Intel Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit test_wma_decoder() fails on my Debian 11 + Intel machine (see fg-deb64-wow64): mf.c:6282: Test failed: ProcessOutput returned 0xd0000001 mf.c:6328: Test failed: ProcessOutput returned 0xd0000001 mf.c:6340: Test failed: ProcessOutput returned 0xd0000001 mf.c:6352: Test failed: ProcessInput returned 0xc00d36b5 https://test.winehq.org/data/patterns.html#mf:mf The last two failures are gone now but the first two are still present. configure does not mention any missing library (besides libhal) in either the 32- or the 64-bit builds. A bisect shows that the failures started with this commit: commit 651e4002ceeb9a15b11a184b5f47a732e26b7e00 Author: Rémi Bernon <rbernon(a)codeweavers.com> AuthorDate: Mon Mar 14 14:43:22 2022 +0100 winegstreamer: Introduce new wg_transform_(push|read)_data functions. And use it to implement WMA decoder Process(Input|Output). The test output is different because ffmpeg WMA decoder outputs data in a different way as native. The data seems valid audio nonetheless, and it shouldn't matter too much. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51931 Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52391 Signed-off-by: Rémi Bernon <rbernon(a)codeweavers.com> Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 10

[Bug 51297] New: d3d8:visual: test_sample_mask() fails on Nvidia (cw-gtx560)
by WineHQ Bugzilla 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=51297 Bug ID: 51297 Summary: d3d8:visual: test_sample_mask() fails on Nvidia (cw-gtx560) Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d8:visual has a failure in test_sample_mask() on cw-gtx560 (Nvidia): https://test.winehq.org/data/patterns.html#d3d8:visual visual.c:11146: Test failed: Got unexpected colour ffffbcbc. This happens on all Windows versions available on that machine (from Windows 8.1 to Windows 10 2009). This failure also does not happen on any other machine which makes it specific to Nvidia or this graphics card or this driver version (391.35, the latest available at this date). The test was introduced by this commit: commit 30fe080965409e68cc86a04af1935e4944f4b049 Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Fri Apr 30 11:08:26 2021 -0500 d3d8/tests: Port test_sample_mask() from d3d9. Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 6

[Bug 45960] New: Editpad Lite 7 siaplay empty boxes instead of text in some menus
by wine-bugs＠winehq.org 20 May '22

20 May '22

https://bugs.winehq.org/show_bug.cgi?id=45960 Bug ID: 45960 Summary: Editpad Lite 7 siaplay empty boxes instead of text in some menus Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 62507 --> https://bugs.winehq.org/attachment.cgi?id=62507 screenshot of problem When trying to set the default font, the drop-down screen offers many selections of empty boxes rather than text, see the attachment. This screen is accessed by: 1/ Options>Configure File Type 2/ On the Editor Options tab click the Edit button next to the "Default text layout" drop-down box 3/ in the Text Layout Configuration Window click the down arrow to the right of of the large drop down box to select fonts in the 2nd-from-last left hand window pane called Main Font. The installer is here: https://www.editpadlite.com/download.html This may be the same issue as bug 45959 which I also submitted, I do not have sufficient knowledge to make that judgement. My system: Kubuntu 18.04.01 Wine version 3.17 -- 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 51755] New: Crash in DeepSkyStacker when stacking images.
by WineHQ Bugzilla 19 May '22

19 May '22

https://bugs.winehq.org/show_bug.cgi?id=51755 Bug ID: 51755 Summary: Crash in DeepSkyStacker when stacking images. Product: Wine Version: 6.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dawid.krol(a)gmail.com Distribution: --- Created attachment 70650 --> https://bugs.winehq.org/attachment.cgi?id=70650 crash log When astrophotography images are processed the program crashes. I looked in the wine log but i didn't noticed anythinh suspicous. The program on Windows is working properly. The program requres GDI+ and I installed but it didn't helped. The problem was reported in Wine's AppDB. Steps to reproduce crash 1. Open Deep Sky Stacker 2. Click Open picture files and select DSC_6524.NEF 3. Select dark files and select DSC_6525.NEF 4. Select bias files and select DSC_6538.NEF 5. Click Stack checked pictures 6. Click OK in the popup. Application is crashing when processing dialog is shown. Files for crash reproduction are in these links. https://www.dropbox.com/s/7lv7encmhwvmn7d/DSC_6524.NEF?dl=0 https://www.dropbox.com/s/17q40uq17d8ar7k/DSC_6525.NEF?dl=0 https://www.dropbox.com/s/o9mn1wd3l4kv1sx/DSC_6538.NEF?dl=0 -- 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.

1 2

[Bug 44503] New: Failed install of Corel PSP X6
by wine-bugs＠winehq.org 19 May '22

19 May '22

https://bugs.winehq.org/show_bug.cgi?id=44503 Bug ID: 44503 Summary: Failed install of Corel PSP X6 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: neil.ray(a)usa.com Distribution: --- Created attachment 60460 --> https://bugs.winehq.org/attachment.cgi?id=60460 Failed install of Corel PSP X6 Attempted to install, via wine, Corel Paint Shop Pro X6. Encountered a fatal error and was unable to continue. Backtrace log attached. My OS is Linux Mint 18.3 on a 32bit machine. -- 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 52938] New: Nitro Family
by WineHQ Bugzilla 15 May '22

15 May '22

https://bugs.winehq.org/show_bug.cgi?id=52938 Bug ID: 52938 Summary: Nitro Family Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jon9097(a)gmail.com Distribution: --- Created attachment 72311 --> https://bugs.winehq.org/attachment.cgi?id=72311 Log In the game Nitro Family when you start just a black screen and game sounds. I can hear the cursor moving in the menu, but you can only see a black screen. The problem has been lingering since 2015, and it's about time it was solved. Surely fixing the bug will make it possible to run quite a few games! -- 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.

1 7

[Bug 52416] New: Metatogger 7.2: Wine crashes upon launching the software
by WineHQ Bugzilla 15 May '22

15 May '22

https://bugs.winehq.org/show_bug.cgi?id=52416 Bug ID: 52416 Summary: Metatogger 7.2: Wine crashes upon launching the software Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: p10qjuhh(a)duck.com Distribution: --- Created attachment 71672 --> https://bugs.winehq.org/attachment.cgi?id=71672 The backtrace generated by Wine Launching Metatogger at all causes a crash. Download: https://www.luminescence-software.org/download/metatogger/Metatogger-Instal… Name: Metatogger-Installer.exe MD5: 4fc5a6f1c39a95bb754c25207fe2bb9a (This installer is updated semi-regularly by the software maintainer, so determining the version is on you) At the time of writing, 7.2 is the latest release, but this problem is likely to still exist in later versions. -- 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.

1 7

[Bug 52407] New: dotnet-sdk-5.0.100-win-x64 simple example fails: error MSB4018: The "AssignCulture" task failed unexpectedly.
by WineHQ Bugzilla 15 May '22

15 May '22

https://bugs.winehq.org/show_bug.cgi?id=52407 Bug ID: 52407 Summary: dotnet-sdk-5.0.100-win-x64 simple example fails: error MSB4018: The "AssignCulture" task failed unexpectedly. Product: Wine Version: 7.0-rc6 Hardware: x86-64 URL: https://download.visualstudio.microsoft.com/download/p r/2892493e-df43-409e-af68-8b14aa75c029/53156c889fc08f0 1b7ed8d7135badede/dotnet-sdk-5.0.100-win-x64.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Note: this happens on version 5.0.100 of the downloadlink, another tested version like dotnet-sdk-5.0.100-rc.2.20479.15-win-x64.exe doesn`t show this, guess something has changed in the code (?) Steps: wget https://download.visualstudio.microsoft.com/download/pr/2892493e-df43-409e-… wine dotnet-sdk-5.0.100-win-x64.exe wine dotnet new wpf -o myapp && cd myapp && wine dotnet run Output: 027c:fixme:nls:ResolveLocaleName stub: L"eo", 0000000028CCC000, 85 C:\Program Files\dotnet\sdk\5.0.100\Microsoft.Common.CurrentVersion.targets(2943,5): error MSB4018: The "AssignCulture" task f ailed unexpectedly. [Z:\home\louis\ramdisk\myapp\myapp.csproj] C:\Program Files\dotnet\sdk\5.0.100\Microsoft.Common.CurrentVersion.targets(2943,5): error MSB4018: System.TypeInitializationE xception: The type initializer for 'Microsoft.Build.Tasks.CultureInfoCache' threw an exception. [Z:\home\louis\ramdisk\myapp\m yapp.csproj] I did a bit of testing and in fact ResolveLocaleName _never_ returns 0, so i guess we could just improve stub a bit to return 1 and get away with it. I`ll attach improved stub that fixes the bug -- 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.

1 8

[Bug 52940] New: [Regression]Assassin's Creed Origins crashes after intro videos with vulkan backend on wine-git
by WineHQ Bugzilla 15 May '22

15 May '22

https://bugs.winehq.org/show_bug.cgi?id=52940 Bug ID: 52940 Summary: [Regression]Assassin's Creed Origins crashes after intro videos with vulkan backend on wine-git Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: e7d86d9c6e58e8e133c606099615b0d9e7940132 Distribution: Debian Hi, When you launch the game from UbisoftConnect, there are 3 intro video (Epilepsy.bk2, pc_warningSaving.bk2 and warning_disclaimer.bk2) and then a splash-screen (screenshot : https://ibb.co/fSC33zX) to access to the main menu. This screenshot has been taken with DXVK, the game has an issue with wined3d opengl/vulkan backend with with wine <= 7.7 (see bug #45358) (https://bugs.winehq.org/attachment.cgi?id=72313) With wine-git the game crashes after the 3 intro video when the splash-screen must appears. I did a regression test and the 1st bad commit is : ###### e7d86d9c6e58e8e133c606099615b0d9e7940132 is the first bad commit commit e7d86d9c6e58e8e133c606099615b0d9e7940132 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Fri Apr 22 15:42:56 2022 -0500 wined3d: Clear Vulkan textures on the GPU in wined3d_texture_vk_load_texture(). Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/wined3d/texture.c | 61 ++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 52 insertions(+), 9 deletions(-) ###### After to revert it, i confirm that the broken splash-screen appears. VKD3D_DEBUG=trace VKD3D_SHADER_DEBUG=trace WINEDEBUG=+d3d,+d3d11,+d3d_shader,+seh log here : https://www.mediafire.com/file/n8gnbe5949mr4rs/AC_Origins_d3d_wine_git.7z/f… -- 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.

1 3

[Bug 52827] New: .NET 6 / .NET6 Application "Reloaded II" Fails to Run
by WineHQ Bugzilla 14 May '22

14 May '22

https://bugs.winehq.org/show_bug.cgi?id=52827 Bug ID: 52827 Summary: .NET 6 / .NET6 Application "Reloaded II" Fails to Run Product: Wine Version: 7.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nekoNexus(a)protonmail.ch Distribution: --- Created attachment 72215 --> https://bugs.winehq.org/attachment.cgi?id=72215 Reloaded-II Vanilla Wine 7.6 Log SHA256 Checksum of Setup.exe: 9f2c200d9049aa2a7729f17b2628f8ff152d10b5d6efbebee4c642b6a37a08db Program version: 1.17.5 Open-source on Github; web archive download link: https://web.archive.org/web/20220416193511/https://objects.githubuserconten… Supposedly requires both .NET 6.x.x runtime x86 and x64 bits ----- Installing the .NET 6 runtime prerequisites and attempting run the application doesn't enable the application to run; it crashes on launch with various errors, one of which mentioning XAML. This application not working also prevents several other applications (namely mod tools) from working as well. (The ones that currently come to mind are Persona 4 Golden PC modding tools.) -- 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.

1 14

[Bug 28126] New: Big Race USA Demo: menu animations and music too fast
by wine-bugs＠winehq.org 14 May '22

14 May '22

http://bugs.winehq.org/show_bug.cgi?id=28126 Summary: Big Race USA Demo: menu animations and music too fast Product: Wine Version: 1.3.26 Platform: x86-64 URL: http://games.softpedia.com/get/Games-Demo/Pro-Pinball- Big-Race-USA-Demo.shtml OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: asb(a)asbradbury.org Created an attachment (id=36038) --> (http://bugs.winehq.org/attachment.cgi?id=36038) bigraceusademo.exe on wine 1.3.26 (no debug channels) In the Big Race USA Demo (or the full Big Race USA game as sold by gog.com), the menu animations (blinking of text and spinning of icons) move far too fast. Additionally, the game music and sound effects are incredibly fast and 'crackly'. I mention both issues as it seems likely they have the same root cause. My CPU is an i5-750 at 2.67Ghz (presumably this problem may not occur on something much slower like an Atom). Workaround: Use cpulimit on the bigraceusademo.exe process. Turning on a noisy enough debug channel will also slow the process down enough that the sound problem will go away. To reproduce, just install the linked demo, run bigraceusademo.exe and observe the rapidly spinning menu items and corrupted audio output. $ sha1sum bigrace.zip fd5cbfc5da9dd29a010cb02a1f847a753a65c2b2 bigrace.zip The demo and full game both work perfectly in Win 7 x64 on the same hardware. I tested in wine 1.0.1, 1.2.3, 1.3.26 and some versions in between. The problem was less pronounced in 1.0.1 (likely due to worse overall performance). I'll attach the output from 1.3.26, though the only relevant line appears to be the following, which seems to be a likely culprit for the problem: fixme:ddraw:ddraw7_WaitForVerticalBlank iface 0x1557b0, flags 0x1, event (nil) stub! -- 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 11

[Bug 47229] New: gog.com - The Void: crashes when entering two game locations
by wine-bugs＠winehq.org 14 May '22

14 May '22

https://bugs.winehq.org/show_bug.cgi?id=47229 Bug ID: 47229 Summary: gog.com - The Void: crashes when entering two game locations Product: Wine Version: 4.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dron2065(a)rambler.ru Distribution: --- Created attachment 64501 --> https://bugs.winehq.org/attachment.cgi?id=64501 Output log of wine before crashing Video game The Void (GOG edittion) crashes with "Unhandled page fault on read access to 0x00000000 at address 0x1953eb7" in the same locations every time. It's make finish game impossible. There are at least two problem places at game. See more in attachment log. -- 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 29

[Bug 47720] New: eac3to performance issues
by wine-bugs＠winehq.org 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=47720 Bug ID: 47720 Summary: eac3to performance issues Product: Wine Version: 4.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 65192 --> https://bugs.winehq.org/attachment.cgi?id=65192 wine version eac3to used to work well a year ago but now has a few issues which need to be addressed not least of which is it takes 4 times longer to demux than it does when run under windows. Also the lossless check seems not to be done and certainly is not reported. A number of warnings which are generated apparently needlessly. I have attached screen shots from under wine and under windows which will show clearly the issues. -- 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 51312] New: dxgi:dxgi: Wrong screen mode order on AMD GPUs (cw-rx460)
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=51312 Bug ID: 51312 Summary: dxgi:dxgi: Wrong screen mode order on AMD GPUs (cw-rx460) Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dxgi:dxgi gets failures of the form: https://test.winehq.org/data/patterns.html#dxgi:dxgi dxgi.c:1460: Test failed: Mode 3: Modes should have been sorted, refresh rate 59.940060 < 85.000000. dxgi.c:1460: Test failed: Mode 22: Modes should have been sorted, refresh rate 59.940060 < 85.000000. dxgi.c:1460: Test failed: Mode 55: Modes should have been sorted, refresh rate 59.940060 < 75.000000. * These failures happen on all available Windows versions (8.1 to 10 2009). * They also happen regardless of the Radeon driver version: 19.11.3 to 21.4.1. * They don't happen on machines with any other GPU (cw-gtx560 and QEmu VMs). * They also happen systematically so are not probably caused by a threading issue. * So this really looks like a Radeon-specific behavior. The failing test was introduced by the following commit: commit eb2028fa90c41d3b7b8b4f924cd86059c5ba1e0d Author: Andrew Eikum <aeikum(a)codeweavers.com> AuthorDate: Mon Oct 28 16:59:18 2019 +0330 dxgi: Sort reported output modes. Sekiro: Shadows Die Twice depends on this for its mode switching. Signed-off-by: Andrew Eikum <aeikum(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Does the application crash on Windows machines with an AMD GPU? Or does the Radeon driver return the wrong order only on some GPUs? If the application does not crash maybe our order specification is a bit too strict? Given that an application depends on this we probably want Wine to respect the ordering. Just add a broken()? -- 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.

1 7

[Bug 52996] New: comdlg32:printdlg fails when OneNote is installed
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=52996 Bug ID: 52996 Summary: comdlg32:printdlg fails when OneNote is installed Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comdlg32:printdlg fails on cw-gtx560 and cw-rx460 when running Windows 1809 and 1909: printdlg.c:198: driver 'winspool' device 'OneNote' port 'Microsoft.Office.OneNote_16001.11629.20028.0_x64__8wekyb3d8bbwe_microsoft.onenoteim_S-1-5-21-2735375161-1667520140-535807745-1002' printdlg.c:215: Test failed: got 0 with 2 and 00000000 for '' (expected '>1' and '!= NULL') printdlg.c:220: Test failed: got driver 'winspool' (expected '') https://test.winehq.org/data/tests/comdlg32:printdlg.html It turns out these test configurations are the only ones that have this 'OneNote' line. All the others have the following trace instead: printdlg.c:198: driver 'winspool' device 'Microsoft Print to PDF' port 'PORTPROMPT:' So my understanding is that 'Microsoft Print to PDF' is the default printer for all the machines except for these four where "OneNote" is the default instead. I don't know how "OneNote" came to be the default on these machines. I don't think it was intentional on my part. Rather I suspect there was some randomness in the order in which some Windows updates were installed or something like that. For reference the cw-rx460-1909 machine has the following printers: * Fax * Microsoft Print to PDF --> This seems to be the default printer on all other machines. * Microsoft XPS Document Writer * OneNote --> This is the one that's selected by default in notepad, so presumably the default printer. (The Windows 10 1909 GUI does not make that really clear anywhere else that I could find) So it seems like the test should be adjusted to not fail with the OneNote printer. That or that check should be skipped? -- 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.

1 1

[Bug 50368] New: DragonAge Origins Launcher doesn't toggle music status
by WineHQ Bugzilla 13 May '22

13 May '22

https://bugs.winehq.org/show_bug.cgi?id=50368 Bug ID: 50368 Summary: DragonAge Origins Launcher doesn't toggle music status Product: Wine Version: 6.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Distribution: ArchLinux Until recently the Dragon Age Origins Launcher didn't work at all becouse bug #44185 that was recently fixed. However now, the laucnehr start, it play correctly the music but the toggle button to disable/enable the music doesn't work. This is the flow of what seems the issue: 0164:trace:mci:mciSendStringW (L"pause all", 0074EE48, 100, 00000000) 0164:trace:mci:mciSendStringW verb=L"pause" on dev=L"all"; offset=4 0164:trace:mci:mciSendStringW [-1, MCI_PAUSE, 00000000, 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000] 0164:fixme:mci:MCI_SendCommand unhandled MCI_ALL_DEVICE_ID 0164:trace:mci:mciSendStringW => 117 wine isn't handling correctly the MCI_ALL_DEVICE_ID case in cases others then closing the device. This affect just the launcher (the game should work properly if not regressed recently, still didn't try) so low priority, but other programs may be affected. -- 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.

1 1

[Bug 52990] New: MFMEv20 Emulator needs user32.RegisterTouchWindow implementation
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=52990 Bug ID: 52990 Summary: MFMEv20 Emulator needs user32.RegisterTouchWindow implementation Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian With wine-7.8, the application pops up an error dialog on start: RegisterTouchWindow Failed. If the function is hacked to return TRUE instead of FALSE, the application then starts fine. -- 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.

1 1

[Bug 51217] New: RtlWow64IsWowGuestMachineSupported() check fails on w1064v1607 for the 32-bit ntdll:info
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=51217 Bug ID: 51217 Summary: RtlWow64IsWowGuestMachineSupported() check fails on w1064v1607 for the 32-bit ntdll:info Product: Wine Version: 6.8 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:info has a failure on w1064v1607 (Windows 10 64-bit version 1607 running the 32-bit tests): https://test.winehq.org/data/patterns.html#ntdll:info info.c:3024: Test failed: wrong result 0 This is a check of the RtlWow64IsWowGuestMachineSupported() result. The commit that introduced this check is: commit 4f8ede8e7665328a2a3ccd303875e239bf443512 Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Thu Apr 29 17:15:15 2021 +0200 ntdll: Implement RtlWow64IsWowGuestMachineSupported(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 4

[Bug 51078] New: mshtml:events hangs on Windows 10 1709
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=51078 Bug ID: 51078 Summary: mshtml:events hangs on Windows 10 1709 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 69941 --> https://bugs.winehq.org/attachment.cgi?id=69941 Patch to more reliably reproduce the hang mshtml:events sometimes hangs on Windows 10 1709: http://winetest.dolphin/data/patterns.html#mshtml:events For some reason this only happens on Windows 1709 (the reports say this is mshtml 11.0.16299.309). The test proceeds all the way to the end but then does not exit because the mshtml component still has threads running: VSyncHelper Internet Explorer_Hidden MSCTFIME UI Commenting out the test_focus() run gets rid of the hangs. Also running the test with WINETEST_INTERACTIVE=1 greatly increases the probability of getting a hang. I attached a patch that does that and can be used to reproduce the hang on the TestBot's w1064v1709 VM. So this is clearly related to focus. -- 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.

1 2

[Bug 52988] New: comctl32:monthcal fails on Windows in Korean because of unexpected IME messages
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=52988 Bug ID: 52988 Summary: comctl32:monthcal fails on Windows in Korean because of unexpected IME messages Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:monthcal fails on Windows in Korean because of unexpected IME messages: monthcal.c:631: Test failed: create parent window: the msg 0x0007 was expected, but got msg 0x0282 instead monthcal.c:631: Test failed: create parent window: the msg 0x0047 was expected, but got msg 0x0024 instead monthcal.c:631: Test failed: create parent window: the msg 0x0005 was expected, but got msg 0x0282 instead monthcal.c:631: Test failed: create parent window: the msg 0x0003 was expected, but got msg 0x0281 instead monthcal.c:631: Test failed: create parent window: the msg sequence is not complete: expected 0000 - actual 0282 monthcal.c:631: Failed sequence create parent window: monthcal.c:631: 0: expected: 0024 - actual: 0024 wp 00000000 lp 0072f630 monthcal.c:631: 1: expected: 0081 - actual: 0081 wp 00000000 lp 0072f5e0 monthcal.c:631: 2: expected: 0083 - actual: 0083 wp 00000000 lp 0072f650 monthcal.c:631: 3: expected: 0001 - actual: 0001 wp 00000000 lp 0072f590 monthcal.c:631: 4: expected: 0018 - actual: 0018 wp 00000001 lp 00000000 monthcal.c:631: 5: expected: 0046 - actual: 0046 wp 00000000 lp 0072f630 monthcal.c:631: 6: expected: 030f - actual: 0046 wp 00000000 lp 0072f630 monthcal.c:631: 7: expected: 0046 - actual: 001c wp 00000001 lp 0000095c monthcal.c:631: 8: expected: 0047 - actual: 0086 wp 00000001 lp 00000000 monthcal.c:631: 9: expected: 001c - actual: 0006 wp 00000001 lp 00000000 monthcal.c:631: 10: expected: 0086 - actual: 0282 wp 00000006 lp 00000000 monthcal.c:631: 11: expected: 0006 - actual: 0282 wp 00000006 lp 00000000 monthcal.c:631: 12: expected: 0281 - actual: 0024 wp 00000000 lp 0072d650 monthcal.c:631: 13: expected: 0282 - actual: 0282 wp 00000006 lp 00000000 monthcal.c:631: 14: expected: 0007 - actual: 0281 wp 00000001 lp c000000f monthcal.c:631: 15: expected: 0047 - actual: 0282 wp 00000002 lp 00000000 monthcal.c:631: 16: expected: 0083 - actual: 0007 wp 00000000 lp 00000000 monthcal.c:631: 17: expected: 0005 - actual: 0047 wp 00000000 lp 0072f630 monthcal.c:631: 18: expected: 0003 - actual: 0005 wp 00000000 lp 01d701ee monthcal.c:631: 19: expected: nothing - actual: 0003 wp 00000000 lp 001a0003 monthcal.c:655: old style: 0x50800000, new style: 0x50800002 monthcal.c:655: old style: 0x50800000, new style: 0x50800000 monthcal.c:655: old style: 0x50800002, new style: 0x50800000 monthcal.c:655: old style: 0x50800002, new style: 0x50800002 monthcal.c:655: old style: 0x50800000, new style: 0x50800001 monthcal.c:655: old style: 0x50800000, new style: 0x50800000 monthcal.c:655: old style: 0x50800001, new style: 0x50800000 monthcal.c:655: old style: 0x50800001, new style: 0x50800001 https://test.winehq.org/data/patterns.html#comctl32:monthcal WM_GETMINMAXINFO == 0x0024 WM_IME_SETCONTEXT == 0x0281 WM_IME_NOTIFY == 0x0282 create_parent_window_seq[] already has some optional IME messages so it looks like more need to be added / moved to another place. The WM_GETMINMAXINFO is new though. -- 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.

1 1

[Bug 39659] New: comctl32:button test gets unexpected WM_CANCELMODE on my Windows 8 laptop
by wine-bugs＠winehq.org 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=39659 Bug ID: 39659 Summary: comctl32:button test gets unexpected WM_CANCELMODE on my Windows 8 laptop Product: Wine Version: 1.8-rc1 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Created attachment 52866 --> https://bugs.winehq.org/attachment.cgi?id=52866 log of test failure Test report: https://test.winehq.org/data/1d19eb15d4abfdd14dccc5ac05b83c0ee1a1ace1/win8_… Message tests calling SetFocus() on a button fail on my Windows 8 machine, because they get a WM_CANCELMODE message they weren't expecting. I have no idea what's special about my setup. It doesn't matter if I run the test stand-alone or with the full test suite, or if I run it as a dedicated user with a default configuration. -- 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 30875] New: Unable to deselect character blocks in BMFont
by wine-bugs＠winehq.org 12 May '22

12 May '22

http://bugs.winehq.org/show_bug.cgi?id=30875 Bug #: 30875 Summary: Unable to deselect character blocks in BMFont Product: Wine Version: 1.5.6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dav75uk(a)yahoo.co.uk Classification: Unclassified Run BMFont (http://www.angelcode.com/products/bmfont/) and click on some of the checkboxes to the right to select characters to be included. It is not possible to uncheck the checkboxes. Workaround is to unselect one of the characters (click on a character in that range) which changes the full checked box to a part check box. The part check box can be unselected. -- 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 52911] New: ole32:moniker fails on Windows in the UTF-8 codepage
by WineHQ Bugzilla 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=52911 Bug ID: 52911 Summary: ole32:moniker fails on Windows in the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ole32:moniker fails on Windows in the UTF-8 codepage: moniker.c:2189: Test failed: IsEqual failed with error 0x000001 [...] https://test.winehq.org/data/patterns.html#ole32:moniker So the failures happen because moniker1 and moniker2 are always different. Adding a call to winetest_push_context() shows that the failures all happen for string 2 which ole32:moniker uses to skip tests on code pages where there are round-trip issues: {0xc0, 0xc1, 0xc2, 0xc3, 0xc4, 0xc5, 0xc6, 0xc7, 0xc8, 0xc9, 0xca, 0xcb, 0xcc, 0xcd, 0xce, 0xcf, 0xd0, 0}, [...] skip("string 2 doesn't round trip in codepage %u\n", GetACP() ); So it looks like the skip fails to trigger for the UTF-8 codepage (or that we should do something else to make the UTF-8 case work). -- 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.

1 2

[Bug 45432] New: Implement Windows Native Firewall Rules for Lightwave Software Licensing - netfw_rules
by wine-bugs＠winehq.org 12 May '22

12 May '22

https://bugs.winehq.org/show_bug.cgi?id=45432 Bug ID: 45432 Summary: Implement Windows Native Firewall Rules for Lightwave Software Licensing - netfw_rules Product: Wine Version: 3.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: newel.anderson(a)gmail.com Distribution: --- Created attachment 61753 --> https://bugs.winehq.org/attachment.cgi?id=61753 Terminal logs installing and launching Lightwave under WIne 3.11 in Linux Lightwave requires Windows Native Firewall Inbound/Outbound Rules in order to register/activate one's license. For reference, please see: https://forum.winehq.org/viewtopic.php?f=8&t=30847&p=116945#p116945 (I'm wineink) Towards the end of the above thread I posted terminal output as well as screenshots. Disabling Windows Firewall, as well as deleting the inbound/outbound rules in Windows, deactivates my license. Re-enabling the rules and Windows Firewall reactivates my license. Since this functionality doesn't exist in Wine, Wine hasn't to my knowledge implemented Windows Native Firewall Rules, it's impossible to register/activate my legally purchased license in Wine. Thank you for your time and consideration. ***Please note, the above applies only to a FULL license of Lightwave. The trial, which is node-locked, works as designed. Unfortunately, the FULL license is not node-locked. -- 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 45

[Bug 52986] New: d3d9:device - In Wine test_vertex_buffer_read_write() fails on on cw-rx460
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52986 Bug ID: 52986 Summary: d3d9:device - In Wine test_vertex_buffer_read_write() fails on on cw-rx460 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- d3d9:device - In Wine test_vertex_buffer_read_write() only succeeds on cw-rx460: device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 0. device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 1. device.c:13967: Test failed: Got unexpected value 3.00000000e+000, i 2. https://test.winehq.org/data/patterns.html#d3d9:device This is specific to this machine so it seems likely that this is related to the graphics card / driver. -- 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.

1 0

[Bug 52985] New: d3d9:device - test_reset_fullscreen() gets an unexpected WM_SIZE message with fvwm
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52985 Bug ID: 52985 Summary: d3d9:device - test_reset_fullscreen() gets an unexpected WM_SIZE message with fvwm Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Created attachment 72354 --> https://bugs.winehq.org/attachment.cgi?id=72354 The TestBot's fvwm configuration d3d9:device - test_reset_fullscreen() gets an unexpected WM_SIZE message with fvwm: device.c:4822: Test failed: Received unexpected WM_SIZE message. https://test.winehq.org/data/patterns.html#d3d9:device This failure happens on cw-gtx560, cw-rx460 and debian11 VM which all run Debian 11 with fvwm, and on debiant VM which runs Debian Testing with fvwm. But it does not happen on fg-deb64 which runs Debian 11 too, but with KDE's window manager. So it is pretty likely that this failure only happens when running fvwm. -- 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.

1 1

[Bug 52984] New: d3d8:device - test_cursor_pos() missing a MOUSEMOVE on cw-gtx560 and cw-rx460
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52984 Bug ID: 52984 Summary: d3d8:device - test_cursor_pos() missing a MOUSEMOVE on cw-gtx560 and cw-rx460 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com d3d8:device - test_cursor_pos() is missing a MOUSEMOVE most of the time on cw-gtx560 and cw-rx460: device.c:1324: Test failed: Didn't receive MOUSEMOVE 0 (50, 50). https://test.winehq.org/data/patterns.html#d3d8:device This happens almost systematically on cw-gtx560 and cw-rx460 with Windows 10 1709 to 1909 but happens much less frequently with more recent Windows versions. Also it never happens in the TestBot VMs running the same Windows versions and also does not happen on fgtb-w10pro64-rx550. So it may be related to the set of display modes that the monitor supports which would explain why the KVM-connected machines are impacted and not the others. Or it could be related to the GPU drivers and fgtb-w10pro64-rx550 just got lucky because it's on a more recent Windows version. -- 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.

1 1

[Bug 52935] New: comctl32:tab - test_tab(-1&-3) fails on Windows with the UTF-8 codepage
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52935 Bug ID: 52935 Summary: comctl32:tab - test_tab(-1&-3) fails on Windows with the UTF-8 codepage Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:tab's test_tab(-1&-3) fails on Windows with the UTF-8 codepage: tab.c:591: Testing with default MinWidth tab.c:579: Test failed: with icon, set size > icon: Expected [51,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [51,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [51,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [54,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [54,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [54,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [57,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [57,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [57,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [60,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [60,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [60,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [63,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [63,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [63,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [66,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [66,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [66,1] got [48,1] tab.c:593: Testing with MinWidth set to -3 tab.c:579: Test failed: with icon, set size > icon: Expected [51,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [51,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [51,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [54,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [54,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [54,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [57,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [57,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [57,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [60,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [60,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [60,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [63,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [63,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [63,1] got [48,1] tab.c:579: Test failed: with icon, set size > icon: Expected [66,30] got [48,30] tab.c:580: Test failed: with icon, set size < icon: Expected [66,20] got [48,20] tab.c:581: Test failed: with icon, min size: Expected [66,1] got [48,1] https://test.winehq.org/data/patterns.html#comctl32:tab Hindi + UTF-8 is the only locale where this test fails on Windows at this time. In particular there is no failure on the standard Hindi locale (English system locale) so this appears to be specific to UTF-8. -- 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.

1 2

[Bug 52939] New: advapi32:registry - test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52939 Bug ID: 52939 Summary: advapi32:registry - test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 72312 --> https://bugs.winehq.org/attachment.cgi?id=72312 Loop on test_RegNotifyChangeKeyValue() to reproduce the event failures advapi32:registry's test_RegNotifyChangeKeyValue() has an intermittent failure on all Windows versions: registry.c:3471: Test failed: expected ERROR_SUCCESS, got 6 registry.c:3599: Test failed: expected WAIT_OBJECT_0, got 258 https://test.winehq.org/data/patterns.html#advapi32:registry The failure is pretty rare so it is likely to cause false positives. The attached patch makes it possible to systematically reproduce the issue, at least on my test VM. With the 10000 loops I get 4 to 5 cases with the failure (so a rate of 0.05%) and a test run still takes under 8 seconds. -- 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.

1 3

[Bug 52925] New: usp10:usp10 The wgDefault check fails on Windows in non-basic locales (Hebrew, Japanese, etc)
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52925 Bug ID: 52925 Summary: usp10:usp10 The wgDefault check fails on Windows in non-basic locales (Hebrew, Japanese, etc) Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: usp10 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com usp10:usp10's wgDefault check in test_ScriptGetFontProperties() fails on some bitmap fonts in a number of locales: * Arabic usp10.c:2591: Test failed: bitmap font System wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font MS Serif wgDefault 0126, tmDefaultChar 0085 usp10.c:2591: Test failed: bitmap font MS Sans Serif wgDefault 0126, tmDefaultChar 0085 * Hebrew usp10.c:2591: Test failed: bitmap font Small Fonts wgDefault 01ac, tmDefaultChar 0080 * Hindi + UTF-8 (no failure for plain Hindi) usp10.c:2591: Test failed: bitmap font System wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Courier wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font MS Serif wgDefault 00fd, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font MS Sans Serif wgDefault 00fd, tmDefaultChar 0081 usp10.c:2591: Test failed: bitmap font Small Fonts wgDefault 00fd, tmDefaultChar 0080 * Japanese usp10.c:2591: Test failed: bitmap font FixedSys wgDefault 00f0, tmDefaultChar 00a0 usp10.c:2591: Test failed: bitmap font @FixedSys wgDefault 00f0, tmDefaultChar 00a0 * Chinese usp10.c:2591: Test failed: bitmap font System wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @System wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Terminal wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @Terminal wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font Fixedsys wgDefault 00ac, tmDefaultChar 0080 usp10.c:2591: Test failed: bitmap font @Fixedsys wgDefault 00ac, tmDefaultChar 0080 https://test.winehq.org/data/patterns.html#usp10:usp10 In each case we get the expected value on Windows with a number of fonts but there are some exceptions that cause the failures. For a given locale the exceptions all have the same wgDefault value which means there is probably some logic to it. So we either need to come up with a better way to find the expected wgDefault value, or to radically loosen the test, or to restrict the test to some 'safe' fonts, or to remove the test entirely. -- 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.

1 2

[Bug 52981] New: windows.media.speech:speech - SpeechRecognizer fails to initializes with elevated privileges
by WineHQ Bugzilla 11 May '22

11 May '22

https://bugs.winehq.org/show_bug.cgi?id=52981 Bug ID: 52981 Summary: windows.media.speech:speech - SpeechRecognizer fails to initializes with elevated privileges Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Most of test_SpeechRecognizer() is skipped when run with elevated privileges: speech.c:896: SpeechRecognizer default language L"fr-FR". speech.c:1172: Tests skipped: Could not init SpeechRecognizer with default language! https://test.winehq.org/data/patterns.html#windows.media.speech:speech The involved lines are: 919 hr = RoActivateInstance(hstr, &inspectable); 922 if (hr == S_OK) ... 1170 else if (hr == SPERR_WINRT_INTERNAL_ERROR) /* Not sure when this triggers. Probably if a language pack is not installed. */ 1171 { 1172 win_skip("Could not init SpeechRecognizer with default language!\n"); An analysis of the test results across Windows versions shows that we see this SPERR_WINRT_INTERNAL_ERROR on Windows 10 >= 1809: cw-gtx560-1507 S_OK cw-rx460-1507 S_OK w1064v1507 S_OK w1064v1607 S_OK cw-gtx560-1709 S_OK cw-rx460-1709 S_OK w1064v1709 S_OK cw-gtx560-1809 skipped cw-rx460-1809 skipped w1064v1809 skipped cw-gtx560-1909 skipped cw-rx460-1909 skipped w1064v1909 skipped w1064v2004 skipped cw-gtx560-2009 skipped cw-rx460-2009 skipped w1064v2009 skipped cw-gtx560-21h1 skipped cw-rx460-21h1 skipped w10pro64-21h1 skipped cw-gtx560-21h2 skipped cw-rx460-21h2 skipped w1064-21h2 skipped w10pro64-21h2 skipped So far that looks pretty clear cut: Microsoft changed things around 1809 such that processes running with elevated privileges cannot / are not allowed to perform speech recognition. That would mean the test should drop the privileges so it can run on any platform. However the test was not skipped in the w10pro64v2004 and w10pro64 (21H1) test configurations... until they were upgraded. So this indicates that there may be a way to get this test to work even while retaining elevated privileges. But how? To help debug the issue I added two test configurations: * w10pro64restored The w10pro64 VM restored from a backup of the pre-2022-05 upgrade VM. Surprisingly the test still ends up being skipped! * w10pro64old Luckily before the upgrade I moved the old VM out of the way. It is now available as w10pro64old with the exact same live snapshots. Comfortingly the test is still not skipped, even after waiting some time and rebooting. That last part indicates there may be something either in the way the TestBot creates the live snapshots, or in the "WineTestBot VMs" checklist I go through when preparing the VMs and the cw-* machines (but then the clear 1809 cutoff point is quite a coincidence). -- 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.

1 0

[Bug 33621] New: [UWIN] ksh93 from UWIN generates a lot of fixme warnings
by wine-bugs＠winehq.org 11 May '22

11 May '22

http://bugs.winehq.org/show_bug.cgi?id=33621 Bug #: 33621 Summary: [UWIN] ksh93 from UWIN generates a lot of fixme warnings Product: Wine Version: 1.5.30 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: simon.toedt(a)gmail.com Classification: Unclassified Running ksh93 (Korn Shell 93) from the UWIN (Unix emulation on Windows) toolkit generates a lot of "fixme" warnings and the shell is generally not useable. The goal is to use WINE for automated testing without having to fire up a full blown Windows system each time in VMware or real iron. Steps to test: 1. Install UWIN: > wget --http-user="I accept www.opensource.org/licenses/eclipse" --http-passwd="." 'http://www2.research.att.com/~gsf/download/beta/uwin-base.2013-02-08.win32.…' > wine uwin-base.2013-02-08.win32.i386.exe 2. Run Windows/UWIN version of ksh93: wine64 'C:\Program Files/UWIN/usr/bin/ksh.exe' fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:process:SetProcessShutdownParameters (00000000, 00000001): partial stub. fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:ntdll:NtSetInformationToken unimplemented class 4 fixme:advapi:LsaOpenPolicy ((null),0x23f980,0x00000001,0x23f950) stub fixme:advapi:LsaClose (0xcafe) stub fixme:netbios:NetServerEnum Stub ((null) 100 0x23f440 -1 0x23fbb8 0x23fbc8 24 (null) (nil)) fixme:netapi32:NetGetDCName ((null), (null), 0x23f448) stub! fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0xf70850,symt:0xfce150) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:dbghelp_dwarf:compute_location Only supporting one breg (r10/338 -> r8/336) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x20e2370,symt:0x2140480) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"libc.so.6"), for debug_info(abbrev:0x21926b8,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e98,symt:0x2970264) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2943cb0,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"ld-linux-x86-64.so.2"), for debug_info(abbrev:0x2914e90,symt:(nil)) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:compute_location Only supporting one breg (rdx/331 -> rax/328) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x36b3448,symt:0x378fa1c) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743718,symt:0x37781b4) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x3743658,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x8834c0,L"libgcc_s.so.1"), for debug_info(abbrev:0x37425a0,symt:0x3754e38) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x8834c0,L"kernel32<elf>"), for debug_info(abbrev:0x3824860,symt:(nil)) fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented fixme:netapi32:NetUserGetInfo Level 3 is not implemented wine version is wine-1.5.30. Wine versions older than wine-1.5.30 may not work as described in bug 33619. IMO the most pressing problems are: 1. fixme:process:SetProcessShutdownParameters (00000300, 00000001): partial stub. 2. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented 3. fixme:netapi32:NetUserGetInfo Level 3 is not implemented 4. fixme:ntdll:NtSetInformationToken unimplemented class 4 5. fixme:netapi32:NetQueryDisplayInformation Level 1 partially implemented -- 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 52968] New: CPU BoostTester manages to run only on real cores in Windows, but not with wine
by WineHQ Bugzilla 09 May '22

09 May '22

https://bugs.winehq.org/show_bug.cgi?id=52968 Bug ID: 52968 Summary: CPU BoostTester manages to run only on real cores in Windows, but not with wine Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christian.frank(a)gmx.de Distribution: --- Hi, the following tiny porgram is used to test the boost capability of cpus. It detects real cores and only tests those, not the smt siblings. On windows it manages to run on the real cores only. On Linux it runs on the cores 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30 I am using a 5950x. The real cores are 0-15. The siblings ar 16-31. 0+16 is a pair, 1+17, 2+18 etc.. So instead of testing the 16 real cores, it is testing only 8 + siblings. The software is availible here, including source. I don't know if the software is doing some strange things to detect the real cores or if the issue is on the wine side. As the source is just a handful of c++ code, someone with experience might take a look and judge where the problem is, wine or the program. Here is the link: https://github.com/jedi95/BoostTester Many thx ! -- 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.

1 2

[Bug 52976] New: Daagon Map Maker on itch.io crash
by WineHQ Bugzilla 08 May '22

08 May '22

https://bugs.winehq.org/show_bug.cgi?id=52976 Bug ID: 52976 Summary: Daagon Map Maker on itch.io crash Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: registry Assignee: wine-bugs(a)winehq.org Reporter: ildaniel999(a)hotmail.com Distribution: --- Created attachment 72346 --> https://bugs.winehq.org/attachment.cgi?id=72346 wine file loads up to 100%, changes screen settings, but then crashes -- 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.

1 0

[Bug 52684] New: Command and Conquer Generals (and C&C Zero Hour) have no ground textures
by WineHQ Bugzilla 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=52684 Bug ID: 52684 Summary: Command and Conquer Generals (and C&C Zero Hour) have no ground textures Product: Wine Version: 7.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: bender647(a)yahoo.com Regression SHA1: 1632b8e7a419ebf256c4a356a58d505ef918f2fe Distribution: Slackware Introduced in wine-7.3 with commit 1632b8e7a419ebf256c4a356a58d505ef918f2fe, the C&C Generals game engine does not draw ground textures. The ground (or water) area is black. Reverting to wine-7.2, or applying this commit as a reverse-patch on wine-7.4 will fix the issue. The commit was found by bisecting the git tree. This symptom appears in older bug reports but the fixes there do not appear to work now. Tested on two platforms, but both were Intel i915 graphics. If necessary, I can get access to an Nvidia platform. To reproduce: 1. A free demo is available for download to run the game: https://www.moddb.com/downloads/start/111369 (https://www.moddb.com/games/cc-generals/downloads/command-conquer-generals-…). 2. Install in 32-bit prefix. 3. Run with `wine start generals.exe -nologo` and the game engine will be seen running behind the main menu. The ground will be blank if the bug is present. Verified to affect: https://appdb.winehq.org/objectManager.php?sClass=version&iId=4881 https://appdb.winehq.org/objectManager.php?sClass=version&iId=35407 Likely also: https://appdb.winehq.org/objectManager.php?sClass=version&iId=1717 -- 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.

1 24

[Bug 45098] New: FrostPunk: multiple graphical glitches
by wine-bugs＠winehq.org 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=45098 Bug ID: 45098 Summary: FrostPunk: multiple graphical glitches Product: Wine Version: 3.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)embed.me.uk Distribution: --- Created attachment 61268 --> https://bugs.winehq.org/attachment.cgi?id=61268 FrostPunk log With patch posted in https://bugs.winehq.org/show_bug.cgi?id=45080 the game sucessfully starts however there are severe graphical glitches which render it unplayable. Log attached. -- 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 2155] Failure of SetFocus, SetActiveWindow and SetForegroundWindow
by WineHQ Bugzilla 07 May '22

07 May '22

https://bugs.winehq.org/show_bug.cgi?id=2155 Ker noa <blue-t(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t(a)web.de -- 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.

1 0

[Bug 50458] New: Tooltips block input in Foobar2000
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=50458 Bug ID: 50458 Summary: Tooltips block input in Foobar2000 Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: debilerpc(a)web.de Distribution: --- **Context:** Like with most media players, Foobar2000's playlist view is essentially a spreadsheet where each line is a track and each column displays a tag or metadata field. If the length of the tag exceeds the width of the column, it gets cut off. You can see the full tag in a tooltip by hovering over it with a mouse in that case. **The problem:** As long as the tooltip is displayed, the app registers neither keyboard nor mouse input. I suspect this problem exists in a variety of [apps](https://bugs.winehq.org/show_bug.cgi?id=16227), not just Foobar2000, but here it is especially annoying. **Expected behavior:** When input is sent, the tooltip should disappear, and Foobar2000 should react to the input. This is what happens under Windows 10. -- 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.

1 6

[Bug 52771] New: Wine console creation breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52771 Bug ID: 52771 Summary: Wine console creation breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The way Wine creates the window for console applications breaks comctl32:button, dinput:keyboard, user32:dialog, user32:input, user32:monitor and user32:win. https://test.winehq.org/data/patterns.html#comctl32:button https://test.winehq.org/data/patterns.html#dinput:keyboard https://test.winehq.org/data/patterns.html#user32:dialog https://test.winehq.org/data/patterns.html#user32:input https://test.winehq.org/data/patterns.html#user32:monitor https://test.winehq.org/data/patterns.html#user32:win These all started failing in Wine on 2022-03-17 with the commit below (also referenced in bug 52761): commit f034084d49b354811096524d472ae5172ac1cebf Author: Eric Pouech <eric.pouech(a)gmail.com> Date: Thu Mar 17 08:27:28 2022 +0100 kernelbase: Handle corner case in CreateProcess. In CreateProcess, if: - parent isn't attached to a console - CreateProcess's flag isn't set with DETACHED_PROCESS nor CREATE_NEW_CONSOLE - child is a CUI program then a console must be allocated for the child. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52048 Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com> Signed-off-by: Jacek Caban <jacek(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> The way the TestBot starts the tests in Wine is this [1]: testagentd (Unix, no terminal) \- shell script (sh Unix, no terminal) \- WineTest.pl (perl Unix, no terminal) \- ./wine TestLauncher (Windows CUI, no console) \- unit test (Windows CUI) -> creates a console \- unit test can recurse upon itself (CUI) I will now try to summarize the current understanding of the issue from the wine-devel discussion [2], using the above figure as a reference: 1. testagentd is a daemon so it does not have an associated terminal. 2. When ./wine does not have a terminal it does not create a console window, even when starting a console application. This is so wine can be used for background (batch) tasks without requiring a X session or popping up windows all over the place. 3. But when a Windows application calls CreateProcess() without DETACHED_PROCESS, a console does get created. This is what happens when TestLauncher starts a unit test. 4. While the console object is created synchronously in the wineserver process, the actual window is created asynchronously (by wineconsole). This causes it to pop up while the unit test as already started, which confuses the tests that check the window hierarchy, the focus, etc. There are two ways the above differ from Windows: 1. I believe Windows creates both the console object and the matching window synchronously. So even if the console was created when starting the test unit there should be no failure. 2. On Windows the shell script is replaced by a batch script which triggers the console creation. So the console creation happens a bit earlier which could also mask any window creation delay. The reason why f034084d49b3 made a difference is that before Wine was not creating console windows. [1] More details on the different ways the TestBot starts the tests: https://www.winehq.org/pipermail/wine-devel/2022-April/212550.html [2] March: https://www.winehq.org/pipermail/wine-devel/2022-March/212330.html April: https://www.winehq.org/pipermail/wine-devel/2022-April/212513.html -- 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.

1 14

[Bug 45388] New: user32: edit fails on Traditional Chinese and Korean locales
by wine-bugs＠winehq.org 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=45388 Bug ID: 45388 Summary: user32:edit fails on Traditional Chinese and Korean locales Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:edit fails with the following errors on Traditional Chinese and Korean locales: edit.c:1489: Test failed: 0: got 1, 1 edit.c:1510: Test failed: 0: got 1, 1 edit.c:1524: Test failed: 0: got 1, 1 edit.c:1538: Test failed: 0: got 1, 1 See: * Source matching the above https://source.winehq.org/git/wine.git/?a=blob;f=dlls/user32/tests/edit.c;h… * user32:edit WineTest failures https://test.winehq.org/data/tests/user32:edit.html The errors can be reproduced on the newtb-wvistau64-zh-cn TestBot VM, and also happen on fg-win7u64-1spie9-ko. -- 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

[Bug 52869] New: kernel32:locale - test_CompareStringA() fails in Wine in Hindi
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52869 Bug ID: 52869 Summary: kernel32:locale - test_CompareStringA() fails in Wine in Hindi Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- test_CompareStringA() started failing in Wine in Hindi recently: locale.c:1884: Test failed: expected CSTR_LESS_THAN, got 2 locale.c:1886: Test failed: expected CSTR_GREATER_THAN, got 2 https://test.winehq.org/data/patterns.html#kernel32:locale A bisect shows this failure started with the commit below: commit 8993e15cfa5b77ac2487239354ffe63bbc5e562d Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Apr 11 17:21:47 2022 +0200 kernelbase: Support UTF-7/8 codepages in get_codepage_table(). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

1 4

[Bug 52743] New: regression cannot write to _fdopen'ed stdout
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52743 Bug ID: 52743 Summary: regression cannot write to _fdopen'ed stdout Product: Wine Version: 7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xantares09(a)hotmail.com Distribution: --- since wine 7.2, opening stdout with _fdopen and printing into it crashes ``` #include <stdio.h> #include <io.h> #include <fcntl.h> int main() { FILE * m_stdout = _fdopen(_fileno(stdout), "wb"); fprintf(m_stdout, "foo\n"); fclose(m_stdout); return 0; } $ x86_64-w64-mingw32-gcc main.c $ wine a.exe ... wine: Unhandled page fault on read access to 0000000000000050 at address 0000000170059685 (thread 0128), starting debugger... ... ``` For context, this is what qt-xmlpatterns does: https://github.com/qt/qtxmlpatterns/blob/dev/tools/xmlpatterns/main.cpp#L184 -- 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.

1 17

[Bug 52362] New: Powershell Core 7 installer hangs forever on Chinese locale (LC_ALL=zh_Han.UTF-8)
by WineHQ Bugzilla 06 May '22

06 May '22

https://bugs.winehq.org/show_bug.cgi?id=52362 Bug ID: 52362 Summary: Powershell Core 7 installer hangs forever on Chinese locale (LC_ALL=zh_Han.UTF-8) Product: Wine Version: 7.0-rc3 Hardware: x86-64 URL: https://github.com/PowerShell/PowerShell/releases/down load/v7.1.5/PowerShell-7.1.5-win-x64.msi OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Hi, someone i was trying to help someone to get this installed and he reported this to me (I couldn`t reproduce it), that the installer hung for him, and in fact he found that it was due to the fact he was running with LC_ALL=zh_Han.UTF-8 I don`t know anything about these chinese locales, but report anyway as could be a bug in wine (?). reproduce: LC_ALL=zh_Han.UTF-8 5ine msiexec /i PowerShell-7.1.5-win-x64.msi A +relay shows it`s looking for files in directory zh-CN which is not there, though there is zn-Han(s) directories. But just copying zh-Han to zh-CN didn`t help either. Anyway, I guess someone with more knowledge about (Chinese) locales would have lots more clues than i have... -- 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.

1 9

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