November 2021 - Wine-Bugs - list.winehq.org

[Bug 51567] Battle.net app takes a long time to start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51567 --- Comment #31 from CJ Bilco <bebing(a)email.com> --- Sounds good. I will definitely remember to do a fresh prefix and a fresh install of battle-net. That has got me over humps in the past. I might give a first try with staging just because I still have the source folder I installed from. Even if I have manually do what the patches automatically would do. But if I am unable to easily do the adding or removing because of that I will quickly move to stable. Yes! It doesn't seem like many people are having this issue! We would be getting more eyes on it if there were more people suffering with it. -- 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.

Nov. 25, 2021

[Bug 51567] Battle.net app takes a long time to start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51567 --- Comment #30 from Sveinar Søpler <cybermax(a)dexter.no> --- There was some bugs around 6.12'ish ref: https://bugs.winehq.org/show_bug.cgi?id=51319 This is closed as fixed with: https://source.winehq.org/git/wine.git/commitdiff/361435f6095f8c759979600b0… Not 100% sure it is related tho. I know that the Battle.net client does not really work if you have enabled "browser hardware acceleration" (default enabled) when using regular wine-staging. This can be disabled in the settings. I tried with Ubuntu distro provided wine-staging-6.22 and after disabling the above, i did not seem to have any huge issues connecting, but going back and forth a bit i experienced a couple of hangs of "Battle.net.exe --updatepid=xxx" pinning one core to 100% leading me having to kill wineserver. Normally a fresh prefix with battle.net seems to take around 5 seconds to start and show my games list and schtuff. Probably not easy to pinpoint a problem if it works for some :) -- 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.

Nov. 25, 2021

[Bug 51567] Battle.net app takes a long time to start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51567 --- Comment #29 from Pavel <pavel1r(a)gmail.com> --- I think staging required for WoW and other games to run, but Battle net should be working with stable. So, it should be possible to check it with stable version. What I'm usually doing, is to try and install Battle.Net in new prefix. The problem can be seen during installation. -- 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.

Nov. 25, 2021

[Bug 51567] Battle.net app takes a long time to start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51567 --- Comment #28 from CJ Bilco <bebing(a)email.com> --- Okay, so would I be able to do this compiling and testing on stable instead of staging? It sounds like the issue happens in stable, but the whole reason I went to staging is some things wouldn't work without it. Well sometimes it's better just to dive in and try some stuff. So currently I am using wine-staging 6.19 because it seems to work better than 6.20 and on. So I think my first try will be start with wine-staging 6.19 as a base and see if I can back out a change or add a change that was removed from there. Oh well, unfortunately I cannot do that today, but will start tinkering when I get a chance. Any help or input is very much welcomed, I will just kinda be bumbling through it. -- 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.

Nov. 25, 2021

[Bug 52105] Handle to \Device\NamedPipe\ cannot be used as the RootDirectory for NtCreateNamedPipeFile

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52105 --- Comment #1 from Jinoh Kang <jinoh.kang.kr(a)gmail.com> --- Patch submitted: https://source.winehq.org/patches/data/220602 -- 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.

Nov. 25, 2021

[Bug 51567] Battle.net app takes a long time to start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51567 --- Comment #27 from Pavel <pavel1r(a)gmail.com> --- (In reply to CJ Bilco from comment #26) > Okay, so this looks promising as I think I would be able to add or subtract > patches if I have this data. I will look at it further. Unfortunately I'm > getting a bit confused. > > Would I start with 6.11 and add something > or start with 6.13 and remove something > or something else > or we might have to do multiple Currently, I got stuck with compilation because it requires staging patches which I only managed to apply to released versions. Didn't have time to look at them more closely. -- 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.

Nov. 25, 2021

[Bug 52106] dxva2:dxva2 fails in test_progressive_device() on cw-rx460 (AMD)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52106 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |12a1b4b360abc6db5de2e393b9e | |c53a77f532ffd Keywords| |regression, source, | |testcase -- 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.

Nov. 25, 2021

[Bug 52106] New: dxva2:dxva2 fails in test_progressive_device() on cw-rx460 (AMD)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52106 Bug ID: 52106 Summary: dxva2:dxva2 fails in test_progressive_device() on cw-rx460 (AMD) Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: dxva2 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com dxva2:dxva2 fails fails in test_progressive_device() on the TestBot's AMD test configuration, cw-rx460: dxva2.c:647: Test failed: Unexpected hr 0x80004005, format 21. dxva2.c:648: Test failed: Unexpected format count 0. dxva2.c:669: Test failed: Unexpected input pool 0x4. https://test.winehq.org/data/patterns.html#dxva2:dxva2 This impacts all Windows versions from 8.1 to 21H1 and multiple Radeon driver versions. But none of the other machines (Nvidia, QEmu) are impacted so this is specific to either the Radeon driver or to this particular graphics card (or generation). Given that the error is a generic E_FAIL, maybe that means one cannot expect this functionality to always be available. A bisect shows that the failures started with the commit that introduced the new tests: commit 12a1b4b360abc6db5de2e393b9ec53a77f532ffd Author: Nikolay Sivov <nsivov(a)codeweavers.com> AuthorDate: Tue Nov 23 15:21:45 2021 +0300 dxva2: Introduce progressive processor device. The point is to provide a device, with similar caps and NV12 support, while keeping software device on its own, the way it should be. This is based on research by Derek Lesho. Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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.

Nov. 25, 2021

[Bug 52105] New: Handle to \Device\NamedPipe\ cannot be used as the RootDirectory for NtCreateNamedPipeFile

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52105 Bug ID: 52105 Summary: Handle to \Device\NamedPipe\ cannot be used as the RootDirectory for NtCreateNamedPipeFile Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 2600ecd4edfdb71097105c74312f83845305a4f2 Distribution: --- Commit 2600ecd4edf (server: Use a separated object for each opened named pipe device file., 2018-10-29) split the role of the named pipe device and the named pipe file. However, in doing so, it changed the semantics of opening \Device\NamedPipe\. In particular, it is no longer possible to use a handle to \Device\NamedPipe\ as RootDirectory when creating a named pipe. This bug makes Cygwin's named pipe creation (https://github.com/cygwin/cygwin/blob/4f47e64b11ed8d47c62fa89e9b971f44b7e9a…) loop forever. -- 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.

Nov. 25, 2021

[Bug 51567] Battle.net app takes a long time to start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51567 --- Comment #26 from CJ Bilco <bebing(a)email.com> --- Okay, so this looks promising as I think I would be able to add or subtract patches if I have this data. I will look at it further. Unfortunately I'm getting a bit confused. Would I start with 6.11 and add something or start with 6.13 and remove something or something else or we might have to do multiple -- 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.

Nov. 25, 2021