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

[Bug 51828] New: Simucube 2: All applications using raw HID access to communicate with devices, stopped tracking steering axis movement
by WineHQ Bugzilla Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=51828 Bug ID: 51828 Summary: Simucube 2: All applications using raw HID access to communicate with devices, stopped tracking steering axis movement Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: logos128(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: d40d8d968658dca4a75afc97f9e48acda0654b0f Distribution: ArchLinux Created attachment 70716 --> https://bugs.winehq.org/attachment.cgi?id=70716 0001-hidclass.sys-Fix-input-reports-with-ReportID-being-d.patch Found out that the dropping of input packets with lengths different than desc->InputLength, which was introduced with the regression commit is causing this issue. Since the Simucube 2 is a HID PID device, it uses multiple HID reports (with defined ReportIDs), which are different lengths. For such devices desc->InputLength specifies the biggest possible buffer length, that would fit any of the input reports. If the most essential input report for tracking the steering axis movements is smaller than desc->InputLength, it'll be dropped by that check. Only the reports with the exact same size go through in non polled mode. In this case with Simucube 2 the biggest input report is of 61 bytes, and is vendor defined. All the other input reports are smaller sizes, and will get dropped. Attached a patch which fixes the issue. It also fixes possible memory access error with report->buffer while copying it to irp->AssociatedIrp.SystemBuffer, due to the internal buffer for hid_report being just report->length which could be less than or equal to desc->InputLength. The patch is based to the current master (aa629c4c7225166f4ee46476d98702df2e142711). -- 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.

1 7

[Bug 51824] New: TrueDrive, SimHub, Fanaleds,etc.: Non smooth movement tracking with severe skipping/jumping of the steering wheel/controller axis
by WineHQ Bugzilla Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=51824 Bug ID: 51824 Summary: TrueDrive, SimHub, Fanaleds,etc.: Non smooth movement tracking with severe skipping/jumping of the steering wheel/controller axis Product: Wine Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: logos128(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 325984ded50b354686e5a454aa5aca3aafa81432 Distribution: ArchLinux Created attachment 70711 --> https://bugs.winehq.org/attachment.cgi?id=70711 0001-hidclass.sys-Fix-writing-all-new-reports-at-the-last.patch All the mentioned applications use raw HID access (through HidD/HidP calls) to the devices they controll, so the movement tracking problems appear only there. DirectInput works well. After further investigation, found that the simpler ring buffer (hidclass.sys/device.c) introduced with the mentioned regression commit is causing the issues. Appeared that all new reports are pushed at the last available ring buffer slot, due to reaching the end of the buffer before the reading has started. Usually such devices as joysticks, controllers, steering wheels, etc., use constant stream of INPUT reports to report their axis movement, so any report skipping or change of the sequence, while the interested apps are reading, would lead to such issues. Attached a patch which fixes the issue (based on the current master aa629c4c7225166f4ee46476d98702df2e142711). -- 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.

1 11

[Bug 51822] New: Simucube 2 TrueDrive: Doesn't recognize the steering wheel device
by WineHQ Bugzilla Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=51822 Bug ID: 51822 Summary: Simucube 2 TrueDrive: Doesn't recognize the steering wheel device Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: logos128(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: 51560aabcb259cb89659d96654d8ad38edbb528d Distribution: ArchLinux Created attachment 70707 --> https://bugs.winehq.org/attachment.cgi?id=70707 0001-hidparse.sys-Preserve-the-original-state-items.repor.patch, wine_6.18.log, SC2_descr.txt Simucube 2 is FFB steering wheel device using the HID PID specification for FFB. Thus the support for it is included in the Linux kernel as part of the HID specification. It still needs some patching of the usbhid kernel module, but in general is entirely functional in Wine, as long as "DisableInput" and "Enable SDL" are disabled in the Wine registry, and for the HIDRAW device is granted rw user access. TrueDrive is an application for controlling and fine tuning various parameters of the steering wheel (using HidD/HidP calls), which also includes real time animation of the steering wheel movement, buttons pushed, etc. The application is not used/needed during gameplay. The TrueDrive version used is 2020.10. The application can be downloaded from the manufacturer site: https://granitedevices.com/wiki/Simucube_2_True_Drive_releases The mentioned regression commit is the earliest in which the problem occurs. I've investigated further, and found that state->items.report_count in the parse_new_value_caps() function (hidclass.sys/descriptor.c) is not preserved properly. While being used for building the alternate value array it's set to 1, and since "Report Count" is a global item, reset_local_items() at the end of the function preserves its state. Thus if there are subsequent main items (Input, Output, etc.) with more than one usages, and with no "Report Count" specified in between, the parser would calculate wrong bit sizes, report len, etc. The particular problem was at the end of the descriptor. Here is an excerpt: /* Usage Page (FF00h), */ /* Usage (01h), */ /* Collection (Application), */ /* Usage (01h), */ /* Report ID (107), */ /* Report Size (8), */ /* Report Count (60), */ /* Logical Minimum (0), */ /* Logical Maximum (255), */ /* Output, */ /* Usage (01h), */ /* Report ID (108), */ /* Input, */ /* End Collection, */ The Input report 108 follows immediately the Output report 107, without Report Count specified in between. In our case parse_new_value_caps() would set erroneously Report Count to 1, after being called on the Output main item. Thus the next Input report size would be calculated wrongly. This is a vendor defined report, which they probably use in the process of recognizing the device. Since then the issue was mitigated a little bit with commit 7096c26a2e48089424fe90956c80c29617bce9f2, when button array value caps were introduced, which stopped modifying state->items.report_count if the parsed item is an array. The issue is still present in the new hidparse.sys (main.c), where the parsing code has been moved with commit a290c5bf7c9ddc92af56231693c6d8f00c3efd7b. It is present in Output report 2. Here is an excerpt: /* Usage (5Ah), */ /* Collection (Logical), */ /* Report ID (2), */ ... /* Report Count (2), */ /* Output (Variable), */ /* Usage (5Ch), */ /* Usage (5Eh), */ /* Unit (Seconds), */ /* Unit Exponent (-3), */ /* Logical Maximum (32767), */ /* Physical Maximum (32767), */ /* Report Size (16), */ /* Output (Variable), */ /* Physical Maximum (0), */ /* Unit, */ /* Unit Exponent (0), */ /* End Collection, */ Since the Output main items are variable, state->items.report_count is still being modified to 1. So the second Output item ends up with two usages, one 16 bit report, and one 0 bit report. This can be seen in the attached log file wine_6.18.log. For Output report 2, the RCnt for Usage 0x5E is 0. The following debug options were used for the log: WINEDEBUG=+timestamp,+pid,+hid,+hidp,+hid_report,+plugplay. The Wine build is 6.18-107-gbcdb28a563d. I've attached the Simucube 2 device descriptor in SC2_Descr.txt. Hope it can help as a real life example of a HID PID device with multiple ReportIDs. Attached also a patch which is fixing the issue (based on the latest master aa629c4c7225166f4ee46476d98702df2e142711). -- 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.

1 11

[Bug 51710] New: 3utools doesn't see iPad
by WineHQ Bugzilla Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=51710 Bug ID: 51710 Summary: 3utools doesn't see iPad Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aykutboray(a)gmail.com Distribution: --- Created attachment 70586 --> https://bugs.winehq.org/attachment.cgi?id=70586 Bug moment When I wanted to install new IPad OS software 3utools doesn't see my iPad it was connected to pc. -- 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.

1 5

[Bug 51987] New: Multiple GUI elements are not rendered when using a theme
by WineHQ Bugzilla Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=51987 Bug ID: 51987 Summary: Multiple GUI elements are not rendered when using a theme Product: Wine Version: 6.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 70975 --> https://bugs.winehq.org/attachment.cgi?id=70975 All broken This is a follow up to bug 51986. See the attached screenshot. -- 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.

1 11

[Bug 52028] New: Regression: Themed contents doesn't displays correctly in some themes
by WineHQ Bugzilla Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=52028 Bug ID: 52028 Summary: Regression: Themed contents doesn't displays correctly in some themes Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: joseskvolpe(a)gmail.com Distribution: --- Created attachment 71028 --> https://bugs.winehq.org/attachment.cgi?id=71028 good vs bad Regression test result: 7c9cacd47f969181624b2c5fafd7554188d7fa47 is the first bad commit commit 7c9cacd47f969181624b2c5fafd7554188d7fa47 Author: Zhiyi Zhang <zzhang(a)codeweavers.com> Date: Fri Nov 5 14:34:58 2021 +0800 comctl32/button: Correctly place parts for themed group boxes. Signed-off-by: Zhiyi Zhang <zzhang(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/comctl32/button.c | 49 +++++++++++++++++++++++++++---------------------- 1 file changed, 27 insertions(+), 22 deletions(-) Procedure: 1 - Open winecfg 2 -- Apply a theme that presents this issue I've used a modified theme from VLT by evgkursai. Original msstyles file presents this issue too. You can download it here: https://www.deviantart.com/evgkursai/art/VLT-2-0-VS-36103075 -- 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.

1 8

[Bug 52025] New: Custom color configuration is reseted if custom theme is applied
by WineHQ Bugzilla Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=52025 Bug ID: 52025 Summary: Custom color configuration is reseted if custom theme is applied Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uxtheme Assignee: wine-bugs(a)winehq.org Reporter: joseskvolpe(a)gmail.com Distribution: --- Regression result: 3762a11c81455edee65881702c5c26ae5d3081b3 is the first bad commit commit 3762a11c81455edee65881702c5c26ae5d3081b3 Author: Zhiyi Zhang <zzhang(a)codeweavers.com> Date: Thu Nov 4 14:44:47 2021 +0800 uxtheme: Fix loading a different theme when theming is on. When a theme is already active and a user tries to activate another theme, the new theme configuration should be written to the registry so that it's still in effect after a wine reboot. Fix a regression introduced in d290362. Signed-off-by: Zhiyi Zhang <zzhang(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/uxtheme/system.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) Wine 6.20 -> 6.21 Procedure: 1 - Open winecfg 2 - Apply a custom theme, theme used on this test was VLT by evgkursai: https://www.deviantart.com/evgkursai/art/VLT-2-0-VS-36103075 3 - Change any color and apply. On this test, i've changed "Selection Background" ("Fundo da Seleção" in portuguese-brazilian) color 4 - Close winecfg 5 - Open winecfg again -- 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.

1 11

[Bug 52205] New: Audio not working on any apps except winecfg
by WineHQ Bugzilla Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=52205 Bug ID: 52205 Summary: Audio not working on any apps except winecfg Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: khosraw.azizi(a)gmail.com Distribution: --- I am trying to run games using wine. I have so far tried 8-10 games and none of them output any audio. The audio in the winecfg app works and my backend is fine. I don't understand because these games worked with audio on my previous computer. This new computer however doesn't output the audio for those programs at all. Linux khosraw-archcraft-hp 5.15.7-zen1-1-zen #1 ZEN SMP PREEMPT Wed, 08 Dec 2021 14:33:18 +0000 x86_64 GNU/Linux khosraw(a)khosraw-archcraft-hp HP All-in-One 24-dp0xxx AMD Ryzen 5 4500U with Radeon Graphics (6) @ 2.375GHz AMD ATI 04:00.0 Renoir -- 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.

1 2

[Bug 32385] New: MSTSC (Remote Desktop) drawing issues
by wine-bugs＠winehq.org Dec. 13, 2021

Dec. 13, 2021

http://bugs.winehq.org/show_bug.cgi?id=32385 Bug #: 32385 Summary: MSTSC (Remote Desktop) drawing issues Product: Wine Version: 1.5.18 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: kenjiru.ro(a)gmail.com Classification: Unclassified Created attachment 42734 --> http://bugs.winehq.org/attachment.cgi?id=42734 Drawing issues. When it works, it has some drawing issues. Some windows are not drawn correctly at all, the title bars of some windows are not drawn. I see a lot of messages in the console, but I don't know which ones are to blame. I've attached the console output. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 3

[Bug 52113] New: Killing Floor 2 : Item Server not connectable
by WineHQ Bugzilla Dec. 13, 2021

Dec. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=52113 Bug ID: 52113 Summary: Killing Floor 2 : Item Server not connectable Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maycne.sonahoz(a)posteo.net Distribution: --- Overview: In Killing Floor 2, the Item Server cannot be reached. In consequence, neither the Inventory nor the Store are available from within the game. Steps to Reproduce: 1) Launch Killing Floor 2. 2) In the main menu, an icon should tell the connectivity with the Item Server. That icon shows the server is unreachable. 3) Access the Inventory tab. It should be filled with your custom items, but it always shows empty. 4) Access the Store tab. It should be filled with store offers, but it always shows empty. Build Date & Hardware: Manjaro stable - Xfce - kernel 5.10.79-1 - 2021-11-16 The issue has been happening from a long time now. As for today's reference: - Failed to reach the steps to reproduce the issue with Development Wine: - Development Wine built locally from source - Steam (for Windows) installed through Wine - Steam refuses to install Killing Floor 2 : "invalid platform" - Issue reproduced with: - Steam (for Linux) Beta - Proton-6.21-GE-2 (based on Wine 6.21) Additional Builds and Platforms: Manjaro stable - Xfce - kernel 5.10.79-1 - 2021-11-16 The issue does not (yet) reproduce with: - Steam (for Linux) Beta - Proton 6.3-8 (based on Wine 6.3) -- 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.

1 2