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

[Bug 47844] Add a dual-screen Wine VM

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47844 --- Comment #3 from François Gouget <fgouget(a)codeweavers.com> --- I also got the "Guest has not initialized the display (yet)." message in a Wine VM screenshot. So something else is afoot. -- 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.

Sept. 30, 2019

[Bug 47821] gcin cannot input chinese characters

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47821 --- Comment #3 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Created attachment 65352 --> https://bugs.winehq.org/attachment.cgi?id=65352 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.

Sept. 30, 2019

[Bug 47834] Borderlands 1 (version 1.5.0) doesn't capture mouse

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47834 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dereklesho52(a)Gmail.com --- Comment #6 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- (In reply to kolAflash from comment #5) > (In reply to Alistair Leslie-Hughes from comment #2) > > I've just updated the raw-input patchset in staging. Does this help? > > No, at least not in StarCraft II :-/ > > https://github.com/wine-staging/wine-staging/commit/ > 0c7512f5f53deb168d3508bdd1f1107ecee774c6 > > Everything was fine wine-staging-4.16. We know its the user32-rawinput patchset. Are you able to track down which of these patches is causing the issue? -- 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.

Sept. 30, 2019

[Bug 47755] Installation of Atmel Studio 7 crashes with a Program Error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47755 --- Comment #17 from John <subs(a)qcontinuum.plus.com> --- Just a thought about PKG_CONFIG_PATH. When I compile the 32-bit version, one of the steps is to do this: PKG_CONFIG_PATH=/usr/lib/pkgconfig ../configure --with-wine64=../wine64-build This is as per the instructions here: https://wiki.winehq.org/Building_Wine#Shared_WoW64 The path is correct for my system. -- 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.

Sept. 30, 2019

[Bug 45375] Halo Online: Weird black display problems.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45375 --- Comment #18 from Paul Gofman <gofmanp(a)gmail.com> --- (In reply to Connor McAdams from comment #15) > > if (ins->handler_idx == WINED3DSIH_RCP || ins->handler_idx == WINED3DSIH_RSQ) > > in my patch posted above instead of just the check for RCP. I went through > an apitrace dump to figure it out at the time. So, if you'd mind adding in > the check for WINED3DSIH_RSQ and seeing if that fixes the other texture > issues, that'd be helpful. Please mind that staging patch already workarounds infinity in RCP, RSQ and LOG with multiply_special = 1. See https://bugs.winehq.org/show_bug.cgi?id=34266#c34 for details, and the patch itself: https://github.com/wine-staging/wine-staging/blob/master/patches/wined3d-ze… Your patch is still different though as it replaces the result with 0 instead of FLT_MAX. Comment #6 suggests that the staging workaround replacing inf with FLT_MAX in RCP / RSQ / LOG does not work here, while more generic workaround with multiply_special = 2 works, while some glitches remain, which might be unrelated. Given some problems observed regardless (maybe related to VM exhaustion), I personally don't have yet the confidence that the test results are not biased by the side problems. If it really the case when multiply_special = 1 does not workaround the problem while '... = 2' does, this is very interesting case. At this point it would be great if someone could test it with the memory problem workaround from Comment #11, to see if this will remove remaining glitches. I don't have a confidence that this is the problem here yet. Yes, one of the logs has single GL_OUT_OF_MEMORY error listed, but it is yet hard to be sure that it is not caused by some other specific problem. It would also be helpful if someone could describe the way how to get (legally of course) this version of the game and which is the quickest way to get to the glitches in game. -- 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.

Sept. 30, 2019

[Bug 47782] Segmentation fault and exceptions using ManagementClass

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47782 Hans Leidekker <hans(a)meelstraat.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Fixed by SHA1| |31c0cb48622ae869cfc358be853 | |1821ec1eda7b4 --- Comment #4 from Hans Leidekker <hans(a)meelstraat.net> --- Win32_DisplayControllerConfiguration is implemented with 31c0cb48622ae869cfc358be8531821ec1eda7b4. -- 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.

Sept. 30, 2019

[Bug 47827] Nostale - New Launcher doesn't work

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47827 --- Comment #3 from Jonathan C. <jonadev1993(a)gmail.com> --- (In reply to nkb from comment #2) > Do you have enough free space? I had no issues when downloading and > installing the game. > > (In reply to Zebediah Figura from comment #1) > > Possibly the same as bug 47817. > > Well, OP would run into the same problem since Nostale won't launch as well. Yes, I have enough free space. I have that when there is an update or when I verify the game. -- 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.

Sept. 30, 2019

[Bug 45375] Halo Online: Weird black display problems.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45375 --- Comment #17 from Connor McAdams <conmanx360(a)gmail.com> --- You'll have to compile wine with that change. https://drive.google.com/open?id=1R5y963bxRZ1z3b0EHulKAgmaxWp8XPwL Is an archive containing the patches already compiled in, it's the version of wine I used to use. Just run it with ./wine from the directory you decompress it into, and tell me if it fixes the issues you're talking about. -- 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.

Sept. 30, 2019

[Bug 45375] Halo Online: Weird black display problems.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45375 --- Comment #16 from halome <halome(a)blockchainworldawards.com> --- > Also, I think I remember solving Reactor texture issues (and the ones that > are shown underneath the ghost exhaust, as well as Diamondback's heat > effect) by adding > > if (ins->handler_idx == WINED3DSIH_RCP || ins->handler_idx == WINED3DSIH_RSQ) > > in my patch posted above instead of just the check for RCP. I went through > an apitrace dump to figure it out at the time. So, if you'd mind adding in > the check for WINED3DSIH_RSQ and seeing if that fixes the other texture > issues, that'd be helpful. How do I use the if (ins->handler_idx == WINED3DSIH_RCP || ins->handler_idx == WINED3DSIH_RSQ) in the terminal to run the game? -- 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.

Sept. 30, 2019

[Bug 47846] Age Of Empires III Crash after Intro

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47846 Igor Piedra <piedra-igor(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Mint -- 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.

Sept. 30, 2019