[Bug 59690] New: Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error
http://bugs.winehq.org/show_bug.cgi?id=59690 Bug ID: 59690 Summary: Both Command & Conquer 3 and Command & Conquer Red Alert 3 show the same kind of error Product: Wine Version: 10.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@list.winehq.org Reporter: scottkidman@protonmail.com Distribution: --- Created attachment 80796 --> http://bugs.winehq.org/attachment.cgi?id=80796 Error Log Since the release of Wine 10.16, both Command and Conquer3 and Red Alert 3 show the same error in the LAN lobby and the starting of a LAN game. Whenever a Wine user enters the LAN mode lobby, his/her user name shows up twice on the player list. Also, ONLY the Wine users can make games that the other users can join, but not the other way around. When the game starts, every joining user gets kicked out of the game. Going back to Wine version 10.15 worked for me, but this isn't a substantial solution, as 10.15 will eventually fade as newer versions come in. Enclosed are error logs for both games. Please be aware that the demo versions were looked at, but both the demo versions of C&C 3 and Red Alert 3 don't have multiplayer, so verification is impossible. Thank you for looking into this matter. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #1 from Scott Kidman <scottkidman@protonmail.com> --- Created attachment 80797 --> http://bugs.winehq.org/attachment.cgi?id=80797 Red Alert 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 Scott Kidman <scottkidman@protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Mint --- Comment #2 from Scott Kidman <scottkidman@protonmail.com> --- I would add that the operating system is Linux Mint 22.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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #3 from Austin English <austinenglish@gmail.com> --- Please run a regression test: https://gitlab.winehq.org/wine/wine/-/wikis/Regression-Testing -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #4 from Scott Kidman <scottkidman@protonmail.com> --- (In reply to Austin English from comment #3)
Please run a regression test: https://gitlab.winehq.org/wine/wine/-/wikis/Regression-Testing
Thank you for the reply. The page you linked was a little intimidating in terms of the details. Can you please provide further advice? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #5 from Scott Kidman <scottkidman@protonmail.com> --- Back. OK, I tried to compile the latest Wine through Git and this is what it came with: configure: WARNING: i386 PE cross-compiler supporting C++17 not found, some modules won't be built. configure: WARNING: x86_64 PE cross-compiler supporting C++17 not found, some modules won't be built. Should I worry about these? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 LingM <lingm+winebz@posteo.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lingm+winebz@posteo.org --- Comment #6 from LingM <lingm+winebz@posteo.org> --- Uh, yeah, without a cross-compiler you're not going to produce a working build. Make sure you have all the required build dependencies installed: https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine#satisfying-build-d... Those two messages are specifically about "MinGW cross-compiler" from the second row of the table. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 Zeb Figura <z.figura12@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com --- Comment #7 from Zeb Figura <z.figura12@gmail.com> --- No, a C++ cross compiler is not necessary for anything right now. Only a C cross compiler. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #8 from Zeb Figura <z.figura12@gmail.com> --- Also, at this point I believe it's still possible to produce a *working build* without even a C cross compiler. Some applications depend on a cross-compiled build, though. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #9 from Scott Kidman <scottkidman@protonmail.com> --- OK, I got that problem handled. How do I run a regression test exactly? like this? $ compiled-wine-dirctory/wine program.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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #10 from Scott Kidman <scottkidman@protonmail.com> --- Created attachment 80847 --> http://bugs.winehq.org/attachment.cgi?id=80847 Regression Test for Red Alert 3 My first attempt. I just entered /wine-git/wine ~/path/to/game/Ra3.exe Tell me how I did, but be lenient, it's my first time after all. The Wine version is wine-11.7-164-g1535a941198. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 Olivier F. R. Dierick <o.dierick@piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be --- Comment #11 from Olivier F. R. Dierick <o.dierick@piezo-forte.be> --- Hello, Please read the link given in comment #3 as it contains the instructions to do a regression test. What you did is compile a local git version of wine and run it. Being able to do that is a requirement of a regression test, but is not the regression test. The regression test involves repeating that, in succession, indicating if the issue was present or not at each iteration, until the git bisect command tells which commit is the bad commit. Now that you have a copy of the git source that you can compile yourself, you need to follow the instructions starting from there to perform the regression test: https://gitlab.winehq.org/wine/wine/-/wikis/Regression-Testing#running-the-b... Please read the whole instruction page thoroughly, as we won't be able to help you by holding your hand for the whole process on this Bugzilla. If you need such help, you should ask on the forums (link on the top most header bar on this page). Regards. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #12 from Scott Kidman <scottkidman@protonmail.com> --- OK guys, I am back. I ran the test and now there are zero revisions. Many were bad, but some were good. Would you like me to post my findings here, despite the fact that there are no hash submissions from the outputs? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #13 from Olivier F. R. Dierick <o.dierick@piezo-forte.be> --- --- quote from instructions --- If you do not see a message telling you the hash of the first bad commit, but something like this instead: Bisecting: 0 revisions left to test after this you are not done yet. This message means you have pinpointed a specific patch but still need to test if it is the last good or first bad commit so compile and test one more time. --- end --- -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 Scott Kidman <scottkidman@protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #80796|0 |1 is obsolete| | Attachment #80797|0 |1 is obsolete| | Attachment #80847|0 |1 is obsolete| | CC| |scottkidman@protonmail.com --- Comment #14 from Scott Kidman <scottkidman@protonmail.com> --- Created attachment 80857 --> http://bugs.winehq.org/attachment.cgi?id=80857 Regression Test Result OK, here is my second attempt in creating a regression test. I had to make a lot of mistakes, and some will probably require learning a couple more times, but I think I get the knack of doing it. The result came when I "ran out of steps." I'll explain. The second last iteration had 0 revisions and 1 step to perform. I still compiled and tested beyond that. When it reached 0 revisions and 0 steps, the bug was not present and a git bisect good outputs the result as shown in the attached file. I just hope I am doing it right. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #15 from Scott Kidman <scottkidman@protonmail.com> --- To clear things further, the following is what I did in sequential order: 1. Computer shows 0 revisions and 1 step. 2. I compile and run. 3. The bug is present. 4. I tell that to the software. 5. Computer shows 0 revisions and 0 steps. 6. I compile and run. 7. Program runs and shows no errors. 8. I tell that to the software, it's a "good" result. 9. The Regression results appear. In case I was too wordy, the steps above are what happened. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #16 from Scott Kidman <scottkidman@protonmail.com> --- Anyhow, please tell me how I did. I compiled 9 times in total and tested each one, in total of course. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 Scott Kidman <scottkidman@protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |d48e8d03bd679480c24671908f1 | |d2e4c0851bd65 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 Scott Kidman <scottkidman@protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pgofman@codeweavers.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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #17 from Scott Kidman <scottkidman@protonmail.com> --- OK, I found out that I have to fill in the regression SHA on the form above. Did that. Can anyone attest to seeing the regression SHA? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #18 from Paul Gofman <pgofman@codeweavers.com> --- I reproduced duplicated user name with Steam version of Command & Conquer Red Alert 3 (Steam game id 17480). However, I could not make the game ever see the peer in the local network (also using Windows on both sides) so could not check if the local multiplayer fully works. The blamed commit, while still looks correct per se, introduced an issue with ws2_32.gethostbyname() which started additionally returning a loopback address for local host name (local host name as in what gethostname shows, not 'localhost'). I sent MR upstream: https://gitlab.winehq.org/wine/wine/-/merge_requests/10825 Could you please confirm if possible if that fully fixes the regressive issues? If not, could you please provide additional info: 1. Exact game name / version reproducing (and how can I get it if that is not Steam version)? 2. Exact reproduction steps. 3. The compressed output with the following logging enabled: WINEDEBUG=+pid,+loaddll,+timestamp,+seh,+unwind,+debugstr,+threadname,+iphlpapi,+winsock ...? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #19 from Scott Kidman <scottkidman@protonmail.com> --- Mr. Gofman, thank you for responding in a timely manner. Unfortunately, I am not savvy enough to do something like that as this is my first time getting my hands dirty with testing. Can you link to an instructional article where I can get the information to do such a thing? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #20 from Scott Kidman <scottkidman@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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #21 from Scott Kidman <scottkidman@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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #22 from Scott Kidman <scottkidman@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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #23 from LingM <lingm+winebz@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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #24 from Scott Kidman <scottkidman@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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #25 from Scott Kidman <scottkidman@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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #26 from LingM <lingm+winebz@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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #27 from Scott Kidman <scottkidman@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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #28 from Scott Kidman <scottkidman@protonmail.com> --- I tested the MR and it seems to work. I updated my system's Wine just in case; I kept it at 10.15 the whole time to keep it "LANNable." The test passed nevertheless. Put it in the next version, Mr. Gofman. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 --- Comment #29 from Scott Kidman <scottkidman@protonmail.com> --- Last message: is it safe to say that the 10825 fix will be on the next Wine 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 Paul Gofman <pgofman@codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Fixed by SHA1| |866547fb1fb726e6eb74629c2f3 | |72ba2bf82f412 Status|UNCONFIRMED |RESOLVED --- Comment #30 from Paul Gofman <pgofman@codeweavers.com> --- Should be fixed by 866547fb1fb726e6eb74629c2f372ba2bf82f412 . Now when MR is merged it should appear in release 11.9. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59690 Alexandre Julliard <julliard@winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #31 from Alexandre Julliard <julliard@winehq.org> --- Closing bugs fixed in 11.9. -- 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.
participants (1)
-
WineHQ Bugzilla