August 2022 - Wine-Bugs - list.winehq.org

[Bug 40500] New: Scrap Mechanic : Unable to launch
by wine-bugs＠winehq.org Dec. 24, 2025

Dec. 24, 2025

https://bugs.winehq.org/show_bug.cgi?id=40500 Bug ID: 40500 Summary: Scrap Mechanic : Unable to launch Product: Wine Version: 1.9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: arionrina(a)verizon.net Distribution: --- Created attachment 54281 --> https://bugs.winehq.org/attachment.cgi?id=54281 Crash log Scrap Mechanic doesn't open up the first window, 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.

3 24

[Bug 48023] New: Visual Studio 2019 not starting
by WineHQ Bugzilla Dec. 24, 2025

Dec. 24, 2025

https://bugs.winehq.org/show_bug.cgi?id=48023 Bug ID: 48023 Summary: Visual Studio 2019 not starting Product: Wine Version: 4.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- Created attachment 65561 --> https://bugs.winehq.org/attachment.cgi?id=65561 Hack for RegLoadAppKey After https://bugs.winehq.org/show_bug.cgi?id=47626 just out of curiosity I tried running Visual Studio: winetricks corefonts dotnet472 msxml6 and applied the attached patch/hack. Result: splash screen is shown and then welcome screen is displayed. But after clicking "Not now, maybe later" it halts with: Application: devenv.exe Framework Version: v4.0.30319 Description: The application requested process termination through System.Environment.FailFast(string message). Message: Failed to schedule time on the UI thread. A continuation would never execute. It crashes much earlier without the patch/hack as it cannot bind binary registry file and read/create registry keys. -- 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 40

[Bug 46523] New: GTA / Grand Theft Auto IV (1.0.7.0) crashes under wine 4.0, works OK under 3.0.4
by wine-bugs＠winehq.org Dec. 23, 2025

Dec. 23, 2025

https://bugs.winehq.org/show_bug.cgi?id=46523 Bug ID: 46523 Summary: GTA / Grand Theft Auto IV (1.0.7.0) crashes under wine 4.0, works OK under 3.0.4 Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dmayr.dev(a)gmail.com Distribution: --- Created attachment 63380 --> https://bugs.winehq.org/attachment.cgi?id=63380 GTA IV backtrace GTA / Grand Theft Auto IV (1.0.7.0): it gets past the intro screen (R* logo), but after pressing "Start", it begins loading data while showing the game characters loading screen, and crashes halfway, showing a backtrace window. It works OK under wine 3.0.4. All libraries are internal, except for MS VC++ 2005 redistributable. No wine prefix options nor 'export' flags. ThinkPad T410s Processor: Intel i5 (1st-gen), quad-core 2.53Mhz Memory: 4Gb RAM OS: Ubuntu 18.04 / elementaryOS Juno Graphics: NVidia NVS3100M (304.107 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.

3 5

[Bug 46776] New: Bioshock crashing on start [REGRESSION]
by wine-bugs＠winehq.org Dec. 21, 2025

Dec. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=46776 Bug ID: 46776 Summary: Bioshock crashing on start [REGRESSION] Product: Wine Version: 4.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: timofeevsv1989(a)gmail.com Distribution: --- Created attachment 63790 --> https://bugs.winehq.org/attachment.cgi?id=63790 Bioshock crash. Wine console output Bioshock 1/2 and it's remasters crashing on start -- 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 1

[Bug 43485] New: Regression bug: Bricscad v15: Drop-down lists are not switchable
by wine-bugs＠winehq.org Dec. 21, 2025

Dec. 21, 2025

https://bugs.winehq.org/show_bug.cgi?id=43485 Bug ID: 43485 Summary: Regression bug: Bricscad v15: Drop-down lists are not switchable Product: Wine Version: 2.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tolikk91(a)yandex.ru Distribution: --- Created attachment 58866 --> https://bugs.winehq.org/attachment.cgi?id=58866 screenshot Drop-down lists are not switchable, This appeared in version 2,13 and remains relevant for version 2,14 -- 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 2

[Bug 50381] New: AIMP (4.70 build 2236) window cannot be moved in Ubuntu MATE 20.04 and Linux Mint 20.0 Cinnamon/MATE
by WineHQ Bugzilla Dec. 20, 2025

Dec. 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=50381 Bug ID: 50381 Summary: AIMP (4.70 build 2236) window cannot be moved in Ubuntu MATE 20.04 and Linux Mint 20.0 Cinnamon/MATE Product: Wine-staging Version: 6.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 93.duke.xperia(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- The AIMP (4.70 build 2236) window cannot be moved to Ubuntu MATE 20.04 and Linux Mint 20.0 Cinnamon / MATE. When you try to re-move by the window manager MATE, the window is moved but then returned to its previous position. Also, the window is in the mode - on top of all windows. Tested on Ubuntu 20.04 / Ubuntu MATE 20.04 / Linux Mint 20.0 Cinnamon/MATE/Xfce / KDE neon 5.20 distributions - this problem only occurs on Ubuntu MATE 20.04 and Linux Mint 20.0 Cinnamon / MATE on Xfce drag and drop works and other DEs too. AIMP v4.70 build 2236 --> https://www.aimp.ru/?do=download&os=windows -- 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 27

[Bug 44821] New: Gothic 1 inventory objects not rendered
by wine-bugs＠winehq.org Dec. 20, 2025

Dec. 20, 2025

https://bugs.winehq.org/show_bug.cgi?id=44821 Bug ID: 44821 Summary: Gothic 1 inventory objects not rendered Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: w1t3sc4(a)cybergal.com Distribution: --- Created attachment 60854 --> https://bugs.winehq.org/attachment.cgi?id=60854 Inventory objects are not rendered. Object icons in the inventory are not rendered (screenshot). This bug was absent in Wine 3.1, but appears in Wine 3.3 and 3.4. -- 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.

3 15

[Bug 13273] New: Wine does not remember disk labels set through winecfg
by wine-bugs＠winehq.org Dec. 20, 2025

Dec. 20, 2025

http://bugs.winehq.org/show_bug.cgi?id=13273 Summary: Wine does not remember disk labels set through winecfg Product: Wine Version: 1.0-rc1 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ccf2egd02(a)sneakemail.com Wine does not seem to remember disk labels or serial numbers when set via winecfg. Steps to reproduce: 1) create a disk entry in ~/.wine/dosdevices ln -s /someplace_with_CD_image ~/.wine/dosdevices/q\: 2) run winecfg, select disk tab. 3) Select q: 4) Show advanced 5) Set to manual setup, disk label to "SOMETHING", disk ID to "FEEDBE" 6) APPLY 7) verify data by selecting some other drive, then re-selecting q: 8) quit winecfg 9) Restart winecfg and reselect the disk tab. Reselect q: Expected results Disk label should be "SOMETHING", id should be "FEEDBE" Actual results Disk label unset, disk ID 0 -- 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.

3 25

[Bug 47624] New: Application crashes in socket communication (Regression)
by wine-bugs＠winehq.org Dec. 19, 2025

Dec. 19, 2025

https://bugs.winehq.org/show_bug.cgi?id=47624 Bug ID: 47624 Summary: Application crashes in socket communication (Regression) Product: Wine Version: 4.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mnemotron(a)gmail.com Distribution: --- Created attachment 65058 --> https://bugs.winehq.org/attachment.cgi?id=65058 Wine debug log +relay,+ntdll,+winsock For several years we've been using Wine 1.7.18 on Lubuntu 13 (Linux 3.11.10) with a proprietary 32-bit Windows application programmed in Delphi. It is installed on small embedded PCs with AMD Geode LX processors at 500 MHz and 1 GB RAM and we have about 100 of these machines. After upgrading a test machine to newer Linux distributions and Wine 4.x the application crashes in its network functions. When booting the same hard drive via USB on a modern PC everything works, so the bug might be driver related. (But it works on the older kernel!) The basic error is this (Wine 4.13 devel): 340728.035:0008:0009:Ret KERNEL32.GetProcAddress() retval=7db174ac ret=0041615c 340728.035:0008:0009:Call ws2_32.shutdown(000000dc,00000001) ret=0067ba05 340728.035:0008:0009:Call ntdll.wine_server_handle_to_fd(000000dc,00000000,0033fac8,0033fac4) ret=7db246cb 340728.035:0008:0009:Ret ntdll.wine_server_handle_to_fd() retval=00000000 ret=7db246cb 340728.035:0008:0009:trace:winsock:WS_shutdown socket 00dc, how 0x1, options 0x0 340728.035:0008:0009:trace:winsock:WS2_register_async_shutdown socket 00dc type 2 340728.036:0008:0009:Call ntdll.RtlAllocateHeap(00110000,00000000,00000018) ret=7db1a77a 340728.036:0008:0009:Ret ntdll.RtlAllocateHeap() retval=001be6c0 ret=7db1a77a 340728.036:0008:0009:err:seh:setup_exception_record nested exception on signal stack in thread 0009 eip 7bca93b9 esp 7ffdbae0 stack 0x242000-0x340000 Winedbg does not work. When attaching to the Windows process, the application crashes and Winedbg says "Can't attach to process ... Error 5". Running the application in Winedbg directly generates the above error message plus "Process of pid=xxxx has terminated". There is no backtrace, the thread dies completely. I have tried various Linux distributions using 4.x kernels (Bodhi Linux 5, Linux Mint Debian Edition 3, Debian 9.9, Debian 10, Ubuntu 16.04) and also tried Wine 2.0.2, which is the oldest available binary package, and everytime the above error occurs. Building a custom Linux kernel for the machine also didn't change anything. Trying to build Wine 1.7.18 on Debian 10 resulted in several compile time errors that I am not able to fix, so I am stuck with available binary packages. Debugging and changing the Windows application itself managed to move the crash from the first network connect to when the application is shutdown. Only widely available network component libraries for Delphi were used (Indy and ICS), there is no self-developed net code. So, the same Windows executable works with Wine 1.7.13 on Linux 3.11, but it crashes in Wine 4.x (I tried several packages from Ubuntu and Debian from winehq) on modern 4.x Linux kernels on this machine. Any ideas? I'm ready to provide more needed info. Thomas -- 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 45483] New: Installation of the DirectX 8.1 SDK fails due to msi custom action failure
by wine-bugs＠winehq.org Dec. 19, 2025

Dec. 19, 2025

https://bugs.winehq.org/show_bug.cgi?id=45483 Bug ID: 45483 Summary: Installation of the DirectX 8.1 SDK fails due to msi custom action failure Product: Wine Version: 3.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: mstefani(a)winehq.org Distribution: --- Created attachment 61838 --> https://bugs.winehq.org/attachment.cgi?id=61838 +msi,+msiexec,+pid debug output The DirectX 8.1 SDK fails to install due msi custom action errors: 006b:006c:err:msiexec:custom_action_server Failed to create custom action server pipe: 231 setup.exe shows "Error: -1603 Fatal error during installation." Steps to reproduce: DX81b_SDK.exe with SHA1: 221c60334da54e8e670741e7090e51255ad0284c MD5: 0ef4637b05b77ae8f75d58e17f0e7d6d DX81b_SDK.exe is a self extracting zip file. cd to the extracted directory and run: wine DXF/setup.exe (Changing to the DXF directory and then wine setup.exe makes no difference). Go through the steps and during the install at 0% a message box with the above error pops up. I'm attaching the +msi,+msiexec,+pid output -- 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.

4 10