June 2025 - Wine-Bugs - list.winehq.org

[Bug 44788] New: Civilization II (v1.02) crash during menus
by wine-bugs＠winehq.org June 18, 2025

June 18, 2025

https://bugs.winehq.org/show_bug.cgi?id=44788 Bug ID: 44788 Summary: Civilization II (v1.02) crash during menus Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: danielalston(a)gmail.com Distribution: --- Created attachment 60814 --> https://bugs.winehq.org/attachment.cgi?id=60814 Backtrace The game will open, the music plays however every few seconds the sound will make an awful corrupt sounding noise (possibly related). The game will usually crash quite quickly. If you're extremely fast you might be able to get in a game and make a couple of moves before the game crashes again. I have similar issues with other 16bit versions of Civilization II. 2.42 patch 2.78 (Fantastic Worlds) -- 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 6

[Bug 45857] New: Incorrect text color (The Longest Journey)
by wine-bugs＠winehq.org June 18, 2025

June 18, 2025

https://bugs.winehq.org/show_bug.cgi?id=45857 Bug ID: 45857 Summary: Incorrect text color (The Longest Journey) Product: Wine Version: 3.16 Hardware: x86-64 URL: https://games.softpedia.com/get/Games-Demo/The-Longest -Journey-161-Demo.shtml OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jhansonxi(a)gmail.com Distribution: Ubuntu Created attachment 62344 --> https://bugs.winehq.org/attachment.cgi?id=62344 Wine screenshot In-game text is outlined in a magenta color. See attached screenshots. Reproduced with demo 161 and full version (GOG.com) build 142. MD5: 6d7f91e0a19513e859775862b2ac43d8 thelongestjourneydemo_english.exe wine-devel 3.16.0~xenial from winehq.org Xbuntu 16.04.5 x86_64 Nvidia GeFOrce GTX 750 Ti, driver version 384.130 -- 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 7

[Bug 53910] New: windows get moved around when dpms blankout happens
by WineHQ Bugzilla June 18, 2025

June 18, 2025

https://bugs.winehq.org/show_bug.cgi?id=53910 Bug ID: 53910 Summary: windows get moved around when dpms blankout happens Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Technically, it's a regression, but not sufficiently significant (for me) to check when it began - I initially thought it was something even more random. Anyway, as the summary says, relatively recently (I'd say within last two months, perhaps less) I've noticed than under some at the time unclear condition, some of the windows get randomly moved around their respective desktops without any of my interaction. For the most part it was only slightly annoying and seemingly random, so I've just lived with it. But today I had an idea and successfully tested it. All that's needed was 'xset dpms force off'. It's also quite generic - can be triggered with notepad and winecfg. My setup is of two monitors, but one of them is quite old and most of the time turned off (that still allows for stumbling upon various quirks of winex11.drv's multi-screen handling). Once 'xset dpms force off' is fully in effect, upon restoring from the blankout the windows get somewhat randomly moved. -- 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 29

[Bug 54801] New: FL Studio Plugin Crashing App
by WineHQ Bugzilla June 17, 2025

June 17, 2025

https://bugs.winehq.org/show_bug.cgi?id=54801 Bug ID: 54801 Summary: FL Studio Plugin Crashing App Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: theenviousone23(a)gmail.com Distribution: --- Whenever I attempt to authorize a specific plugin, it causes the entire application to close down immediately afterwards, and I'm not sure why this is happening. -- 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 58366] New: msvcrt: wassert (L"iface->lpVtbl == &d3d11_buffer_vtbl",L"dlls/d3d11/buffer.c",218)
by WineHQ Bugzilla June 17, 2025

June 17, 2025

http://bugs.winehq.org/show_bug.cgi?id=58366 Bug ID: 58366 Summary: msvcrt: wassert (L"iface->lpVtbl == &d3d11_buffer_vtbl",L"dlls/d3d11/buffer.c",218) Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jesperpedersen.db(a)gmail.com Distribution: --- Created attachment 78767 --> http://bugs.winehq.org/attachment.cgi?id=78767 msvcrt assert Hi, Banished crashes with the attached on 10.10. Let me know if I can provide additional information. Thanks ! Best regards, Jesper -- 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 58380] New: dinput Controllers (i.e. Sony DualSense / DualShock) don't work properly with Ubisoft Games
by WineHQ Bugzilla June 17, 2025

June 17, 2025

http://bugs.winehq.org/show_bug.cgi?id=58380 Bug ID: 58380 Summary: dinput Controllers (i.e. Sony DualSense / DualShock) don't work properly with Ubisoft Games Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: contact(a)jaybmusic.net Distribution: --- Using DirectInput controllers like the Sony Dual Shock or Dual Sense controllers don't work properly in games launched via Ubisoft Connect. Tested with several Wine versions (9.x, 10.x) and several launchers (Steam, Bottles, Lutris). The controller works fine in Ubisoft Connect and can control the surface, also showing the correct icons for buttons, so it is indeed identified as a Sony controller. However, in game it is not properly passed through. In Far Cry games (which officially support Sony controllers) nothing happens. If you disconnect and reconnect the controller during gameplay the UI elements switch to Playstation icons (X, Triangle, Circle etc.), however, all inputs from the controller are ignored. In Assassin's Creed Origins it *kind of* works but it's constantly alternating between keyboard and Sony input mapping and thus making inputs very slow and laggy. Also the buttons are mapped incorrectly. The controllers work in other games that support these controllers that are not by Ubisoft. XInput Controllers work perfectly fine in Ubisoft Games. -- 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 58333] New: Lotus Freelance Graphics 2.1 reports a C runtime error and exits
by WineHQ Bugzilla June 17, 2025

June 17, 2025

http://bugs.winehq.org/show_bug.cgi?id=58333 Bug ID: 58333 Summary: Lotus Freelance Graphics 2.1 reports a C runtime error and exits Product: Wine Version: 10.9 Hardware: x86-64 URL: https://archive.org/download/lotussmartsuiterelease3.1 forwindows/Lotus%20SmartSuite%20Release%203.1%20for%20 Windows.zip OS: Linux Status: NEW Keywords: download, win16 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 78706 --> http://bugs.winehq.org/attachment.cgi?id=78706 Screenshot Lotus Freelance Graphics 2.1 reports a C runtime error and either exits or hangs. Installed with an earlier version of Wine to work around Bug 58329. Tested with many version of Wine up to latest git (wine-10.9-62-g68bd146ae55). $ wine 'c:\LOTSUITE\FLW\FLW.EXE' 0134:err:local:LOCAL_GetBlock not enough space in local heap 0b07 for 124 bytes After many hours messing around I discovered that this was due to me adding a single environment variable, such as WINEDEBUG=+server for example. Apparently this was just enough to "break the donkey's back". However, my environment variables aren't particularly large. $ true | xargs --show-limits Your environment variables take up 2260 bytes POSIX upper limit on argument length (this system): 2092844 POSIX smallest allowable upper limit on argument length (all systems): 4096 Maximum length of command we could actually use: 2090584 Size of command buffer we are actually using: 131072 An +all trace (because I didn't know where to start) shows that Wine's environment variables only come to around 3K, which also doesn't seem a lot. I wanted to trace get_startup_info() but setting WINEDEBUG=+ntdll or +server simply triggers the bug. To prove... nothing I added 100 large variables and winevdm sat churning away for five minutes before I got bored and stopped it. 0130:err:sync:RtlpWaitForCriticalSection section 78F049E0 "dlls/krnl386.exe16/syslevel.c: Win16Mutex" wait timed out in thread 0130, blocked by 0134, retrying (60 sec) 0134:trace:local:LOCAL_PrintHeap Local Heap ds=0b07 first=f2c0 last=fff4 items=5 0134:trace:local:LOCAL_PrintHeap f2c0: prev=f2c0 next=f2cc type=1 0134:trace:local:LOCAL_PrintHeap size=12 free_prev=f2c0 free_next=ff80 0134:trace:local:LOCAL_PrintHeap f2cc: prev=f2c0 next=f2fc type=1 0134:trace:local:LOCAL_PrintHeap f2fc: prev=f2cc next=ff80 type=1 0134:trace:local:LOCAL_PrintHeap ff80: prev=f2fc next=fff4 type=0 0134:trace:local:LOCAL_PrintHeap size=116 free_prev=f2c0 free_next=fff4 0134:trace:local:LOCAL_PrintHeap fff4: prev=ff80 next=fff4 type=0 0134:trace:local:LOCAL_PrintHeap size=12 free_prev=ff80 free_next=fff4 0134:err:local:LOCAL_GetBlock not enough space in local heap 0b07 for 124 bytes “Does this mirror the behaviour seen on Windows?” I'll have to come back to that. -- 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 58375] New: Fatal error when trying to run Hitman 3
by WineHQ Bugzilla June 17, 2025

June 17, 2025

http://bugs.winehq.org/show_bug.cgi?id=58375 Bug ID: 58375 Summary: Fatal error when trying to run Hitman 3 Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mfuyami16(a)gmail.com Distribution: --- Created attachment 78784 --> http://bugs.winehq.org/attachment.cgi?id=78784 backtrace from trying to open the main executable, hitman3.exe When trying to run the game Hitman 3, I get a fatal error report. The launcher opens normally, but when I press play, it crashes entirely. I tried opening it from the terminal, and the same thing happens. I am not an experienced user of either Linux or Wine, but I have installed and successfully run several other games on the same device. I have restarted the computer multiple times and even tried redownloading the game, with no effect. The backtrace from Wine is 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 5

[Bug 52500] New: error with winediag (nodrv_CreateWindow)
by WineHQ Bugzilla June 17, 2025

June 17, 2025

https://bugs.winehq.org/show_bug.cgi?id=52500 Bug ID: 52500 Summary: error with winediag (nodrv_CreateWindow) Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: josue.bock(a)univ-smb.fr Distribution: --- Created attachment 71795 --> https://bugs.winehq.org/attachment.cgi?id=71795 output in command line showing errors Hello, When upgading from 6.22 to 6.23, wine does not open anymore with a software. It seems to be related to another bug report (https://bugs.winehq.org/show_bug.cgi?id=51210) but AFAIC see, this was not the same wine version involved. My laptop also has two GPU, one Intel and one Nvidia. The Intel one is expected to be unactivated. I asked for help on the forum before sending this bug report, the discussion is here: https://forum.winehq.org/viewtopic.php?f=2&t=36155&p=135932#top -- 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 55

[Bug 48483] New: Mouse cursor always visible in Gothic 2 with D3D11 renderer
by WineHQ Bugzilla June 17, 2025

June 17, 2025

https://bugs.winehq.org/show_bug.cgi?id=48483 Bug ID: 48483 Summary: Mouse cursor always visible in Gothic 2 with D3D11 renderer Product: Wine-staging Version: 5.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: supercoolemail(a)seznam.cz CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Gothic 2 (Russian with 2.6 no-cd patch) with D3D11 renderer shows X11/KDE mouse all the time. Cursor should not be visible in Gothic 2 at all. It does not have any functional impact but it's disturbing. How to reproduce: - Get Gothic 2. - Test G2 works (menu at least). - Extract GD3D11 (e.g. from https://github.com/Kirides/GD3D11/releases/download/v17.7-dev8/Gothic2-GD3D… but even old versions from Liker suffer from same issue). DLLs from archive belong to `<game dir>/System` directory. - Start the game with `ddraw=n,b`. - See that mouse cursor appears when menu finishes loading. Alternatively, mouse movements make cursor appear even before menu finishes loading. There is some analysis here https://github.com/Tk-Glitch/PKGBUILDS/issues/428 . I can confirm that same issue happens with clean wine-staging 5.0rc4 from Arch repositories (also with wine-tkg built from master). While clean G2 works properly in vanilla wine, GD3D11 needs staging otherwise it crashes at startup. Tested on `Linux coolhost 5.4.12-arch1-1 #1 SMP PREEMPT Tue, 14 Jan 2020 21:44:31 +0000 x86_64 GNU/Linux` Ryzen 7 1700 RX 580 8G 16 G RAM mesa 19.3.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 10