wine-bugs August 2025

wine-bugs@winehq.org

1 participants
376 discussions

[Bug 58635] New: CapCut crashes upon launch
by WineHQ Bugzilla 12 Sep '25

12 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58635 Bug ID: 58635 Summary: CapCut crashes upon launch 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: ihatemylife0025(a)gmail.com Distribution: --- Created attachment 79192 --> http://bugs.winehq.org/attachment.cgi?id=79192 Logs from running CapCut on a new wineprefix I've tried every workaround I could find but CapCut (version 6.9.0, from here: https://lf16-capcut.faceulv.com/obj/capcutpc-packages-us/packages/CapCut_6_…) crashes ~10 seconds from launch. Things I've tried: Installing on a Windows PC and copying the files. No difference. Enabling DXVK. No difference. Using the experimental xe driver for my GPU. No difference. Creating a new prefix. No difference Using the stable 10.0 version. No difference Using CapCut beta version 7.0.0. No difference Installing corefonts with winetricks. No difference I'm using wine version 10.13 from the official fedora 42 repository GPU: 0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) Subsystem: Lenovo Device 3f9c Kernel driver in use: i915 Kernel modules: i915, xe CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 (8) @ 4.20 GHz RAM: 20GB (16+4) DDR4 3200mhz Laptop Model: 82H8 (IdeaPad 3 15ITL6) Kernel Version: Linux 6.15.10-200.fc42.x86_64 Distribution: Fedora 42 KDE Plasma Edition -- 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 56278] New: wayland: dropdowns is rendered as toplevel
by WineHQ Bugzilla 12 Sep '25

12 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=56278 Bug ID: 56278 Summary: wayland: dropdowns is rendered as toplevel Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hugo(a)whynothugo.nl Distribution: --- When using the wayland driver, dropdown menus are rendered as their own toplevel windows. On tiling window managers (e.g.: swaywm), this results in it being tiled just like any other window. I can't imagine that they would be placed correctly on stacking window managers either. I confirmed with lswt that dropdowns are effectively rendered as toplevels. An xdg_popup should be used here instead: https://wayland.app/protocols/xdg-shell#xdg_popup The weirdness in behaviour can be reproduced with: - wine reg.exe add HKCU\\Software\\Wine\\Drivers /v Graphics /d wayland - winecfg - Go to the desktop integration tab and click on any dropdown -- 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 58503] New: Mouse cursor vanishes when using winewayland
by WineHQ Bugzilla 12 Sep '25

12 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58503 Bug ID: 58503 Summary: Mouse cursor vanishes when using winewayland Product: Wine Version: 10.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: sutupud(a)yahoo.com Distribution: --- Since the cursor changes on winewayland in wine 10.12, I see a regression when playing Saints Row 3 Remastered (GOG). After some time in game, the mouse cursor no longer appears when switching to the menu. When that happens, the log is filled with: 0024:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash [... repeated ~100 times ...] 0024:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash 0024:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash 0024:err:waylanddrv:wayland_pointer_update_cursor_buffer Failed to get icon info for cursor=0xa70076 0024:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash 0024:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash 0024:err:waylanddrv:wayland_pointer_update_cursor_buffer Failed to get icon info for cursor=0xa70076 0024:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash 0024:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash 0024:err:waylanddrv:wayland_pointer_update_cursor_buffer Failed to get icon info for cursor=0xa70076 0024:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash 0024:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash [... keeps repeating ...] The game normally switches between hidden and visible mouse cursor when accessing the menu or in-game phone screen. Except from that the game keeps running, just without visible mouse cursor. It doesn't trigger immediately, which makes testing not so easy. Most of the time it runs fine for something between half an hour and an hour. For that reason I can't say if other applcations are affected too, since I didn't test anything else long enough. It did not happen in wine 10.11, and I could not reproduce it after reverting https://gitlab.winehq.org/wine/wine/-/commit/6a9df1f4c5a8448f426ba3454faf25… -- 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 11

[Bug 57444] New: A old game Exertus darkness approaches unable to run under wine wow64
by WineHQ Bugzilla 12 Sep '25

12 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=57444 Bug ID: 57444 Summary: A old game Exertus darkness approaches unable to run under wine wow64 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436.tw(a)gmail.com Distribution: --- Created attachment 77440 --> https://bugs.winehq.org/attachment.cgi?id=77440 Log from wine wow64 Exertus darkness approaches is a very old game. It was able to play even with virtualbox, but unable to run under wow64 env Ubuntu 20.04 wine lastest master -- 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 32

[Bug 58513] New: Wine 10.9 completely broke (LGA775 Core2Quad)
by WineHQ Bugzilla 12 Sep '25

12 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58513 Bug ID: 58513 Summary: Wine 10.9 completely broke (LGA775 Core2Quad) Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xeroxslayer(a)proton.me Distribution: --- I have no other way to describe it except this. Everything was working fine up until Wine 10.8, then I upgrade to Wine 10.9 on Void Linux, and it doesn't work at all any more. There are more details in this issue on GitHub. There is just way too much info to paste here. https://github.com/void-linux/void-packages/issues/55697 Basically, it just doesn't work at all. You run `winecfg` or any other software and this is what you get. ``` 002c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x6fffffc4c133 0034:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x6fffffc4c133 003c:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x6fffffc4c133 ``` Nothing works. This happens, and then Wine quietly exits. From what little I understoo, basically, it can't locate binaries. The binaries are there, at that location, it just doesn't see them... or can't load them, IDK. You can find more relevant info in this comment, with some debug flags enabled. https://github.com/void-linux/void-packages/issues/55697#issuecomment-29902… I do have to note that Wine past 10.8 (>=10.9) does work on other rigs I have, newer ones, but this particular rig is an LGA775 Core2Quad. Now, I know that Wine is mostly focused towards gaming and gamers, but there are people out there that use it for simple things as well, like Winamp and similar things, and we really don't need brand new hardware to do that. In fact, this is my workshop rig and I basically just need it to browse some things on the web (still performs OKish regarding that) and maybe open a few documents, an IC programmer from time to time, but that's about it. So, this rig still suits my needs just fine. I tried scrubbing the volume, check for errors, nothing, everything is peachy, no corruption problems whatsoever. On Void's side, there are literally no changes in the template, except bumping up versions, hashes and removing `libOSMesa` as a dependency (which is depreciated, found that out later on), but I even tried adding `libOSMesa` as a dependency and building it like that, no changes whatsoever, it's still completely broken. There are way too many commits between 10.8 and 10.9, and in all honesty, I wouldn't even know where to start looking (I presume something to do with CPU, but, I'm just guessing here), so if someone could shed some light, I would gladly test. -- 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 25

[Bug 58027] New: trivial use of Win32 GNU make failes with Wine 10.x but not with Wine 9.0
by WineHQ Bugzilla 12 Sep '25

12 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=58027 Bug ID: 58027 Summary: trivial use of Win32 GNU make failes with Wine 10.x but not with Wine 9.0 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: dl.soluz(a)gmx.net Distribution: --- Created attachment 78286 --> https://bugs.winehq.org/attachment.cgi?id=78286 contains the specific make.exe (with MD5, and source-infos)+makefile and scenarios its a super simple makefile that does nothing more then clean: del *.not_existing_at_all and make fails to run the del command on 10.x Wine versions but works on Wine 9.0 i created a git-repo with the make.exe (with MD5) a makefile and a clear description whats happening - in short Wine 10.x breaks someway the del command run the repo: https://github.com/LowLevelMahn/bug_repo0 (i also attached the 3 files of the repo as zip) i don't know if that is a real Wine bug but its strange that is does not happen with a older Wine version (tested only 9.0 so far) tested with up-to-date Ubuntu 24.10 (up-to-date) + sudo apt install wine32 => wine 9.0 up-to-date WSL2/SUSE Tumbleweed + sudo zypper install wine => wine 10.0 up-to-date Fedora 42 (Beta) + sudo dnf install wine32 => wine 10.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.

1 12

[Bug 57912] New: cmd: not every ( is a command grouping
by WineHQ Bugzilla 12 Sep '25

12 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=57912 Bug ID: 57912 Summary: cmd: not every ( is a command grouping Product: Wine Version: 10.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: blubban(a)gmail.com Distribution: --- @echo off if 1==2 ( echo(1 xif 1==2 ( echo 2 ) echo 3)) echo 4 Expected (win10): 3)) 4 Actual (wine 10.2): Syntax error: unexpected ( 4 Oddly enough, it seems that every ) is, in fact, a command grouping. @echo off if 1==2 ( echo () echo 1 ) echo 2 Expected (win10): 1 2 Actual (wine 10.2): Syntax error: unexpected ( 2 Reduced from update.bat in https://www.smwcentral.net/?p=section&a=details&id=33546 -- 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 2

[Bug 58636] New: CapCut installer fails: CreateFileW with FILE_ATTRIBUTE_DIRECTORY | FILE_FLAG_BACKUP_SEMANTICS | FILE_FLAG_POSIX_SEMANTICS should create a directory instesd of a file.
by WineHQ Bugzilla 12 Sep '25

12 Sep '25

http://bugs.winehq.org/show_bug.cgi?id=58636 Bug ID: 58636 Summary: CapCut installer fails: CreateFileW with FILE_ATTRIBUTE_DIRECTORY | FILE_FLAG_BACKUP_SEMANTICS | FILE_FLAG_POSIX_SEMANTICS should create a directory instesd of a file. Product: Wine Version: 10.13 Hardware: x86-64 URL: https://lf16-capcut.faceulv.com/obj/capcutpc-packages- us/packages/CapCut_6_9_0_2786_capcutpc_0_creatortool.e xe OS: Linux Status: NEW Keywords: download, source Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian I tried the installer from bugreport https://bugs.winehq.org/show_bug.cgi?id=58635 but it fails instantly with a error messagebox. I think I managed to track down the bug: The installer does: KERNEL32.CreateFileW(0012f4c4 L"C:\\users\\louis\\AppData\\Local\\\CapCut",00000001,00000003,00000000,00000001,03000010,00000000) Then an empty file "CapCut" is present in Appdata\Local\ dir. After that it tries to create L"C:\\users\\louis\\AppData\\Local\\CapCut\\User Data" and L"C:\\users\\louis\\AppData\\Local\\CapCut\\User Data\\Log" in which Log is a file. This all fails as a file CapCut is already present. Manual workaround to fool the installer: mkdir ~/.wine/drive_c/users/**/AppData/Local/CapCut before you start the installer, then it won't crash. Apparently on windows one can create a directory with CreateFile with the flags used by the installer; below is a simple test program I tested on windows and that creates a directory: #include <windows.h> #include <stdio.h> #include <shlwapi.h> // compile: x86_64-w64-mingw32-gcc a.c -lshlwapi int main() { char path[] = "c:\\log"; HANDLE h = CreateFileA( path, GENERIC_READ | GENERIC_WRITE, 0, NULL, CREATE_NEW, FILE_ATTRIBUTE_DIRECTORY | FILE_FLAG_BACKUP_SEMANTICS | FILE_FLAG_POSIX_SEMANTICS , // 0x03000010, NULL); if (h == INVALID_HANDLE_VALUE) { DWORD err = GetLastError(); printf("err %d\n", err); return 1; } printf("%p\n", h); BOOL ret = PathIsDirectoryA(path); printf("PathIsDirectoryA returned %d\n",ret); return 0; } Output on windows: 00000000000000c0 PathIsDirectoryA returned 16 Output on wine: 000000000000005c PathIsDirectoryA returned 0 -- 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 57913] New: cmd: echo(abc is misparsed
by WineHQ Bugzilla 12 Sep '25

12 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=57913 Bug ID: 57913 Summary: cmd: echo(abc is misparsed Product: Wine Version: 10.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: blubban(a)gmail.com Distribution: --- @echo off echo 1 echo. echo . echo.2 echo( echo ( echo(3 Expected (win10): 1 . 2 ( 3 Actual (wine 10.2): 1 . 2 ( ( (3 Reduced from update.bat in https://www.smwcentral.net/?p=section&a=details&id=33546 -- 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 57478] New: Commit 1fe64cd59573473160186aa172c4bf5055510cd7 makes Sims 2 black-screen when running with Nvidia 470.256.02 and dxvk 1.10.3
by WineHQ Bugzilla 12 Sep '25

12 Sep '25

https://bugs.winehq.org/show_bug.cgi?id=57478 Bug ID: 57478 Summary: Commit 1fe64cd59573473160186aa172c4bf5055510cd7 makes Sims 2 black-screen when running with Nvidia 470.256.02 and dxvk 1.10.3 Product: Wine Version: 9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: dkk089(a)gmail.com Distribution: --- Said commit makes Sims 2 launch to a black screen. Everything else works and it seems like the actual graphical content is just not output to the screen somehow : music is playing in the background and you can see the mouse cursor changing its symbol if you move it around (hovering over a text field). I saw this with Nvidia 470.256.02 and GeForce GT 645M. However, running on a Radeon RX550 with open source drivers is just fine. dxvk was 1.10.3 during both runs. Bisecting leads to 1fe64cd59573473160186aa172c4bf5055510cd7 and reverting this commit from master makes everything work okay again. -- 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 18

← Newer
1
...
4
5
6
7
8
9
10
...
38
Older →

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 August 2025