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

[Bug 58216] New: Inquisitor crashes on start
by WineHQ Bugzilla Sept. 19, 2025

Sept. 19, 2025

http://bugs.winehq.org/show_bug.cgi?id=58216 Bug ID: 58216 Summary: Inquisitor crashes on start Product: Wine Version: 10.7 Hardware: x86-64 URL: https://store.steampowered.com/app/241620/Inquisitor/ OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Regression SHA1: 075033d61ffac2a8d42e06e91a12c88f2fa17401 Distribution: ArchLinux Created attachment 78529 --> http://bugs.winehq.org/attachment.cgi?id=78529 terminal output The intro video in Inquisitor never worked for me: it was gracefully skipped and the game loaded directly the main menu. Since Wine-10.7 the game crashes right after start. Reverting the following commit fixes the crash for me: commit 075033d61ffac2a8d42e06e91a12c88f2fa17401 winegstreamer: Make sure WMSyncReader never reads in the background. 'winetricks wmp9' also makes the crash go away (the startup video still does not work). Reproduced with the Steam and GOG.com versions. wine-10.7-73-gf9741837a3b -- 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

[Bug 58662] New: 16-bit bitmap rendering
by WineHQ Bugzilla Sept. 19, 2025

Sept. 19, 2025

http://bugs.winehq.org/show_bug.cgi?id=58662 Bug ID: 58662 Summary: 16-bit bitmap rendering Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)winehq.org Reporter: zowie+wine(a)vandillen.io Distribution: --- Created attachment 79243 --> http://bugs.winehq.org/attachment.cgi?id=79243 Glitchy 16-bit render of Civilization 3. Without OpenGL Civ 3 does not have visible glitches. I've added a new test earlier today for 16-bit bitmap rendering with wGL [1]. In conclusion, it's pretty broken. The solution to this problem isn't trivial, so I'm opening this issue for discussion. On Windows, when wglChoosePixelFormat is called with the flag `PFD_DRAW_TO_BITMAP` and `cColorBits = 16`, you'll be given a pixel format with r5g5b5a1 (except that the alpha bit is somewhat quirky). This gives you a software rendered OpenGL context for OpenGL 1.1 [2]. On Wine, asking for a 16-bit pixel format gets you nothing, because all 16-bit pixel formats with the DRAW_TO_BITMAP are required to have an alpha bit in Wine and none of the pixel formats on my Nvidia driver actually have an alpha bit (there's only r5g6b5 and r16). The alpha bit requirement was introduced recently in MR !8392 [3]. It's worth noting that not getting a pixel format — although it's wrong — actually works pretty well for Civilization 3 (see “relevant software” section). Removing the check for an alpha bit, Wine will be able to find a 16 bit pixel format again, but you'll get unusably bad renders (screenshots in the attachments). Some observations on the screenshots: - You can see alternating vertical black/blue and orange/white/yellow lines every horizontal pixel. - Blue pixels appear in the black lines, but they're rare. I only see blue pixels in the text in the SimGolf screenshot. - The render buffer doesn't seem to be getting cleared (pretty apparent in Civilization 3: the old squares were sticking around) - Zooming in, you can see that there aren't only vertical lines, but also horizontal lines (see zoomed-in screenshot). My theory is that there's two problems: - Wine is probably putting 32-bit-per-pixel renders into the 16-bit-per-pixel bitmaps. This explains the vertical & horizontal lines. I'm guessing there's also some memory corruption as a consequence: It's presumably overwriting twice as much bitmap memory as it should. - The right pixel format just doesn't exist. The format r5g5b5a1 is not something that is actually implemented on hardware (at least not anymore), it's just a quirky Windows software renderer thing. The second point is a bit troublesome because I don't see any easy workarounds. The most obvious solution is to make an OpenGL 1.1 software renderer of our own. Alternatively, it might be possible to simulate the behaviour by using a 32-bits-per-pixel OpenGL context. Whenever glFinish is called, we could download the render to a "secret" Wine-internal bitmap that's also 32 bpp and then overwrite the 16 bpp bitmap based on the pixels of the 32 bpp bitmap. I'm not sure how reliable that is. Looking at the OpenGL 1.1 reference [4], I think making an OpenGL 1.1 software renderer could be a fun project, but the other solution definitely seems like less effort. I've only been involved in Wine for seven days though, so I'll defer the decision to senior maintainers. [1] https://gitlab.winehq.org/wine/wine/-/merge_requests/8888 [2] https://www.khronos.org/opengl/wiki/Platform_specifics:_Windows#PFD_DRAW_TO… [3] https://gitlab.winehq.org/wine/wine/-/merge_requests/8392 [4] https://www.talisman.org/opengl-1.1/Reference.html --- Relevant software (screenshots in attachments) - Sid Meier's SimGolf (demo: https://archive.org/details/Simgolfdemo) In SimGolf, a 16-bit DRAW_TO_BITMAP OpenGL context seems to be used for drawing the terrain. Currently, the terrain renders as black. - Sid Meier's Civilization 3 In Civilization 3, it seems that 16-bit bitmap rendering is used to draw an outline for the movement range of a selected unit (that's just a guess. It draws a square when a unit is selected but I haven't seen it without glitches). It's notable that Civilization 3 currently works fine. Because wglChoosePixelFormat doesn't find a 16-bit pixel format, the `null_gl` implementation is being used right now. That works out pretty well because the movement range outline isn't something you miss when you don't know it's supposed to be there. --- Relevant bugs: Sid Meier's SimGolf does not render properly | https://bugs.winehq.org/show_bug.cgi?id=50876 Civilization III Complete shows black terrain (Wine compiled with OSMesa support) | https://bugs.winehq.org/show_bug.cgi?id=41930 -- 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 9

[Bug 48548] New: Support running multiple tests in submitted jobs
by WineHQ Bugzilla Sept. 18, 2025

Sept. 18, 2025

https://bugs.winehq.org/show_bug.cgi?id=48548 Bug ID: 48548 Summary: Support running multiple tests in submitted jobs Product: Wine-Testbot Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: cdavis5x(a)gmail.com When I submit a job manually on the testbot, I can only run one instance of one executable. For a binary, this makes sense, since there's only one binary; but a patch, for which a choice of Wine test executables is offered, can affect multiple Wine unit tests. I then have to submit the job multiple times, one for each test unit affected. This seems... suboptimal. It'd be much faster and more convenient if I could run multiple tests in a single job. -- 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 58707] New: infinite blocking on reading piped stderr
by WineHQ Bugzilla Sept. 17, 2025

Sept. 17, 2025

http://bugs.winehq.org/show_bug.cgi?id=58707 Bug ID: 58707 Summary: infinite blocking on reading piped stderr Product: Wine Version: 10.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: sewn(a)disroot.org Distribution: --- Created attachment 79307 --> http://bugs.winehq.org/attachment.cgi?id=79307 C program that runs the Wine program 'reg', reading its stderr and discarding it. When a wine program is ran with its stderr piped and read, the program hangs forever for as long as the wineserver is, which can be further tested by running 'wineserver' with a large persistence value. This causes programs that are ran software that wraps around wine to block until wineserver exits. An example program that shows this behavior occuring is attached. Wineserver can be ran seperately with a high persistence to showcase the "hanging". -- 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 58078] New: StarCraft Remastered: game is not started with wine-10.5
by WineHQ Bugzilla Sept. 17, 2025

Sept. 17, 2025

https://bugs.winehq.org/show_bug.cgi?id=58078 Bug ID: 58078 Summary: StarCraft Remastered: game is not started with wine-10.5 Product: Wine-staging Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dimich.dmb(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- The game is not started with wine-10.5 StarCraft.exe process is running and consuming 100% of one CPU core. No video mode changed, no game window created. Battle.net launcher is displaying StartCraft as "Playing Now". After downgrading wine to 10.4 the game starts and works fine. StartCraft: v1.23.10.13515 OS: Arch Linux Kernel v6.14.1 GPU: Nvidia, proprietary driver v570.133.07 -- 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 58702] New: Update to 10.15 breaks Bricklink Studio
by WineHQ Bugzilla Sept. 17, 2025

Sept. 17, 2025

http://bugs.winehq.org/show_bug.cgi?id=58702 Bug ID: 58702 Summary: Update to 10.15 breaks Bricklink Studio 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: bonizak(a)gmail.com Distribution: --- Created attachment 79304 --> http://bugs.winehq.org/attachment.cgi?id=79304 wine backtrace file Bricklink's Studio Version 2.25.8_1, was running fine under 10.14 dev but the update to 10.15 last night has broken Studio. Studio window will open copying the focus window image but otherwise is blank. -- 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 58704] New: io_uring support for Wine
by WineHQ Bugzilla Sept. 16, 2025

Sept. 16, 2025

http://bugs.winehq.org/show_bug.cgi?id=58704 Bug ID: 58704 Summary: io_uring support for Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: k.kahurani(a)gmail.com Distribution: --- This issue mostly relates to the server(for filesystem operations), it seems like the networking implementation could be done outside the server. Just throwing this out there, it's highly unlikely I will work on it for various reasons. Wine still doesn't have io_uring support though, quite a few projects have already implemented io_uring support. Wine would also do with any performance benefits. io_uring is at least promoted as performance oriented, this makes it very interesting. io_uring offers performance benefits in multiple fronts. -> The first and probably the simplest is where operations on file might not have to make calls to 'fget'; typically when an operation is executed on files in Linux, it will involve some call to 'fget' one way or the other. With io_uring, it's possible to register files so that this 'fget' call is avoided. I am not sure how much performance benefit that could achieve. But, still an optimization nonetheless. Similarly, you could register buffers for opcodes(which translate to syscalls) so they're validated, mapped and so on so forth beforehand. When the actual operations/syscall are being executed, this boilerplate is not called. That is also an optimization. -> io_uring allows submitting a batch of syscalls(opcode operations) via one single syscall. This is an optimization, because, of course, without io_uring, you'd have to make multiple syscalls to achieve the same. However, it only seems like this optimization would only be applicable when making very many syscalls and making them very fast otherwise when making singular syscalls, they have to wait until the batch is full and hence would introduce some latency in low throughput situations. -> There might be other optimizations that I have not considered. What interests me most, though, is the syscall/request polling feature which allows applications to submit syscalls(opcode) via zero syscalls. io_uring sets up a kernel thread which polls the io ring and hence when submissions are made, the thread will discover them without any syscalls been made. This is very interesting and would be a straightforward mega-optimization were it not for that fact that the created kernel thread does pin a CPU. Would this work well with other work that's competing for CPU? It's consequently not very clear whether this would be an improvement to Wine, which makes syscalls alongside and in the midst of doing other heavy work. Any thoughts? -- 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 50242] New: Lotus Approach crashes on start up
by WineHQ Bugzilla Sept. 15, 2025

Sept. 15, 2025

https://bugs.winehq.org/show_bug.cgi?id=50242 Bug ID: 50242 Summary: Lotus Approach crashes on start up Product: Wine-staging Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68752 --> https://bugs.winehq.org/attachment.cgi?id=68752 Approach crash on start up Dear Wine Staging Maintainers, Fedora 33 wine-5.22-1.fc33.x86_64 As of 5.22, Lotus Approach now crashes on start up. Word Pro is okay. I have attached the trace. -T -- 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 58644] New: Gears of war Reloaded - doesn't start the actual game
by WineHQ Bugzilla Sept. 14, 2025

Sept. 14, 2025

http://bugs.winehq.org/show_bug.cgi?id=58644 Bug ID: 58644 Summary: Gears of war Reloaded - doesn't start the actual game 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: levanchelidze(a)gmail.com Distribution: --- Created attachment 79208 --> http://bugs.winehq.org/attachment.cgi?id=79208 terminal output I tried to start this game on uhd 620, i found footage online (youtube) that this game actually run on that hardware on windows so i wanted to see if can run on linux as well. However before the game starts it hangs i must say that once it actually entered and than hanged but usually it hangs here (screenshot). I installed vkd3d with winetricks and it hanged at the same place as well -- 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 45870] New: Star Wars Pit Droids fails to install
by wine-bugs＠winehq.org Sept. 14, 2025

Sept. 14, 2025

https://bugs.winehq.org/show_bug.cgi?id=45870 Bug ID: 45870 Summary: Star Wars Pit Droids fails to install Product: Wine Version: 3.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zzarko(a)gmail.com Distribution: --- Created attachment 62369 --> https://bugs.winehq.org/attachment.cgi?id=62369 Screenshot of error I have tried to install an old Win95 game, Star Wars Pit Droids, but it always crashes during the install (actual error is in screenshot). I have created 32-bit wine environment and selected W95 as OS version. The game can be found at: https://www.myabandonware.com/game/star-wars-pit-droids-403 I have tried this with Wine 2.4, same error. I'll add WINEDEBUG=warn+all outputs for both 3.16 and 2.4 versions. -- 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