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

[Bug 52016] steamwebhelper crash due to GetHandleVerifier+0x1edd84c in libcef

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52016 andy <andy86(a)fastwebnet.it> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|mfplat |-unknown Summary|steamwebhelper crash due to |steamwebhelper crash due to |unimplemented function |GetHandleVerifier+0x1edd84c |mfplat.dll.MFIsQueueThread |in libcef --- Comment #1 from andy <andy86(a)fastwebnet.it> --- I forgot I've used mediafoundation workaround, without that (clean prefix) steamwebhelper crash with GetHandleVerifier+0x1edd84c in libcef same as native mfplat. -- 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. 10, 2021

[Bug 52016] New: steamwebhelper crash due to unimplemented function mfplat.dll.MFIsQueueThread

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52016 Bug ID: 52016 Summary: steamwebhelper crash due to unimplemented function mfplat.dll.MFIsQueueThread Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: andy86(a)fastwebnet.it Distribution: --- Steamwebhelper.exe crash continuously while steam is running, wine says: Call from 7B011026 to unimplemented function mfplat.dll.MFIsQueueThread, aborting Steam library and store tabs remains always black like bug 37110 and installing corefonts (bug 32342) and/or disable libglesv2.dll do not workaround this. Using native mfplat steam shows library loading screen but crash with libcef error. -- 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. 10, 2021

[Bug 32342] Multiple applications and games using 'Webkit' or 'Blink' web browser engine crash on startup ('Arial' and 'Times New Roman' font face name validation)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=32342 andy <andy86(a)fastwebnet.it> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andy86(a)fastwebnet.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. 10, 2021

[Bug 51873] Joy.cpl crashes on the FFB tab when the FFB device is selected in the drop down list

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51873 --- Comment #14 from Rémi Bernon <rbernon(a)codeweavers.com> --- Sorry, effect number, not event. -- 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. 10, 2021

[Bug 51873] Joy.cpl crashes on the FFB tab when the FFB device is selected in the drop down list

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51873 --- Comment #13 from Rémi Bernon <rbernon(a)codeweavers.com> --- I see. It could be possible to do it the same way as feature reports but the problem I'm seeing there is that IOCTL_HID_GET_INPUT_REPORT needs to be explicitly requested and I don't see how it would specify the event number it's interested in. Is HIDIOCGINPUT returning an error if there's no more input report for the matching id, or is it blocking until there's one? If it's the case, we'll maybe have to implement IOCTL_HID_GET_INPUT_REPORT in the same kind of way then, instead of succeeding every time and returning the last report seen. This would need to be the case for all the backend though, and maybe not completely straightforward. The client (dinput) will also need to make a dedicated asynchronous ioctl to read effect statuses, instead of reading them in the same way as the device state reports. Another possible approach would be to do like the SDL backend, where we would request HIDIOCGINPUT regularly and push the report in the same way as device state reports. That may be simpler from the client perspective as we wouldn't have to worry whether a device needs IOCTL_HID_GET_INPUT_REPORT requests or just ReadFile calls. -- 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. 10, 2021

[Bug 51873] Joy.cpl crashes on the FFB tab when the FFB device is selected in the drop down list

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51873 --- Comment #12 from Ivo Ivanov <logos128(a)gmail.com> --- (In reply to Rémi Bernon from comment #11) > Created attachment 71009 [details] > WIP patches for PID input state report Thanks! The patchset looks good. The SDL and lnxev parts look implemented well. My device (Simucube 2) though, doesn't send a single PID State Report on the INTERRUPT IN endpoint. It'll need the input report requested through the control endpoint with the HIDIOCGINPUT from the winebus.sys/bus_udev hidraw part. I thought that if there is no available report with the requested id from the last read through the INTERRUPT IN channel, then something like the Get Feature Report can be done in IOCTL_HID_GET_INPUT_REPORT in winebus.sys/main.c hid_internal_dispatch(), etc. -- 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. 10, 2021

[Bug 52015] Final Fantasy XIV crashes on game startup on wine-6.21

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52015 contact(a)mail.redstrate.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux CC| |contact(a)mail.redstrate.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.

Nov. 10, 2021

[Bug 52015] New: Final Fantasy XIV crashes on game startup on wine-6.21

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52015 Bug ID: 52015 Summary: Final Fantasy XIV crashes on game startup on wine-6.21 Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: contact(a)mail.redstrate.com Distribution: --- As of 6.21, the game (Final Fantasy XIV) crashes on startup as soon as you try using any launcher, as the crash happens from ffxiv_dx11.exe (the game's actual executable). This only happens of 6.21, as going back to 6.20 fixes this issue. Unfortunately the only relevant error is a page fault and wine even fails to attach a debugger and gather a stack trace. I unfortunately don't have time today to perform a bisect, but I'll try to run one as soon as possible. -- 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. 10, 2021

[Bug 51873] Joy.cpl crashes on the FFB tab when the FFB device is selected in the drop down list

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51873 --- Comment #11 from Rémi Bernon <rbernon(a)codeweavers.com> --- Created attachment 71009 --> https://bugs.winehq.org/attachment.cgi?id=71009 WIP patches for PID input state report -- 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. 10, 2021

[Bug 51873] Joy.cpl crashes on the FFB tab when the FFB device is selected in the drop down list

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51873 --- Comment #10 from Rémi Bernon <rbernon(a)codeweavers.com> --- Awesome! I'll have a look at the patches, thanks. About the GetEffectStatus issue and the PID state input report, I saw that problem too and I have some WIP patches (attached next), if you want to have a look -and feel free to make updates or rewrite then if you like- but I wanted to write some tests first and didn't find the time to do it yet. -- 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. 10, 2021