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

[Bug 59728] New: Nexus Boardviewer crashes after opening any supported schematic format

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59728 Bug ID: 59728 Summary: Nexus Boardviewer crashes after opening any supported schematic format Product: Wine Version: 11.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)list.winehq.org Reporter: svyatpro(a)gmail.com Distribution: --- Created attachment 80880 --> http://bugs.winehq.org/attachment.cgi?id=80880 Nexus BV application + X750DP.fz schematic When I open any schematic format the application crashes immediately. Steps to repro: 1. Navigate to menu bar click File->Open 2. Choose any bdw, cad, fz schematic file (for example X750DP.fz inside app folder) -- 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.

May 6, 2026

[Bug 59690] Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #27 from Scott Kidman <scottkidman(a)protonmail.com> --- I'll rerun the 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.

May 6, 2026

[Bug 59690] Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #26 from LingM <lingm+winebz(a)posteo.org> --- > 1. Do I copy those commands verbatim or are they merely examples and I have to find the MR-IDs by myself? The do work verbatim for me. The "10825" is the ID of Paul's MR. The "cc3_fix_maybe" is just a made up name for the local branch. > 2. I had to recompile the Wine Git from scratch, so all the states created by the regression testing are gone. After compiling from scratch, or at any state, can I just recompile the Wine binaries then and there? Usually I'd assume a build system would automatically recompile whatever changed. During the bisection git also just changed the state of the source files and you simply recompiled, right? That said, I'm no wine dev myself and can't answer that question with certainty. -- 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.

May 6, 2026

[Bug 59690] Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #25 from Scott Kidman <scottkidman(a)protonmail.com> --- (In reply to LingM from comment #23) > Download that MR into a new branch on your existing git clone: > > $ git fetch origin merge-requests/10825/head:cc3_fix_maybe > Checking that branch out: > > $ git checkout cc3_fix_maybe > > Now you need to recompile and like you did during bisection. > > @Zeb: Thanks for correcting me btw. Didn't even notice it asked about C++ > and not C. This is embarrassing, but I must ask anyway. 1. Do I copy those commands verbatim or are they merely examples and I have to find the MR-IDs by myself? 2. I had to recompile the Wine Git from scratch, so all the states created by the regression testing are gone. After compiling from scratch, or at any state, can I just recompile the Wine binaries then and there? Sorry, my friend screwed something up, and I have to start all over. -- 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.

May 6, 2026

[Bug 59722] RemoveDirectoryW fails with ERROR_SHARING_VIOLATION after subprocess exit

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59722 --- Comment #2 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- Created attachment 80879 --> http://bugs.winehq.org/attachment.cgi?id=80879 debugging.txt Hello, I tried if I could debug this and here calling the reproducer.exe from a unix terminal gets me two conhost.exe processes. The second gets started in cmd.exe in init_console/alloc_console. This second conhost.exe gets started with current directory in cwd_test, therefore the directory cannot be deleted. Attached file contains some notes with backtraces of interesting events. At the bottom is s simple patch to start the conhost processes with current directory of c:\windows\system32, and it stopped showing me the failure on RemoveDirectory. Can you please check if this fixes the issue also with msys2? -- 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.

May 5, 2026

[Bug 59690] Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #24 from Scott Kidman <scottkidman(a)protonmail.com> --- Thank you LingM, that's what I need to know. I'll let you guys know. -- 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.

May 5, 2026

[Bug 59690] Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #23 from LingM <lingm+winebz(a)posteo.org> --- Download that MR into a new branch on your existing git clone: > $ git fetch origin merge-requests/10825/head:cc3_fix_maybe Checking that branch out: > $ git checkout cc3_fix_maybe Now you need to recompile and like you did during bisection. @Zeb: Thanks for correcting me btw. Didn't even notice it asked about C++ and not C. -- 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.

May 5, 2026

[Bug 59690] Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #22 from Scott Kidman <scottkidman(a)protonmail.com> --- (In reply to Scott Kidman from comment #19) > Unfortunately, I am not savvy enough to do something like that as this is my > first time getting my hands dirty with testing. What I meant by that would be in reference to testing out the patch. -- 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.

May 5, 2026

[Bug 59690] Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #21 from Scott Kidman <scottkidman(a)protonmail.com> --- (In reply to Paul Gofman from comment #18) > Steam version of Command & Conquer Red Alert 3 (Steam game id 17480). I didn't use the Steam version, I used the DVD version. -- 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.

May 5, 2026

[Bug 59690] Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #20 from Scott Kidman <scottkidman(a)protonmail.com> --- Apologies in advance. -- 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.

May 5, 2026