Wine 10.0-rc2 Released With 21 Fixes For The Week

[phoronix]

Phoronix: Wine 10.0-rc2 Released With 21 Fixes For The Week

Building off last week's release of Wine 10.0-rc1 is now Wine 10.0-rc2 as the next test release in working toward the Wine 10.0 stable debut around mid January...

https://www.phoronix.com/news/Wine-10.0-rc2-Released

[pinguinpc]

This wine version back to work in my case because fixed this bug:

https://bugs.winehq.org/show_bug.cgi?id=57506

Also have various bugs related virtual desktop however remains a nasty bug in some apps using virtual desktop:

https://bugs.winehq.org/show_bug.cgi?id=57515

in this bug game app (in my case with world in conflict gog version) begin normally but when you close game and back to virtual desktop, wine taskbar disappear

Another solved issue stay related with mouse description above object (in before versions stay broken if remember correctly this issue appear around wine 9.21) and now this is solved too



in screen appear in yellow square where appear Scorn x64 GOG


Other issue fixed in my case stay related with this bug:

https://bugs.winehq.org/show_bug.cgi?id=57418

appear "Fatal error: Unable to create game window!" when try open sin episodes emergence but now:



however suffer of same problem than world in conflict when you close game

[theuserbl]

This wine version back to work in my case

Thx for you comment. :-)
Not everyone testing every new WINE-version.
But it is nice, that there is someone, who making from every WINE-version nice fresh new screenshots and own tests.
Thanks.


Btw: Have you tried out how the ReactOS explorer.exe with its taskbar working in WINE ? Could it be possible to replace some WINE-parts with ReactOS-parts ?
I think ReactOS have the better desktop, because there is the goal, that it is widely used. I think on WINE most people using the windows-managed-by-operatingsystem mode. So wthout the WINE-desktop. Thats the reason why it have on WINE a lower priority then on ReactOS.

For the ReactOS parts download a nightly build of the LiveCD in the bit-number like your WINE is (I think it is 64 bit)

https://reactos.org/getbuilds/

Uncompress the 7zip file and mount the iso file. There are already compiled binaries in there. Now you can replace your WINE explorer.exe with the ReactOS explorer.exe.
Also you can try out the ReactOS-programs and -games on WINE.

[ayumu]

These wine versions (RCs before stable releases every year) are about the most important.

They fix several regressions, and ultimately ensure the stable release is much better than the one the year before.

[mirmirmir]

These wine versions (RCs before stable releases every year) are about the most important.

They fix several regressions, and ultimately ensure the stable release is much better than the one the year before.

So does that mean, we, as end user, are getting wine update once a year?

[avis]

Another critical systray related regression has been fixed in time for 10-rc2:

https://bugs.winehq.org/show_bug.cgi?id=57525

While tenchrio continues to write walls of text "exposing" me, I continue to do my job. And poor almost entirely false tenchrio's essays here will be ignored and forgotten while my humble contributions will be on full display and will be recorded in commit histories.

[tenchrio]

Another critical systray related regression has been fixed in time for 10-rc2:

https://bugs.winehq.org/show_bug.cgi?id=57525

While tenchrio continues to write walls of text "exposing" me, I continue to do my job. And poor almost entirely false tenchrio's essays here will be ignored and forgotten while my humble contributions will be on full display and will be recorded in commit histories.

Ahh, the spin doctor that accuses others of spinning is at it again. And this time you actually dared to at me.

Sorry Avis but that issue is actually closed by Rémi Bernon and the commit only links to your issue and doesn't mention you by name, can you at the very least stop trying to steal credit for solving issues and just finally admit that all you do is report issues (poorly too, why wouldn't you specify your DE from the start for an issue related to the systrays, I can understand a novice doing this but someone claiming decades of experience should know better)? Like at least thank Rémi in your post rather than pretending once again that the "mighty" Artem contributed (while in reality the issue would have gone nowhere without Rémi's contributions, just like many others of your issues in tons of issue trackers)!

Next stop would be your lying about the severity of the issues you report since this one only seemed to affect XFCE (and only under specific circumstances, so much for "critical systray related regression", even in the issue tracker it is only listed as "P2 Major", so not critical and looking at the bug creation page for wine you are the one that set it like that, you would think a self proclaimed Bugzilla Kernel maintainer would know the distinction. If anything that P2 Major is wrong too since it was just a UI bug that didn't interfere with the running of the program so it should be set as severity "trivial").

Also did you delete your github profile? Still gave a lot of laughs yesterday when I was out having a drink with fellow Software Engineer graduates, one of my friends was complaining about one of their testers, so I wanted to show your github profile but it was miraculously gone. Guess now I will just have to show some of your Wine issues.

[avis]

I reported the bug, Remi wrote a patch specifically to address it and poor tenchrio again makes it sound like I did nothing.

You really should become a spin doctor. Your skills at turning everything inside out are just unparalleled.

And the final commit mentions my bug report:

https://gitlab.winehq.org/wine/wine/-/commit/0b4d2cd2ca1ff74936c408ae65d8d98172745da2

We offset the rect to right before to use parent-relative coordinates,
we need to tell host_window_configure_child it's relative to the parent.

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=57525

This is something absolutely bonkers. I mean this person reinterprets commit log messages. I'm so happy I have you permanently blocked. I don't want to lose my sanity dealing with people who live in an alternative reality and who have the guts to defile those who do the work.

Two recent major regressions in Wine (the other one) have been fixed thanks to me and somehow I did nothing. OMG.

[Espionage724]

FreeBSD has 10.0-rc2!

https://www.freshports.org/emulators/wine-devel/

Screenshot_2024-12-15_15-31-21.png

[tenchrio]

I reported the bug, Remi wrote a patch specifically to address it and poor tenchrio again makes it sound like I did nothing.

And you're trying to make it sound as if reporting and solving a bug are equivalent....
<s> Man, I should really start logging all the names of the company's customers that report bugs and mention them in commits of the company's software, instead of the issue the bug solves and any commentary why it was there in the first place. I mean they found the bug after all! </s>

You really should become a spin doctor. Your skills at turning everything inside out are just unparalleled.

Well you should stop trying to be one as your skills at trying to take claim of issues as if you are the one that solved the issue are quite pathetic, especially since you link directly to them showing that you just report them. So literally like I said before, you didn't resolve it, you didn't actually contribute code to the project and yet you keep trying to pretend to be this mastermind open source maintainer, but you aren't, you're a Software Karen (and a very entitled one).

That isn't me being a "spin doctor" that is just the plain truth, also no thanks I am good being a Software Engineer, what are you again? Like actually, not the made up tittles you keep trying to use here on Phoronix or on Reddit (lmao "SecOp", crazy how bad you are at lying despite how often you do it).

And the final commit mentions my bug report:

https://gitlab.winehq.org/wine/wine/-/commit/0b4d2cd2ca1ff74936c408ae65d8d98172745da2

Wow. you really have a bad time reading more than 1 sentence, I linked to the same commit. The point was that Rémi solved the issue not you and that Rémi is in the commit history and only refers to your issue as being fixed rather than the "Thanks to Artem S. Tashkinov for finding this!" you keep trying to interpret it as, finding an issue on a deeper level is different than just reporting "action doesn't work (as intended)", do you even know how Git Blame works? Did you even know that's a command? Actual Software testers do and use it regularly, especially for a regression and finding when/what commit something stopped working (a.k.a. bisecting, something you don't do on a commit level let alone rarely on a release level).

IDK man, maybe follow your own advice and work on your English reading comprehension. Also that commit was 7 lines of codes (4 of which trace and 2 whitespace so only 1 line was needed to fix your issue), with all your freetime how could you not solve this on your own? Did you even try?

This is something absolutely bonkers. I mean this person reinterprets commit log messages.

Yeah it's insane that you keep trying to do that.

I'm so happy I have your permanently blocked. I don't want to lose my sanity dealing with people who live in an alternative reality and who have the guts to defile those who do the work.

Instead you want to move to an alternative reality where creating an issue in the tracker is equivalent to solving it and the creator of the issue gets all the credit, too bad you're stuck in this one. Also "I have you permanently blocked" not your. Haven't really noticed aside from your constant cries of attention that I am supposedly blocked.

And you want to talk about defiling work? Really, you, the guy who hasn't written a single line of code but constantly makes comments like this:

Maybe one day it will dawn on Wayland developers that we don't need this massive amount of duplication effort.

How about you stop defiling the work the Wayland devs do by not continuously posting your terrible display driver manifesto on Phoronix?
Or how about you finally fork and write the code rather than crying about how devs don't do as you say because you report issues?

Too recent major regressions in Wine (the other one) have been fixed thanks to me and somehow I did nothing. OMG.

Two not too, or just use the number 2. Your English skills really aren't as cracked as you try to make them out to be (and yet you wonder why people on Phoronix and even the Wine issue tracker have a hard time understanding you, but sure blame their English reading comprehension rather than your poor writing or understanding of coding). Also no those weren't fixed because of you, Rémi fixed that one too, you didn't fix it you reported it, that's it!

If you did nothing we don't have your asinine posts on Phoronix, someone else (probably more pleasant) comes along and reports the issue and Rémi fixes it. if Rémi does nothing, we don't have a fix (and you can't claim you resolved it either lol, just like a dozen of your issues on all the trackers you post on, well I guess no longer github ones now that you deleted your account).

Even more insane Ivo Ivanov actually bisected that second regression and managed to pinpoint the exact commit that the regression occurred, yet here you are trying to once again take credit for the actual work other put in! And are you really that bad at reading English you don't understand that Rémi told you twice that the issue does not occur in Gnome? It's hilarious you are trying to accuse me of being a spin doctor when your issue only seemed to affect 1 DE and you're trying to spin it as "Critical" and "Major" when the program in question ran fine you just couldn't use the systray icon (and only under specific circumstances on 1 DE) and of course more importantly, you didn't resolve the issue, so how about you credit the devs that did....