wine-bugs

wine-bugs@winehq.org

1 participants
159448 discussions

[Bug 52244] New: starcraft2 crashes while loading arcade game e_gfxErrorShaderCompileFailed
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=52244 Bug ID: 52244 Summary: starcraft2 crashes while loading arcade game e_gfxErrorShaderCompileFailed Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- Created attachment 71352 --> https://bugs.winehq.org/attachment.cgi?id=71352 console messages [cedric@cedric ~]$ wine --version wine-6.23 [cedric@cedric ~]$ uname -a Linux cedric 5.15.8-arch1-1 #1 SMP PREEMPT Tue, 14 Dec 2021 12:28:02 +0000 x86_64 GNU/Linux [cedric@cedric ~]$ rm -rf ~/.wine [cedric@cedric ~]$ wineboot [cedric@cedric ~]$ wine ~/.wine-sc2-ok/drive_c/Program\ Files\ $x86$/StarCraft\ II/StarCraft\ II.exe Install battle.net (it finds starcraft2), close click Play choose custom -> arcade. Type in "coop" into the search field, and click on "Wings of liberty coop 1. Liberation day", and click create lobby, and then click "start game". After the countdown, the loading screen shows up, and the progress bar goes about to half full. Then this error dialog shows up: "Starcraft II e_gfxErrorShaderCompileFailed To help us identify the problem, please describe what you were doing when the error occurred. Please use the Report ID below when communicating with Blizzard about the issue. DF97FB56-8356-44A6-A960-5BEA033C44DA [X] Send to Blizzard [Reopen] [Close]" -- 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 44920] New: Starcraft II Arcade Crash during load
by wine-bugs＠winehq.org 24 Nov '25

24 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=44920 Bug ID: 44920 Summary: Starcraft II Arcade Crash during load Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: antonio.e.russo(a)gmail.com Distribution: --- Created attachment 61011 --> https://bugs.winehq.org/attachment.cgi?id=61011 WINEDEBUG=warn+all log of crash (gzipped) Starcraft II is a moving target. After the most recent patch, I was unable to use wine-staging 2.21, which had been working excellently for me. Wine 3.5 has trouble: loading the "Hero Attack 3X" (popular) arcade game, the game crashes. I've attached a "WINEDEBUG=warn+all" log, and can help debug. I checked "use 32-bit version", and I am using a clean prefix. -- 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 59038] New: wow64 mode and Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception.
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59038 Bug ID: 59038 Summary: wow64 mode and Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception. Product: Wine Version: 10.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: info(a)fernandolucas.info Distribution: --- Created attachment 79802 --> http://bugs.winehq.org/attachment.cgi?id=79802 wine console output I am using the new packages for Debian Wine 10.18 - 10.19 with the new wow64 mode. Installing .net 10 after initializing the prefix works well. Additional installations of a previous .net core version or running C:\Program Files\dotnet\dotnet.exe workload install wasm-tools fails with 0150:fixme:crypt:CertAddCertificateLinkToStore (00007FFFFED4B850, 00007FFFFE8A3DF8, 00000004, 0000000000000000): semi-stub Unhandled exception: The type initializer for 'Microsoft.DotNet.Installer.Windows.InstallerBase' threw an exception 0130:fixme:unwind:call_user_apc_dispatcher flags 0x3 are not supported. -- 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 59036] New: Wine-devel 10.19 - 0ld Win95 game Hellbender crashes on setup.exe / auto.exe / Hellbend.exe
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59036 Bug ID: 59036 Summary: Wine-devel 10.19 - 0ld Win95 game Hellbender crashes on setup.exe / auto.exe / Hellbend.exe Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)list.winehq.org Reporter: eick.roberto(a)gmail.com Distribution: --- Created attachment 79798 --> http://bugs.winehq.org/attachment.cgi?id=79798 backtrace bug 1 Old Win95 game (32bit) Hellbender crashes on setup.exe / auto.exe / Hellbend.exe Standard wine folder @ /home/user/.wine Happens persistently, on my Debian Sid x86_64 running Wine-devel 10.19 with the so called Experimental Wow64 mode. Seems to be unable to access file '/usr/src/packages/BUILD/dlls/winmm/waveform.c' Must related to sound, which should start playing but it doesn't, it crashes, after actually drawing/decorating the windows. Attachmed backtrace/details. There's a very strance path it tries to locate the "waveform.c". If I go into /usr/src no "packages" directory nor those subdirectories exist. Maybe it should be looking at a different location. -- 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 59037] New: CLIP Studio Paint 4.10: Application performance issue when selecting a material-based tool from the tool panel
by WineHQ Bugzilla 24 Nov '25

24 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59037 Bug ID: 59037 Summary: CLIP Studio Paint 4.10: Application performance issue when selecting a material-based tool from the tool panel Product: Wine Version: 10.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: fun(a)fefes.co.uk Distribution: --- Created attachment 79801 --> http://bugs.winehq.org/attachment.cgi?id=79801 Terminal log showing the err:sync CSP hangs for about one minute when starting a new session and selecting a material-based tool, for example, a downloaded G-pen material, from the tool panel. Selecting another similar tool will also cause the hang, but as long as you do not switch tool groups, selecting the first material is instant. There is also a lag when first attempting to use the tool on the canvas, and I believe it is likely related, but I am happy to raise a new bug for that behaviour. CSP also hangs for longer when switching tool groups, if that tool group contains at least one tool that uses a material. From what I can gather, this might be related to a thread being locked by another thread, but is then waiting 60 seconds to try again, as seen in lines such as: 0158:err:sync:RtlpWaitForCriticalSection section 0000713087FB7238 "?" wait timed out in thread 0158, blocked by 02b8, retrying (60 sec). In the attached log is just the basic example of selecting a new material. Download link: https://vd.clipstudio.net/clipcontent/paint/app/410/CSP_410w_setup.exe OS & DE: Linux Mint Cinnamon 22.2 Zara Architecture: AMD x86_64 Workarounds utilised: All listed for Clip Studio Paint 4.10 at https://appdb.winehq.org/objectManager.php?sClass=version&iId=42586 except for using wine-stable 10.4 where performance was worse. -- 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 58443] New: x11 'minimized' windows not re-fullscreening (fallout 3 / new vegas)
by WineHQ Bugzilla 23 Nov '25

23 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58443 Bug ID: 58443 Summary: x11 'minimized' windows not re-fullscreening (fallout 3 / new vegas) Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zlice(a)crtdrift.us Distribution: --- c67bfdbeba1860c891e53c64379f5e86d8e8b664 / https://gitlab.winehq.org/wine/wine/-/commit/c67bfdbeba1860c891e53c64379f5e… reading the title of the mr makes sense, however this completely breaks fullscreen for fallout 3 and new vegas, and im sure other older games as mentioned https://bugs.winehq.org/show_bug.cgi?id=58442 - there have been a lot of fullscreen/focus/window bugs so it's hard to tell what all is what i spent a bunch of time to just bisect so i'll have to look for what is going on tomorrow -- 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 33

[Bug 56447] New: PlayOnline Viewer: The "splash screen" is blank/grey without its image.
by WineHQ Bugzilla 23 Nov '25

23 Nov '25

https://bugs.winehq.org/show_bug.cgi?id=56447 Bug ID: 56447 Summary: PlayOnline Viewer: The "splash screen" is blank/grey without its image. Product: Wine Version: 9.4 Hardware: x86-64 URL: https://web.archive.org/web/20210810150839/http://www. playonline.com/ff11eu/download/media/install_win.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Distribution: Gentoo This is a very old one, but as far as I can tell, not reported until now (aside from some side-mentions). PlayOnline Viewer, which is used to launch Final Fantasy XI Online, has a blank/grey window for its "splash screen". It has been working in Wine Staging for some time. Not sure if related, but comparing the logging between runs, each of these show up twice with Vanilla but only once with Staging: err:d3d:wined3d_fence_wait glClientWaitSync returned 0x911b. err:d3d:wined3d_context_gl_wait_command_fence Failed to wait for command fence with id 0x1, ret 0x4. err:d3d:wined3d_fence_wait glClientWaitSync returned 0x911b. err:d3d:wined3d_context_gl_wait_command_fence Failed to wait for command fence with id 0x2, ret 0x4. -- 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 58833] New: PlayOnline Viewer: Excessive virtual memory size possibly leading into a crash.
by WineHQ Bugzilla 23 Nov '25

23 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58833 Bug ID: 58833 Summary: PlayOnline Viewer: Excessive virtual memory size possibly leading into a crash. Product: Wine Version: unspecified Hardware: x86-64 URL: https://web.archive.org/web/20210810150839/http://www. playonline.com/ff11eu/download/media/install_win.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Regression SHA1: 63e6cfa106a0b12351e8d01eb5bfefd925c3a74e Distribution: Gentoo After 63e6cfa106a [1] which fixes bug 58812 [2], the PlayOnline Viewer / Final Fantasy XI Online use an excessive amount of virtual memory space, leading into a crash with a debug build of Wine. Non-debug builds also show the problem, but so far have avoided crashing (virtual memory size still gets over 4 G though). Without the mentioned commit, the virtual memory usage goes like this on 'top', in stages. PlayOnline Viewer before log-in: 3343040 Final Fantasy XI started, in the first screen before title: 3401136 Title screen: 3421604 Back to PlayOnline Viewer from Final Fantasy XI: 3390496 Now the same with the commit applied: 3828208 3987620 4015256 4027220 Thank you! 1. https://gitlab.winehq.org/wine/wine/-/commit/63e6cfa106a0b12351e8d01eb5bfef… 2. https://bugs.winehq.org/show_bug.cgi?id=58812 -- 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 59035] New: Wrong default printer with lpoptions set
by WineHQ Bugzilla 23 Nov '25

23 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=59035 Bug ID: 59035 Summary: Wrong default printer with lpoptions set Product: Wine Version: 9.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: dpat(a)syn-net.org Distribution: --- Created attachment 79791 --> http://bugs.winehq.org/attachment.cgi?id=79791 Wine Log with lpoptions set (wrong default printer) I am running Linux Mint Debian Edition 6 (LMDE6 based on Debian/bookworm) with a Cinnamon DE and have the following printers configured: user@LMDE6 ~ % groups user users % lpstat -v device for Brother_MFC_9332CDW: implicitclass://Brother_MFC_9332CDW/ device for HP_OfficeJet_Pro_7740_series_5940AF: implicitclass://HP_OfficeJet_Pro_7740_series_5940AF/ device for Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511: implicitclass://Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511/ A server default printer is set: % lpstat -d system default destination: Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511 And I have the following `~/.cups/lpoptions` file: % cat .cups/lpoptions Dest Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511 When calling notepad with Wine, the wrong default printer is shown (preselected) (in my case the Brother_MFC_9332CDW) in the print options (File: Print...): % WINEDEBUG=+winspool,+tid,+pid,+process,+commdlg wine notepad 2>&1 | tee wine-lpoptions-set.log If I delete the `~/.cups/lpoptions` file, the correct default printer is shown (preselected) (Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511): % WINEDEBUG=+winspool,+tid,+pid,+process,+commdlg wine notepad 2>&1 | tee wine-lpoptions-unset.log I could not figure out who, what or why did create and set the option in `~/.cups/lpoptions`, but I know the Samsung printer was replaced and CUPS automatically detected the new printer and switched the default printer (to the Brother) at some time before. I assume the user did try to change the default printer withing the GUI, but maybe ended up changing the lpoptions file? I later changed the system default printer (from Brother to Samsung) and noticed this problem with Wine. I am not a CUPS expert, but as far I could research ``Dest Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511`` itself looks like an invalid or at least incomplete option. Nevertheless, this should not have an effect on an application in Wine. I am on Wine version wine-9.19 and can not upgrade to a new version as this version is the latest version I was able to run Access Runtime 2010 (where I actually need the correct default printer to be set). P.s. I only can add one attachment (wine-lpoptions-set.log), if you need wine-lpoptions-unset.log for comparison, I can upload it separately as well. The most striking change I could identify is: 0118:011c:trace:winspool:SetDefaultPrinterW (L"Brother_MFC_9332CDW") vs 0118:011c:trace:winspool:SetDefaultPrinterW (L"Samsung_M332x_382x_402x_Series_SEC30CDA7C6D511") I can not see why the other printer was chosen. -- 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 58880] New: Winecfg in wine 10.17 can not create controls(buttons,links ...) in some configurations
by WineHQ Bugzilla 23 Nov '25

23 Nov '25

http://bugs.winehq.org/show_bug.cgi?id=58880 Bug ID: 58880 Summary: Winecfg in wine 10.17 can not create controls(buttons,links ...) in some configurations Product: Wine Version: 10.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: galdralag(a)bk.ru Distribution: --- Created attachment 79542 --> http://bugs.winehq.org/attachment.cgi?id=79542 Running winecfg with WINEDEBUG=warn+all on WINEPREFIX from previous wine version When wine 10.17 compiled not in wow64 mode can't create controls (buttons,links). So winecfg is not working on WINEPREFIX'es from previous versions. Running winecfg with WINEDEBUG=warn+all shows error: 0124:warn:dialog:DIALOG_CreateControls32 control L"Button" L"OK" creation failed When creating winecfg new WINEPREFIX it shows window but exits when switching to "About" tab with error: 0120:warn:dialog:DIALOG_CreateControls32 control L"SysLink" L"<a href=\"https://www.winehq.org\">https://www.winehq.org</a>" creation failed After some investigations I found that problem in comctl32 and new component comctl32_v6 that appeared in 10.17. When I replace comctl32 from 10.16 all works as earlier. When wine compiled in wow64 mode winecfg shows main window and switching on About tab also ok. -- 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

Jump to page:

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