wine-bugs

wine-bugs@winehq.org

1 participants
159121 discussions

[Bug 58731] New: Using newer versions of dgVoodoo2 to play older games fail to initialize.
by WineHQ Bugzilla 25 Sep '25

25 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58731 Bug ID: 58731 Summary: Using newer versions of dgVoodoo2 to play older games fail to initialize. Product: Wine-staging Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nosferatu.arucard.1983(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- This is a year old bug around the Steam and later Lutris gaming community when notice the dgVoodoo2 wrapper after version 2.80 fail to work on Wine, either Proton or Proton-GE or any forks. Since Proton always uses DXVK for Direc3D 11 rendering (the dgVoodoo2 output), it was common to combine dgVoodoo2 with DXVK to wrap old DirectX and 3dfx Glide code to Direct3D 11, leaving DXVK to translate to Vulkan. As the time goes around, Dege was wary the fact that the last version of this own creation is now 2.86.2 at the time of writing and Lutris never update beyond 2.80 or a modded version called 2.8.2 After some testing and a rare game called Montezuma's Return which have a 3dfx version, I discovery that using dgVoodoo2 over Wine's vanilla DirectX 11 implementation also had the same problems like Proton or Wine-GE (modded versions) with DXVK. This old Glide game works with the lastest dgVoodoo2 without problems, while DirectDraw games like Omikron or Carmageddon TDR2000 fail to work using the lastest dgVoodoo2, but older versions worked fine. But the latter games had GPU diagnose tools and a pattern was found. If the dgVoodoo2 wrapper works, then the virtual dgVoodoo DirectX wrapper appears on devices list. If not, it displays the Wine's safe mode software renderer (DirectDraw HAL). Forcing playing the game, makes them crash or running at slowest speeds. After all testing, the issue happens either using DXVK or Wine's DirectX implementation, meaning that the problem should be found on Wine's code. Computers with Mesa drivers at certain games could start dgVoodoo2 2.86.2 on games like Omikron, which means that this open-source drivers code had an unintended workaround to force dgVoodoo2 to work, but this is rare and not always work. The test with Montezuma Return shows that the emulation code from Glide to DirectX works on Wine, along the DirectDraw emulation that work on certain cases. However the real issue is the initialization routine (that was changed) caused this huge regression, and it is not be handled by Wine. -- 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 58729] New: various bugs in Jedi Knight - Dark Forces II Demo (macOS)
by WineHQ Bugzilla 24 Sep '25

24 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58729 Bug ID: 58729 Summary: various bugs in Jedi Knight - Dark Forces II Demo (macOS) Product: Wine Version: 10.14 Hardware: x86-64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cemer99797(a)isorax.com This is a new bug report following my previous bug report (bug# 58156). In the previous bug report, the game Jedi Knight - Dark Forces II Demo could not launch at all on macOS, with the following error: > "err:module:loader_init "smackw32.DLL" failed to initialize, aborting" As of Wine-devel 10.14, this game is now playabale again but only with workaround and caveats. (comments cross-posted as well in bug# 58156) my system: macOS 11 game demo download page (choose Download this File > Agree > Jedi Knight Demo.zip): https://community.pcgamingwiki.com/files/file/1308-jedi-knight-dark-forces-… sha256: 7bc013918cf79879a086a10c27306f2f3511852726f4b4a9fec09668ed221d18 ---- To play the game, you have to launch the JEDI.EXE launcher app (not the JKDEMO.EXE game app) and click "Play Jedi Knight Demo"... After clicking "Play Jedi Knight Demo": 1. the game app will be launched to an all-black fullscreen and tries to change the screen resolution 2. the game app will minimize itself to the macOS Dock after 1 to 3 seconds 3. the same error pop-up as in my first post will show up: > Unable to start the Jedi Knight Demo game program. Try running JK.EXE where you installed the Demo directly. Also make sure you have the latest DirectX drivers installed on your system. Clicking the minimized game app from the macOS Dock (grayscale Jedi icon) will return the game app to fullscreen, with an all-black fullscreen and the intro video music playing in the background. Pressing Esc will skip the all-black intro video and correctly load the main menu and the game is playable! Press the equals key to increase the game viewport to fill the screen. ### NOTES: 1. if you choose "Cutscenes" from the main menu and press OK to play the Splash movie (intro movie), it will now play correctly 2. if you switch out of (Cmd-Tab) and return to the game from: * the all-black intro video (before pressing Esc to skip): the game correclty returns to the all-black intro video * the main menu: the main menu will now be all black, but the sounds still play when clicking your mouse and pressing Esc * the correctly-playing intro video from the Cutscenes menu: the game returns to an all-black intro video, but if you skip it (Esc), the main menu will display correctly * gameplay: the game viewport will be all the way off-screen to the top of the screen, meaning only the bottom 20% of the game can be seen (press the equals key to increase the in-game viewport). If you press Esc the pause menu still appears correctly * the pause menu, activated for the first time from gameplay: the game returns to an all-black pause menu, and pressing Esc returns the game viewport being off-screen to the top as before * the pause menu, activated for a second time from gameplay: the pause menu correctly reappears, but after returning to gameplay, the game viewport is still off to the top of the screen 3. if you close all macOS Terminal windows (which normally exits all wine processes), the game app will still be running, but the error pop-up will be killed. The game can be exited by force-quitting the wine processes in macOS Activity Monitor or Force Quit dialog I also bisected this with Wine-devel 10.12 and 10.13, and they both give the same error as in my first post: > "smackw32.DLL" failed to initialize, aborting so this was fixed in Wine-devel 10.14 I am using the official WineHQ/Gcenx binary from Homebrew/GitHub: https://formulae.brew.sh/cask/wine@devel https://github.com/Gcenx/macOS_Wine_builds/releases/download/10.14/wine-dev… -- 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 58137] New: Installation of WISO MeinGeld is impossible after entering the license key
by WineHQ Bugzilla 24 Sep '25

24 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58137 Bug ID: 58137 Summary: Installation of WISO MeinGeld is impossible after entering the license key Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: guentera(a)gmx.de Distribution: --- Created attachment 78415 --> http://bugs.winehq.org/attachment.cgi?id=78415 Enter the License Key After entering the license key and confirming the licensing conditions, you will be asked to confirm the conditions again and again. Unable to complete the installation. WISO "Mein Geld Professional" is a German finance Software. Follow this link to get a free 30-day trial: https://www.buhl.de/c-j/wiso-meingeld-pro-2025/ Download: https://download.buhl.de/Download/MeinGeld/MG2025/ESD/WISOFinanz2025.exe Wine-Mono and Wine-Gecko must be installed. -- 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 4

[Bug 47135] New: Onenote fails to start: Desktop Experience feature is not installed ( lacking Win32_ServerFeature class from wbemprox)
by wine-bugs＠winehq.org 24 Sep '25

24 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=47135 Bug ID: 47135 Summary: Onenote fails to start: Desktop Experience feature is not installed (lacking Win32_ServerFeature class from wbemprox) Product: Wine Version: 4.7 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Created attachment 64360 --> https://bugs.winehq.org/attachment.cgi?id=64360 hack to start Onenote The relaylog below *** made with ONENOTE (MSOffice 2010) shows problem apparently seems to be in wbemprox, missing Win32_ServerFeature class The attached crappy hack allowed me to start Onenote, and also Onenote from Office365 starts with it. Crappy hack is only to show where the problem is and problably contains several errors, hopefully someone can fix this in proper way (hint at Hans;)). Sidenote: reverting the hack makes Onenote from Office365 run into the bug again, but Onenote from office 2010 now continues happily to start; maybe it sets some registry key once started and the patch is not needed anymore? No idea. 008c:Call KERNEL32.lstrlenA(2e09825c "SELECT Name FROM Win32_ServerFeature") ret=2e0e8fd1 008c:Ret KERNEL32.lstrlenA() retval=00000024 ret=2e0e8fd1 008c:Call KERNEL32.MultiByteToWideChar(00000000,00000000,2e09825c "SELECT Name FROM Win32_ServerFeature",00000025,00000000,00000000) ret=2e0e8fe7 008c:Ret KERNEL32.MultiByteToWideChar() retval=00000025 ret=2e0e8fe7 008c:Call KERNEL32.MultiByteToWideChar(00000000,00000000,2e09825c "SELECT Name FROM Win32_ServerFeature",00000025,0033f9f0,00000025) ret=2e0e9085 008c:Ret KERNEL32.MultiByteToWideChar() retval=00000025 ret=2e0e9085 008c:Call oleaut32.SysAllocString(0033f9f0 L"SELECT Name FROM Win32_ServerFeature") ret=2e0e90bb . . . . 008c:Call user32.MessageBoxW(00000000,0033f6b2 L"OneNote cannot start because the Desktop Experience feature is not installed. Install it in the Windows Control Panel > Prog rams and Features > Turn Windows features on or off.",39835ba4 L"Microsoft Office",00000030) ret=39bb2183 -- 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 12

[Bug 58538] New: d2d_device_context_DrawGeometry Ignoring stroke style => No Circles, only Lines
by WineHQ Bugzilla 24 Sep '25

24 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58538 Bug ID: 58538 Summary: d2d_device_context_DrawGeometry Ignoring stroke style => No Circles, only Lines Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: d.astra(a)yopmail.com Distribution: --- Created attachment 79028 --> http://bugs.winehq.org/attachment.cgi?id=79028 WINEDEBUG=+d2d, Rainmeter 4.5.23 I'm using Rainmeter 4.5.23 with Wine 10.12-staging and everything, which should be round or a circle, is either not drawn at all or more of a hexagonal shape. Main error output in the console: 013c:fixme:d2d:d2d_geometry_sink_AddArc iface 0000000002E13CF8, arc 000000000011EC80 stub! 013c:fixme:d2d:d2d_geometry_sink_AddArc iface 0000000002E13CF8, arc 000000000011EC80 stub! 013c:fixme:d2d:d2d_path_geometry_GetWidenedBounds iface 0000000002E13BE0, stroke_width 0.00000000e+00, stroke_style 0000000000000000, transform 0000000000000000, tolerance 2.50000000e-01, bounds 000000000011EA40 stub! Further output with WINEDEBUG=+d2d as attachement -- 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 58665] New: cmd incorrectly wraps text containing ANSI escape sequences
by WineHQ Bugzilla 24 Sep '25

24 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58665 Bug ID: 58665 Summary: cmd incorrectly wraps text containing ANSI escape sequences Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: forestix(a)gaga.casa Distribution: --- Created attachment 79250 --> http://bugs.winehq.org/attachment.cgi?id=79250 reproducer: should print 3 lines; wine prints 4 lines Wine's cmd.exe prematurely inserts line breaks when a program's output contains non-printable ANSI escape sequences, such as those used to change colors. It looks as though Wine is counting not only the printable characters in the program's output, but also the non-printable ones, and using the total to decide where to insert a line break. Text that fits entirely on one line in a real Windows console is sometimes broken midway through the line, or followed by a blank line that should not be there, when run in an xterm using Wine. I am attaching a batch file that reproduces the problem. It should print 3 lines. The second line is identical to the others with the addition of some non-printable escape sequences. These characters should either occupy no width in the terminal (making the line length match the others) or be rendered as visible placeholder characters (as older Windows versions do). To see Wine handling it incorrectly, run it in an 80-column xterm or a similar terminal. Ideally, the output should look like this, with the head of line 2 in red: 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789 In wine, the output looks like this: 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_12 3456789 79 chars _123456789_123456789_123456789_123456789_123456789_123456789_123456789 Bug 49780 is related, but IMHO does not excuse this behavior. Regardless of whether virtual terminal sequences are supported, Wine should either print a character or not count it toward the length of a line when deciding where to wrap it. -- 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 4

[Bug 49780] New: wineconsole reports VT sequence support when it does not
by WineHQ Bugzilla 24 Sep '25

24 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=49780 Bug ID: 49780 Summary: wineconsole reports VT sequence support when it does not Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: magiblot(a)hotmail.com Distribution: --- Created attachment 68092 --> https://bugs.winehq.org/attachment.cgi?id=68092 Demo application to reproduce the issue Wineconsole does not support applications writing Virtual Terminal sequences through the Console API. That's fine. However, when enabling the console ENABLE_VIRTUAL_TERMINAL_PROCESSING mode on stdout with SetConsoleMode, no error is returned, so the application has no way to detect whether VT sequences are supported or not. This is documented in https://docs.microsoft.com/en-us/windows/console/setconsolemode. The port of Turbo Vision at https://github.com/magiblot/tvision is affected by this. When using the Console API, Turbo Vision prefers VT sequences over SetConsoleCursorPosition/SetConsoleTextAttribute for code reusability and performance. Nevertheless, it can fall back to the latter method when SetConsoleMode fails to enable either ENABLE_VIRTUAL_TERMINAL_PROCESSING or DISABLE_NEWLINE_AUTO_RETURN. Since SetConsoleMode does not return error on wineconsole, garbage is shown instead of a colorful interface. STEPS TO REPRODUCE To reproduce the issue on Turbo Vision: (A) - Using the attached 'tvdemo.exe' 1. Run the application on wineconsole. You should see a black-and-white background and escape sequences drawn on the console. 2. Press Alt+F, then D. You should see the command prompt, and the message "VT enabled" at the top, which demonstrates the issue in SetConsoleMode. (B) - Compiling from source code (requires up-to-date CMake and MSVC). 1. Insert the following code after line 63 in source/linux/win32con.cpp (https://github.com/magiblot/tvision/blob/dd4e410e60a34e08053399e346d4ed4e63…): ``` if (supportsVT) cerr << "VT enabled" << endl; else cerr << "VT not enabled: " << GetLastError() << endl; ``` 2. Follow the build instructions at https://github.com/magiblot/tvision/blob/dd4e410e60a34e08053399e346d4ed4e63… 3. Follow the steps in (A). EXPECTED BEHAVIOUR On Windows, support for VT sequences can be disabled by turning on the "Legacy Console" mode. If tvdemo.exe is ran in these conditions, the interface is displayed properly. If entering the command prompt by pressing Alt+F, then D, the message "VT not enabled: 87" is displayed (error 87 stands for ERROR_INVALID_PARAMETER), which is what should be shown on wineconsole as well, since it clearly does not support VT sequences. Thank you! -- 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 58716] New: Camerabag Pro 2025.2 crashes with unhandled exception (unimplemented function propsys.dll.PropVariantToFileTime) on loading a JPEG
by WineHQ Bugzilla 23 Sep '25

23 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58716 Bug ID: 58716 Summary: Camerabag Pro 2025.2 crashes with unhandled exception (unimplemented function propsys.dll.PropVariantToFileTime) on loading a JPEG Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: superian(a)gmail.com Distribution: --- Created attachment 79316 --> http://bugs.winehq.org/attachment.cgi?id=79316 backtrace.txt generated by WINE New installation of WINE development version 10.15 on Linux Mint 22.2 (Ubuntu Noble-based). windowscodecs installed via winetricks (suggested at https://appdb.winehq.org/objectManager.php?sClass=version&iId=31067) then install the program. Installation OK, registration code accepted OK, runs until 'Load Photo/Video' when it crashes with the attached back trace saying: "Unhandled exception: unimplemented function propsys.dll.PropVariantToFileTime called in 64-bit code (0x006fffff3dd817)." -- 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 10

[Bug 58719] New: Wagotabi crashes on wine-10.15.
by WineHQ Bugzilla 23 Sep '25

23 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58719 Bug ID: 58719 Summary: Wagotabi crashes on wine-10.15. Product: Wine Version: 10.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- Created attachment 79320 --> http://bugs.winehq.org/attachment.cgi?id=79320 Console log The game Wagotabi (Steam AppID: 2701720. Uses Unity Engine) doesn't work under wine-10.15. Attempting to start the game in a clean prefix results in the game crashing with a black screen instantly on start up. Installing DXVK into the wine prefix gets the game to show it's company logos, but it then runs into https://bugs.winehq.org/show_bug.cgi?id=49028. Attempting to use -force-vulkan or -force-glcore Unity cmdline args results in the common UnityPlayer error: InitializeEngineGraphics failed. So the game lacks support for any alternative renderers. A demo is available on steam for anyone wanting to try this. Strangely, the game's store page claims it's Steam Deck Verified. So I guess proton is compatible, but I've only tested Wine, so I can't vouch for that claim. Console log attached. -- 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 58605] New: 10.13 - Compile Error
by WineHQ Bugzilla 23 Sep '25

23 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58605 Bug ID: 58605 Summary: 10.13 - Compile Error Product: Wine Version: 10.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jonfarr87(a)gmail.com Distribution: --- Created attachment 79140 --> http://bugs.winehq.org/attachment.cgi?id=79140 Config Log As of the 10.13 release I'm getting the below error. Tried both Vanilla and Staging, same issue. Can confirm the issue is not present with 10.12 i686-w64-mingw32-gcc -c -o dlls/ucrtbase/tests/i386-windows/printf.o dlls/ucrtbase/tests/printf.c -Idlls/ucrtbase/tests -Iinclude -Iinclude/msvcrt \ -D_UCRT -D__WINESRC__ -D__WINE_PE_BUILD -Wall -fno-strict-aliasing -Wdeclaration-after-statement \ -Wempty-body -Wignored-qualifiers -Winit-self -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits \ -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op -ffunction-sections \ -fno-omit-frame-pointer -mpreferred-stack-boundary=2 -gdwarf-4 -fno-builtin -g -O2 dlls/ucrtbase/tests/misc.c: In function ‘test_carg’: dlls/ucrtbase/tests/misc.c:2017:34: error: initializer element is not constant { -INFINITY, INFINITY, M_PI_3_4 }, ^~~~~~~~ dlls/ucrtbase/tests/misc.c:2017:34: note: (near initialization for ‘tests[8].expect’) dlls/ucrtbase/tests/misc.c: In function ‘test_cargf’: dlls/ucrtbase/tests/misc.c:2073:34: error: initializer element is not constant { -INFINITY, INFINITY, M_PI_3_4 }, ^~~~~~~~ dlls/ucrtbase/tests/misc.c:2073:34: note: (near initialization for ‘tests[8].expect’) make: *** [Makefile:191364: dlls/ucrtbase/tests/i386-windows/misc.o] Error 1 make: *** Waiting for unfinished jobs.... -- 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 13

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