- Wine-Bugs - list.winehq.org

[Bug 57310] New: wineboot failed to initialize a wine prefix
by WineHQ Bugzilla Feb. 21, 2025

Feb. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=57310 Bug ID: 57310 Summary: wineboot failed to initialize a wine prefix Product: Wine Version: 0.9.17. Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rmkk(a)atlas.cz This issue is relevant for INTEL MACs only, ARM MACs are working fine. Starting wine without existing wineprefix should create a brand new .wine and initialize it - this is failing on Intel Macs. The last working version I found is wine-staging-9.1-osx64.tar.xz, all newer ones are failing including the latest wine-staging-9.17-osx64.tar.xz. So after version 9.1 something has to change. It is easy to reproduce ... local(a)Radim--iMac ~ % sw_vers ProductName: macOS ProductVersion: 15.0 BuildVersion: 24A5327a local(a)Radim--iMac ~ % arch i386 local(a)Radim--iMac ~ % rm -rf ~/.wine local(a)Radim--iMac ~ % ~/Downloads/Wine\ Staging.app/Contents/Resources/wine/bin/wineboot wine: created the configuration directory '/Volumes/Data/Radim Home/.wine' wineserver: using server-side synchronization. 0024:err:environ:run_wineboot failed to start wineboot 1 zsh: killed ~/Downloads/Wine\ Staging.app/Contents/Resources/wine/bin/wineboot -- 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 57795] New: cmd lacks support for right-to-left handle redirection (2<&1)
by WineHQ Bugzilla Feb. 21, 2025

Feb. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=57795 Bug ID: 57795 Summary: cmd lacks support for right-to-left handle redirection (2<&1) Product: Wine Version: unspecified Hardware: x86-64 URL: https://github.com/curl/curl OS: FreeBSD Status: NEW Keywords: source Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: damjan.jov(a)gmail.com When compiling the Windows version of Curl from Wine + MS Platform SDK, the build breaks when copying the binaries to destination directories, because in https://github.com/curl/curl/blob/2ed232a4e66c7ecb75f1b7fc7623da967857ef04/… (and other places) it does this: @if exist $(LIB_DIROBJ)\$(LIB_NAME_DLL) copy $(LIB_DIROBJ)\$(LIB_NAME_DLL) $(DIRDIST)\bin\ /y >nul 2<&1 That "2<&1" at the end of the line breaks it. Wine's cmd only supports redirections in the opposite direction, like "1>&2". I am working on a patch. -- 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 57787] New: Final Fantasy XI Online crashes with unhandled page fault on launch
by WineHQ Bugzilla Feb. 21, 2025

Feb. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=57787 Bug ID: 57787 Summary: Final Fantasy XI Online crashes with unhandled page fault on launch Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Regression SHA1: 33756286efb9e6b58831b01b9f2ef4d7992a967a Distribution: Gentoo Created attachment 77988 --> https://bugs.winehq.org/attachment.cgi?id=77988 Terminal Output/Backtrace After 33756286efb [1], Final Fantasy XI Online crashes during the "handover" from PlayOnline Viewer to the actual game client. Attached terminal output with 'WINEDEBUG="wbemprox"' and the backtrace. Last tested at 9dbd872a714 [2]. Thank you! 1. https://gitlab.winehq.org/wine/wine/-/commit/33756286efb9e6b58831b01b9f2ef4… 2. https://gitlab.winehq.org/wine/wine/-/commit/9dbd872a714cc5fdbe9d96707d0745… -- 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 56464] New: vbscript: Join on array with "empty" items fails
by WineHQ Bugzilla Feb. 21, 2025

Feb. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=56464 Bug ID: 56464 Summary: vbscript: Join on array with "empty" items fails Product: Wine Version: 9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: francisdb(a)gmail.com Distribution: --- > cat test.vbs Dim u Dim arr, arr1 'first item not empty arr = array("test", u) WScript.Echo "Join arr = " & Join(arr,"") 'first item is empty arr1 = array(u, "test") WScript.Echo "Join arr1 = " & Join(arr1,"") Wine > wine wscript test.vbs 0114:fixme:vbscript:Global_Join 0114:fixme:wscript:ActiveScriptSite_OnScriptError () Windows > cscript test.vbs Microsoft (R) Windows Script Host Version 5.812 Copyright (C) Microsoft Corporation. All rights reserved. Join arr = test Join arr1 = test On a vpinball where wine vbscript is embedded we get a segfault: free(): double free detected in tcache 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 12

[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 7115] Need for Speed III installer fails in Win9X mode, reporting "Could not get 'HardWareKey' value" (active PnP device keys in 'HKEY_DYN_DATA\\Config Manager\\Enum' missing)
by WineHQ Bugzilla Feb. 21, 2025

Feb. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=7115 --- Comment #28 from joaopa <jeremielapuree(a)yahoo.fr> --- Bug still occurs in wine-10.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 0

[Bug 1201] Microsoft Golf 99 (Direct3D game) crashes on startup (IDirect3D::EnumDevices needs to return at least two devices for the requested Direct 3D Version 1)
by WineHQ Bugzilla Feb. 21, 2025

Feb. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=1201 --- Comment #49 from joaopa <jeremielapuree(a)yahoo.fr> --- Bug still occurs with wine-10.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 0

[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 8563] MechWarrior 4: Vengeance fails to start
by WineHQ Bugzilla Feb. 21, 2025

Feb. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=8563 --- Comment #47 from joaopa <jeremielapuree(a)yahoo.fr> --- Working for me with wine-10.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 0

[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