February 2026 - Wine-Bugs - list.winehq.org

[Bug 57031] Mouse "tremble" in Robin Hood: The Legend of Sherwood (GoG).

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=57031 Lukáš Linhart <l.linhos(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |l.linhos(a)gmail.com -- 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.

Feb. 25, 2026

[Bug 59450] VKD3D "fixme" errors and game hangs in Hades 2

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #5 from Henri Verbeet <hverbeet(a)gmail.com> --- (In reply to Tony Fabris from comment #2) > To answer your last question quickly: The message "Unhandled view dimension > 0x2" is a continuous stream in the console from the moment the game starts > playing. Yet the game still runs fine during that stream of messages. I can > play the game for long stretches with that message continuously spilling out > of the console. The hang is not coincident with that message, or any other > particular message. Too bad; it would have been a relatively easy issue to address. :) I'll see what I can do about some of the FIXMEs in that log, but it doesn't look especially likely that they have anything to do with the hang you're seeing. Unfortunately that also casts some doubt on whether this is necessarily a vkd3d issue; I don't think an issue in a different part of Wine (or e.g. MoltenVK) can be ruled out at this point. > Regarding the fact that VKD3D is modified in Crossover: I had tried to > contact their tech support about it first. I'm a lifetime-paid Crossover > customer (they even sent me swag when I signed up) but they just shrugged > their shoulders about it. Sorry to hear that. Just so I don't give the wrong impression, I actually work for CodeWeavers, but I'm not that much involved with CrossOver or the macOS side of things, and my role in this bug tracker is purely that of vkd3d maintainer/developer. > Though whatever modification they made to VKD3D, > it works, because I can run the game under Crossover but not under a vanilla > build of Wine. I'd love to know what it is that they did; if there's a way > to make that tweak (whatever it is) to a vanilla build of Wine, and then > troubleshoot from there, that might be fruitful. The source code for vkd3d (and Wine, and a few other components) in CrossOver can be found at https://www.codeweavers.com/crossover/source (There are a few different ways to get there from the CodeWeavers homepage; one way is to go to "CrossOver", scroll to the bottom of the page, then click "GET CROSSOVER SOURCE CODE".) > Regarding building my own software: As recently as a couple of years ago, I > was the DevOps engineer in charge of the entire set of version control and > build systems for a large software company. The problem is, it was an all > Microsoft/Windows/Azure house, so I've got only a little bit of experience > with building software on Linux/Unix/BSD/MacOS. Though I'm absolutely > willing to give that a shot with some guidance. There's only a couple of > barriers to that: I'm on MacOS v12 Monterey, and my Intel Mac won't run a > newer OS than that. And the most common package manager, Homebrew, is > deprecated on Macos v12 Monterey and I have to find versions of everything > on MacPorts instead of Homebrew. However, I'm happy to spin up a virtual > machine to run builds if needed: I'm a paying customer of Parallels as well, > so if Wine/VKD3D builds can be built in one of those VMs I could do that > too. I just wouldn't know where to start, or how to integrate those built > files into a Crossover bottle, without guidance. Wine uses Windows builds of vkd3d; in principle that means it doesn't matter too much whether the build was made on macOS, Linux, Windows, or somewhere else. Building on Windows is possible, but needs something like MSYS2 or Cygwin. WSL 2 might work as well, but I'm not aware of anyone having tried. If you have some familiarity with building things on Linux, building in a Linux VM may be the easiest option. For macOS, the main package you'll need is mingw-w64; I think that's called the same in both brew and MacPorts. mingw-w64 also includes WIDL in the form of x86_64-w64-mingw32-widl, at least in brew. There are some instructions at https://gitlab.winehq.org/wine/vkd3d/-/wikis/Building-a-MinGW-WoW64-Wine-wi… Those are written for Linux, but should largely apply to macOS as well. It may be best to just send me an e-mail if you run into any issues with this part, to avoid spamming the bug tracker too much. :) (In reply to Tony Fabris from comment #4) > I can't tell if the "trace" command had any effect on the console output. > Did it work or am I doing it wrong? It doesn't look like it; if it worked you'd see a lot of output of the form "vkd3d:....:trace:...". It may be that the CrossOver UI is interfering; I know it has a mechanism to set these environment variables through the GUI, and that may be overriding what you're setting on the command line. -- 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.

Feb. 25, 2026

[Bug 59459] MiKTeX 2.9 build 5105 (32-bit) "Unhandled page fault on read access to 00000000" after installation

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59459 --- Comment #1 from KRosUser <kyle.kcsoftwares(a)gmail.com> --- Created attachment 80446 --> http://bugs.winehq.org/attachment.cgi?id=80446 Installer error message -- 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.

Feb. 25, 2026

[Bug 59459] MiKTeX 2.9 build 5105 (32-bit) "Unhandled page fault on read access to 00000000" after installation

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59459 KRosUser <kyle.kcsoftwares(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|11.2 |11.3 -- 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.

Feb. 25, 2026

[Bug 34178] MiKTeX 2.9 build 5105 (32-bit) fails to install (wizard dialog caption reset by initial property page selection)

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=34178 KRosUser <kyle.kcsoftwares(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle.kcsoftwares(a)gmail.com --- Comment #10 from KRosUser <kyle.kcsoftwares(a)gmail.com> --- Different symptom here: https://bugs.winehq.org/show_bug.cgi?id=59459 -- 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.

Feb. 25, 2026

[Bug 59459] MiKTeX 2.9 build 5105 (32-bit) "Unhandled page fault on read access to 00000000" after installation

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59459 KRosUser <kyle.kcsoftwares(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Distribution|--- |Ubuntu URL| |https://github.com/tim-lebe | |dkov/packages/releases/down | |load/2019_Q1/org.miktex.MiK | |TeX-2.9.5105-org.miktex.MiK | |TeX-2.9.5105.exe -- 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.

Feb. 25, 2026

[Bug 59459] New: MiKTeX 2.9 build 5105 (32-bit) "Unhandled page fault on read access to 00000000" after installation

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59459 Bug ID: 59459 Summary: MiKTeX 2.9 build 5105 (32-bit) "Unhandled page fault on read access to 00000000" after installation Product: Wine Version: 11.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)list.winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- Created attachment 80445 --> http://bugs.winehq.org/attachment.cgi?id=80445 Unhandled Page Fault Backtrace Trying to reproduce https://bugs.winehq.org/show_bug.cgi?id=34178 with installer from https://github.com/tim-lebedkov/packages/releases/download/2019_Q1/org.mikt… Installer fails at the last stage for "unknown reason" After closure, Unhandled page fault is triggered with attached backtrace wine: Unhandled page fault on read access to 00000000 at address 0041D900 (thread 01ec), starting debugger... -- 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.

Feb. 25, 2026

[Bug 59450] VKD3D "fixme" errors and game hangs in Hades 2

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #4 from Tony Fabris <tfabris(a)gmail.com> --- Created attachment 80444 --> http://bugs.winehq.org/attachment.cgi?id=80444 Console output after setting VKD3D_DEBUG=trace - Did that work? Attaching console output after executing these commands (I'm doing everything at the shell instead of using the Crossover UI): VKD3D_DEBUG="trace" "/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/CrossOver-Hosted Application/wine" --bottle "Games and Utilities" --cx-app "C:\Program Files\Hades2\Ship\Hades2.exe" The game hangs at the same time the stream of console output stops. I can't tell if the "trace" command had any effect on the console output. Did it work or am I doing it wrong? As always: The message "Hades2.exe[73770:1377925] addPresentedHandler cannot be called after drawable has been presented" is a continuous constant stream of output, intermixed with other messages, and that's not a VKD3D message so I don't think it's useful in this case? Mainly I'd like to know if the variable VKD3D_DEBUG="trace" worked at all? -- 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.

Feb. 25, 2026

[Bug 59450] VKD3D "fixme" errors and game hangs in Hades 2

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #3 from Tony Fabris <tfabris(a)gmail.com> --- Slight update about that one error message: "Unhandled view dimension 0x2" isn't the one that comes out in a continuous stream while playing the game. The one that comes out in a continuous stream is this one: "Hades2.exe[73770:1377817] addPresentedHandler cannot be called after drawable has been presented" and that's not even a VKD3D Message. So I'll try to get more information about "Unhandled view dimension 0x2" and get back to 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.

Feb. 25, 2026

[Bug 59450] VKD3D "fixme" errors and game hangs in Hades 2

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59450 --- Comment #2 from Tony Fabris <tfabris(a)gmail.com> --- Henri, thanks so much for your detailed response. To answer your last question quickly: The message "Unhandled view dimension 0x2" is a continuous stream in the console from the moment the game starts playing. Yet the game still runs fine during that stream of messages. I can play the game for long stretches with that message continuously spilling out of the console. The hang is not coincident with that message, or any other particular message. Regarding the fact that VKD3D is modified in Crossover: I had tried to contact their tech support about it first. I'm a lifetime-paid Crossover customer (they even sent me swag when I signed up) but they just shrugged their shoulders about it. Though whatever modification they made to VKD3D, it works, because I can run the game under Crossover but not under a vanilla build of Wine. I'd love to know what it is that they did; if there's a way to make that tweak (whatever it is) to a vanilla build of Wine, and then troubleshoot from there, that might be fruitful. Crossover's whole deal was that they were advertising that version 26.0 made a whole bunch of new games compatible, and I have a guess that their changes to VKD3D were a big part of that process. Here's their blog post about it: https://www.codeweavers.com/blog/mjohnson/2026/2/10/crossover-26-cures-arti… Regarding building my own software: As recently as a couple of years ago, I was the DevOps engineer in charge of the entire set of version control and build systems for a large software company. The problem is, it was an all Microsoft/Windows/Azure house, so I've got only a little bit of experience with building software on Linux/Unix/BSD/MacOS. Though I'm absolutely willing to give that a shot with some guidance. There's only a couple of barriers to that: I'm on MacOS v12 Monterey, and my Intel Mac won't run a newer OS than that. And the most common package manager, Homebrew, is deprecated on Macos v12 Monterey and I have to find versions of everything on MacPorts instead of Homebrew. However, I'm happy to spin up a virtual machine to run builds if needed: I'm a paying customer of Parallels as well, so if Wine/VKD3D builds can be built in one of those VMs I could do that too. I just wouldn't know where to start, or how to integrate those built files into a Crossover bottle, without guidance. In the meantime, I will try using those environment variables to get more information out of the version of VKD3D that's running in Crossover. If there's anything new in that output, I'll put it here, and also send it to the Crossover folks and see if they can come up with something too. Thanks so much for your help! -- 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.

Feb. 25, 2026