September 2023 - Wine-Bugs - list.winehq.org

[Bug 50152] New: YOU and ME and HER: Game crashes after launching from game launcher
by WineHQ Bugzilla Feb. 21, 2025

Feb. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=50152 Bug ID: 50152 Summary: YOU and ME and HER: Game crashes after launching from game launcher Product: Wine Version: 5.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aleksandr_kines(a)rambler.ru Distribution: --- Created attachment 68660 --> https://bugs.winehq.org/attachment.cgi?id=68660 Terminal output Wine crashes when I click on "Start Game" button in game launcher and wait some time after game window appeared. -- 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 46206] New: Altium Designer 17 account sign in fails as of 3.19
by wine-bugs＠winehq.org Feb. 21, 2025

Feb. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=46206 Bug ID: 46206 Summary: Altium Designer 17 account sign in fails as of 3.19 Product: Wine Version: 3.19 Hardware: x86-64 URL: https://s3.amazonaws.com/altium-release-manager/Altium _Designer_17/OfflineSetup_Altium_Designer_Public_17_1_ 9.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhansonxi(a)gmail.com Distribution: Ubuntu Account sign-ins are broken in Altium Designer 17.1.9 (and probably other releases) as of Wine 3.19. Steps to reproduce: 1. Launch Altium Designer. 2. Close floating window (Storage, etc.) which will likely trigger an error (probably bug #39765 which I'll verify later) 3. At MyAccount/License Management page click "Sign in" link 4. At "Account Sign In" dialog (which can get stuck behind main window) enter anything for user name and password, check the "I have read and understand the warning" privacy invasion checkbox, then the "Sign in" button. Expected behavior: Dialog box closes then reappears a moment later when sign-in fails. Wine 3.19-3.21 behavior: Dialog closes then an "Out of memory" error dialog is displayed. Installation: 1. Download the offline installer from the URL (3.6GB). Extract to subdirectory. 2. winetricks -q corefonts dotnet461 mdac28 win7 I used winetricks 20180815-next. Verified NET Runtimes with netfx_setupverifier-20180517.exe. Manually triggered GAC rebuild via ngen.exe since winetricks didn't seem to do so and it cluttered up the logs when it randomly started on its own. 3. Run the Altium installer. To save time deselect the optional items. Other: There's a nuisance rundll32.exe error at start-up reporting "This application could not be started". It doesn't seem to be related to this bug although I haven't found the cause of it yet. -- 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 14

[Bug 24308] New: Fullscreen fails for MechWarrior 4 games (Only one D3D device per DirectDraw object)
by wine-bugs＠winehq.org Feb. 21, 2025

Feb. 21, 2025

http://bugs.winehq.org/show_bug.cgi?id=24308 Summary: Fullscreen fails for MechWarrior 4 games (Only one D3D device per DirectDraw object) Product: Wine Version: 1.3.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: georg298(a)gmx.de For all MechWarrior 4 games, fullscreen fails with message fixme:ddraw:d3d7_CreateDevice Only one Direct3D device per DirectDraw object supported. Obviously, the game falls back to window'ed mode, as static HRESULT WINAPI d3d7_CreateDevice(IDirect3D7 *iface, REFCLSID riid, IDirectDrawSurface7 *surface, IDirect3DDevice7 **device) returns DDERR_INVALIDPARAMS changing this behaviour (returning D3D_OK instead): if (ddraw->d3ddevice) { FIXME("Only one Direct3D device per DirectDraw object supported.\n"); LeaveCriticalSection(&ddraw_cs); return D3D_OK; // return DDERR_INVALIDPARAMS; } makes fullscreen work for these games. Probably it's not "legal" to return D3D_OK in this case, but maybe there is a real solution for this problem? -- 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 26

[Bug 55219] New: Sample() method fails to compile for ps_2_0
by WineHQ Bugzilla Feb. 20, 2025

Feb. 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=55219 Bug ID: 55219 Summary: Sample() method fails to compile for ps_2_0 Product: vkd3d Version: 1.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: bunglehead(a)gmail.com Distribution: --- Created attachment 74833 --> https://bugs.winehq.org/attachment.cgi?id=74833 test Extracted from existing d3dcompiler tests: --- 1 sampler s; 2 Texture2D t; 3 float4 main() : COLOR 4 { 5 return t.Sample(s, float2(0.5, 0.5)); 6 } --- This fails to compile currently, on Windows this produces (combined?) s+t definition at s0. -- 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 54377] New: Rayman Origins has messed up rendering due to missing 'tan' handling
by WineHQ Bugzilla Feb. 20, 2025

Feb. 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=54377 Bug ID: 54377 Summary: Rayman Origins has messed up rendering due to missing 'tan' handling Product: vkd3d Version: 1.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Distribution: --- 0218:err:d3dcompiler:D3DCompile2 Shader log: 0218:err:d3dcompiler:D3DCompile2 <anonymous>:166:18: E5005: Function "tan" is not defined. 0218:err:d3dcompiler:D3DCompile2 -- 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 54417] New: Cradle needs 'sincos' support
by WineHQ Bugzilla Feb. 20, 2025

Feb. 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=54417 Bug ID: 54417 Summary: Cradle needs 'sincos' support Product: vkd3d Version: 1.6 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- 0184:fixme:d3dcompiler:D3DCompile2 Ignoring flags 0x4810. vkd3d:fixme:hlsl_yylex Unsupported preprocessor #pragma directive at line 1. 0184:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 0184:err:d3dcompiler:D3DCompile2 Shader log: 0184:err:d3dcompiler:D3DCompile2 core/shaders/default/render/fragment_copy_2d.shader:209:1: E5000: syntax error, unexpected KW_SAMPLERCOMPARISONSTATE 0184:err:d3dcompiler:D3DCompile2 0184:err:d3dcompiler:D3DCompile2 Failed to compile shader, vkd3d result -4. 0184:err:d3dcompiler:D3DCompile2 Shader log: 0184:err:d3dcompiler:D3DCompile2 core/shaders/default/render/vertex_hdr_shaft.shader:232:1: E5005: Function "sincos" is not defined. 0184:err:d3dcompiler:D3DCompile2 1.6-86-gf9e7cb63 -- 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 52568] New: Support for AF_UNIX is missing
by WineHQ Bugzilla Feb. 20, 2025

Feb. 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=52568 Bug ID: 52568 Summary: Support for AF_UNIX is missing Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: ralf.habacker(a)freenet.de Distribution: --- Newer Windows 10 builds supports AF_UNIX, see https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/ for details. There have been unfinished attempts to incorporate such support into wine, see https://www.winehq.org/pipermail/wine-devel/2021-May/187049.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 17

[Bug 49167] New: Wine staging 5.8 not available on macos download page
by WineHQ Bugzilla Feb. 18, 2025

Feb. 18, 2025

https://bugs.winehq.org/show_bug.cgi?id=49167 Bug ID: 49167 Summary: Wine staging 5.8 not available on macos download page Product: Wine-staging Version: 5.8 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rmkk(a)atlas.cz CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Please check the 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 27

[Bug 10522] New: endless WM_PAINT loop bug (update regions, queue paint count)
by wine-bugs＠winehq.org Feb. 17, 2025

Feb. 17, 2025

http://bugs.winehq.org/show_bug.cgi?id=10522 Summary: endless WM_PAINT loop bug (update regions, queue paint count) Product: Wine Version: CVS/GIT Platform: PC URL: http://www.microsoft.com/whdc/devtools/debugging/install x86.mspx OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Created an attachment (id=9265) --> (http://bugs.winehq.org/attachment.cgi?id=9265) trace with WINEDEBUG=+tid,+message,+win,+server Hello, I've seen this bug a while ago in other apps but ignored it because it was not easily to reproduce. Well until recently when I tested some stuff with windbg from "Debugging Tools for Windows" (Microsoft). I used debugging tools version 6.8.4.0 and recent GIT (wine-0.9.49-302-g58b85bb). Immediately when a child window was opened using toolbar (register, locals, .. whatever), windbg would become unresponsive, eating most CPU. Happens in both GUI modes - "floating/docking toolwindow" and "MDI emulation. Though "MDI emulation" is more obvious, it actually shows the endless refreshing (window caption). Attached is WINEDEBUG=+tid,+message,+win,+server log. Additionally I added a trace message which prints the current queue paint count (when incremented or fetched) which makes some things easier to spot. Printed as "inc_queue_paint_count: %d" and "get_message_paint_count: %d". The window hierarchy is as follows: --- snip --- *root*=0x10020 Shell_TrayWnd=0x10022 WinDbgFrameClass=0x10024 DockClass=0x10026 ToolbarWindow32=0x10028 msctls_statusbar32=0x1002a tooltips_class32=0x1002e WinBaseClass=0x10030 ToolbarWindow32=0x10032 SysListView32=0x10034 SysHeader32=0x10036 RichEdit20W=0x10038 --- snip --- After the child windows are created the queue paint count never drops to zero, resulting in endless WM_PAINT processing. Maybe some update (region) code path missed or flags problem? I played a bit with ignoring null region updates and it seemed to help a bit (preventing endless WM_PAINT loop) though other stuff wasn't drawn properly then. Regards -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 41

[Bug 51697] New: Far cry 5, frequent stuttering due to ntdll spam
by WineHQ Bugzilla Feb. 16, 2025

Feb. 16, 2025

https://bugs.winehq.org/show_bug.cgi?id=51697 Bug ID: 51697 Summary: Far cry 5, frequent stuttering due to ntdll spam Product: Wine-staging Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gab.pulcio(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 70570 --> https://bugs.winehq.org/attachment.cgi?id=70570 12.5MB log, mostly spam from ntdll that causes a lot of lag in-game, in my opinion DXVK is not the issue as far as I know, since it doesn't throw any error, NTDLL though, spams like hell, since the log is 12.5MB and that makes the game laggy very frequently, sometimes my FPS dips to 15/20 for various seconds (and it's not the CPU throttling lag, since I disabled PROCHOT response and undervolted the CPU) -- 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 19