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 #18 from CJ Bilco <bebing(a)email.com> --- Oh it looks like you all are compiling from source. I thought everyone else was using package management. So nevermind my comment about that. -- 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 #17 from CJ Bilco <bebing(a)email.com> --- I compile from the source, so I don't know if that would make doing this easier or harder, but I am willing to try. Another idea is to see if we have a common setup. Sometimes I have a fear it has to do with 32 bit libvulkan. I am able to compile 64 bit libvulkan, but not 32 bit libvulkan, so I take the 32 bit libvulkan from .deb files. But the only version I can use is a bit older. I am using libvulkan.so.1.0.39. Also, I am have nvidia. Thirdly, I get: 0150:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems But I think I get that for other apps that work okay. -- 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 #16 from Pavel <pavel1r(a)gmail.com> --- I'm trying to do so, but don't understand how to apply staging patches, as neither 6.11 nor 6.12 patches do not apply to commits in between. If someone has experience with this, some guidance will be helpful -- 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 52100] foobar2000 crashes immediately after start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52100 matthias.grobarek(a)posteo.de changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEEDINFO |RESOLVED --- Comment #4 from matthias.grobarek(a)posteo.de --- Oh my God, you are completely right, why haven’t I taken a look at this myself?! I had the USE flag gstreamer disabled because sometime in the past I didn’t want Portage to re-emerge dozens of packages with abi_x86_32. I reactivated the gstreamer USE flag and let Portage re-emerge all those packages. wine-staging 6.22 works properly now. I’m sorry to have bothered you with my own mistakes. :( -- 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 52062] dinput HID joystick doesn't implement effect state reports.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52062 --- Comment #2 from Ivo Ivanov <logos128(a)gmail.com> --- (In reply to Rémi Bernon from comment #1) > I wrote (and sent upstream) a few tests for these functions and as far as I > can see, Microsoft PID driver isn't trying to read the effect state reports > using IOCTL_HID_GET_INPUT_REPORT at all, but expects the reports to come > alongside the device state input reports. > > In any case, not having the reports implemented doesn't seem to be much of > an issue, and DInput returns some default flags depending on the operations > and the effects is knows have been created and started. I thought the same. There is no sign of any Get_Input_Report requests in the captured usb traffic from Windows, either. IMO it would need the start time (GetTickCount64(), etc.) and loop count from Start(), and duration from SetParameters(). Also if start delay is confirmed by a conformance test to be separate from the duration, it should be added to the equation as well. Probably would need a flag for the paused state too. Then there is the Solo mode in Start(), and the various FFB commands in SendForceFeedbackCommand(), which would need enumeration of the created effects and resetting (zeroing, etc.) their start times and probably the other state parameters. Slightly more complicated look the Pause and Continue commands from SendForceFeedbackCommand(), which by documentation should pause the effect timers by their current step, and then continue playing for the remaining time. They would need enumeration of the created effects on Pause and clearing the start time, start delay, and reducing the duration to the remaining time, while flagging them as paused. Then Continue would set the start time of the paused effects, etc. All of this while also considering the Infinity duration and loop count. This could be implemented as backup for the other method. -- 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 51210] winediag:nodrv_CreateWindow Unknown error (998)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51210 --- Comment #13 from Vasily Galkin <galkin-vv(a)ya.ru> --- Created attachment 71124 --> https://bugs.winehq.org/attachment.cgi?id=71124 code sample for adding vkGetPhysicalDeviceXlibPresentationSupportKHR > If anyone know how vkCreateInstance can be called in a way that returns ICD that is compatible with specific X11 disaply, this maybe can be used to fix the issue. I was completely wrong here, since I wasn't undestanding how vulkan loader works. I've started step-by-step debugging with vulkan-loader 1.2.189 and found that pvkGetRandROutputDisplayEXT( vk_physical_devices[device_idx], ... call (in my example or in wine's xrandr.c) initially calls loaders GetRandROutputDisplayEXT that tail-calls terminator_GetRandROutputDisplayEXT that tail-calls into libnvidia-glcore.so.470.86 both GetRandROutputDisplayEXT and terminator_GetRandROutputDisplayEXTdefined in https://github.com/KhronosGroup/Vulkan-Loader/blob/sdk-1.2.189/loader/exten… but are not visible in the stacktrace due to tail-calling. So my situation is similar to https://bugs.winehq.org/show_bug.cgi?id=49407 But the problem is not "protocol error is returned on bad RROutput" but "crash on non-nvidia Display* ". Note that 470.86 is the latest driver on 470 "Production" branch, but 470 is NOT the latest branch now. The latest is "NewFeature" 495.44. I tried to filter out vulkan devices incompatible with a display by adding VK_KHR_xlib_surface to the list of extensions and using vkGetPhysicalDeviceXlibPresentationSupportKHR, that seems to be designed for it according to "Issue 1" in https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VK_KH… This works for filtering out "AMD vulkan device and Nvidia display" combination, but fails to filter out "Nvidia vulkan device and AMD display". It seems that vkGetPhysicalDeviceXlibPresentationSupportKHR incorrectly returns true for Nvidia device. attaching a partial code sample that I used for vkGetPhysicalDeviceXlibPresentationSupportKHR experiments. Also see the above khronos link for alternative that can be used after creating window. -- 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 49856] ShareX can't open settings window

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49856 --- Comment #11 from Fabian Maurer <dark.shadow4(a)web.de> --- Seems to work fine with wine-6.22. What's odd though: Sometimes it tried to download dotnet47, despite mono being installed. Fresh wineprefix fixed it 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.

Nov. 25, 2021

[Bug 36550] cygwin build broken in dlls/msvcrt/tests

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=36550 --- Comment #2 from Austin English <austinenglish(a)gmail.com> --- (In reply to Piotr Caban from comment #1) > Is this still an issue? Do we care about building wine on cygwin? I personally don't have regular access to windows to check, but think it's an interesting case (or at least, if we don't support it, we should explicitly state that in the README/configure). That said, with wine now building using mingw/WSL being a thing, I'm not sure how/where cygwin fits in the current atmosphere. I'd be curious to know what others think, particularly Alexandre; but if no one else cares, I'm fine with closing 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 52100] foobar2000 crashes immediately after start

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52100 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- Did you build with USE=-gstreamer? What are your USE flags? -- 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 49856] ShareX can't open settings window

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49856 --- Comment #10 from Cameron <CamnJB(a)gmail.com> --- Program seems to work fine other than hotkeys don't work and an ffmpeg error when I try to screen capture. Everything else seems to work fine. -- 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