January 2021 - Wine-bugs - list.winehq.org

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

21 Feb '25

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 39057] New: Support for Indexed Vertex Blending
by wine-bugs＠winehq.org 21 Feb '25

21 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=39057 Bug ID: 39057 Summary: Support for Indexed Vertex Blending Product: Wine Version: 1.7.47 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: swswine(a)gmail.com Distribution: --- Created attachment 52025 --> https://bugs.winehq.org/attachment.cgi?id=52025 Patch to implement indexed vertex blending support Vertex blending support has been added recently (https://bugs.winehq.org/show_bug.cgi?id=6955 was closed). But indexed vertex blending is not supported yet. I've implemented rather straightforward patch to do it which works for me, it is attached. Though I am far not familiar with wined3d development and not quite sure that my patch is complete and does not have any caveats. A potential caveat with this patch is the following. Besides using indexes in vertex shaders, a big enough number of supported vertex blend matrices is required to really support this Direct3D feature. It was 4 in 1.7.47, I changed to 128 using the same framework developed in 1.7.47. It may potentially fail on some graphic cards due to large number of uniforms in vertex shader generated. Besides the transfer of those uniforms may probably be optimized not to call glUniformMatrix for every matrix when only one or few has changed. -- 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 133

[Bug 46206] New: Altium Designer 17 account sign in fails as of 3.19
by wine-bugs＠winehq.org 21 Feb '25

21 Feb '25

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 21 Feb '25

21 Feb '25

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 49167] New: Wine staging 5.8 not available on macos download page
by WineHQ Bugzilla 18 Feb '25

18 Feb '25

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 17 Feb '25

17 Feb '25

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 30111] New: Crysis 2 ingame crashes
by wine-bugs＠winehq.org 16 Feb '25

16 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=30111 Bug #: 30111 Summary: Crysis 2 ingame crashes Product: Wine Version: 1.4-rc6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: christian.frank(a)gmx.de Classification: Unclassified Hi Guys, after getting the crysis2 loading issue fixed, i noticed that the game itself runs well, but very very unstable. The game simply crashes. The last i see on the console is (the d3d_texure fixme is repeatedly displayed all the time you play) fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x159925c8 stub! fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x15992338 stub! fixme:faultrep:ReportFault 0x32df20 0x0 stub fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x159925c8 stub! The sound of the game is still running but the process is [defunct]. Any ideas on how to debug this issue ? Any recommend traces ? I also noticed a freeze after a ingame video sequence. Many thanks, Christian -- 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 23

[Bug 21811] New: 3impact tech demo collection crashes on first demo
by wine-bugs＠winehq.org 16 Feb '25

16 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=21811 Summary: 3impact tech demo collection crashes on first demo Product: Wine Version: 1.1.39 Platform: x86 URL: http://www.3impact.com/ OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com http://www.3impact.com/3Impact_Engine/dyruk89b/3impact51_demo.exe is a set of demos showing mannekins flailing about and boulders rolling. Runs great on Vista. It installs fine on Wine. To start the app, do cd ~/".wine/drive_c/Program Files/3impact5demos" wine demos.exe skinnedragdoll.dll The first problem is bug 21790; do 'winetricks vcrun2005' to get past that. The next problem is a crash related to d3dx9_36.D3DXAssembleShaderFromResourceW, roughly bug 12020. Work around this with 'winetricks d3dx9'. The next problem is that full-screen mode doesn't work (bug 21791). Work around this by telling the demo to run in a window. This prompts you to press N, and then crashes after you do, with wine: Unhandled page fault on read access to 0x0000001c at address 0x431c10 (thread 0009), starting debugger... I'll attach a +relay,+seh log. -- 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 45623] New: Audio cracking since 3.13
by wine-bugs＠winehq.org 16 Feb '25

16 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=45623 Bug ID: 45623 Summary: Audio cracking since 3.13 Product: Wine Version: 3.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- Since wine 3.13 version came out, the audio in a game I play (Overwatch) after a while starts to crack a lot. This happens with both winepulse and winealsa driver. This does not happen 3.12 so should probably be marked as regression. -- 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 52

[Bug 33295] New: Vietcong: Connecting to a multiplayer server does not work
by wine-bugs＠winehq.org 16 Feb '25

16 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=33295 Bug #: 33295 Summary: Vietcong: Connecting to a multiplayer server does not work Product: Wine Version: 1.5.26 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sworddragon2(a)aol.com Classification: Unclassified Connecting to any multiplayer server in the server list will result in the phone sound that the connection has failed. Even servers with default maps (and logically compatible versions) does not work. -- 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 6