wine-bugs October 2021

wine-bugs@winehq.org

1 participants
4983 discussions

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

13 Dec '21

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 13 Dec '21

13 Dec '21

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 51934] New: Battle.Net after login bug
by WineHQ Bugzilla 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=51934 Bug ID: 51934 Summary: Battle.Net after login bug Product: Wine Version: 6.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ptg76(a)ukr.net Distribution: --- Created attachment 70899 --> https://bugs.winehq.org/attachment.cgi?id=70899 backtrace log Hi, All! After updates, I cannot log in to Battle.Net nor the Starcraft game directly. After entering username and password it falls into repeating "crash"(?). I've attached the backtrace log file. Any ideas, workarounds, something? Sincerely, Peter -- 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 13

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

13 Dec '21

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 29503] New: Stucuk's Setup System patcher often fails with 'Canvas does not allow drawing' error message
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=29503 Bug #: 29503 Summary: Stucuk's Setup System patcher often fails with 'Canvas does not allow drawing' error message Product: Wine Version: 1.3.36 Platform: x86 URL: http://www.fileplanet.com/207230/200000/fileinfo/Dark- Horizon-Patch-v1.0.6.1 OS/Version: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 38206 --> http://bugs.winehq.org/attachment.cgi?id=38206 screenshot (patcher running in virtual desktop) The installer of the patch made for Dark Horizon uses a Stucuk's Setup System according to the file properties. The installer of the community patch made for Original War also uses this kind of patcher, sharing the same problem. The patcher for Dark Horizon consists of nearly 3000 small files. The installation process doesn't take long (15-20 seconds). At some point during the install process, the patcher is interrupted with an error message: 'Setup Thread Error: Canvas does not allow drawing', and the installer quits prematurely. This happens fairly often (maybe 8 times out of 10 attempts), but sometimes the patcher finishes the job without erroring out. Before the error message pops up, text which normally appears inside the installer window also printed and overwritten several hundreds of times in the upper left corner of the screen (see attached screenshot). This happens both in virtual desktop mode and in full-screen. To reproduce the problem with the patcher made for Dark Horizon you don't have to download the demo for the game; the patch can be installed alone in a selected directory anywhere inside a wineprefix. -- 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 5

[Bug 41615] New: Max Payne 1 and 2 crash using glsl=enabled
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=41615 Bug ID: 41615 Summary: Max Payne 1 and 2 crash using glsl=enabled Product: Wine Version: 1.9.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- Created attachment 55965 --> https://bugs.winehq.org/attachment.cgi?id=55965 backtrace-max-payne-1-glsl Max Payne 1 and 2 crash using glsl=enabled during 1st chapter Both crash during 1st chapter however if use glsl=disabled in wine register works stable both games pass 1st chapter with crashes System Specs Using in Tests Nvidia Drivers 375.10 (run package from nvidia drivers homepage) Xubuntu 16.04 64Bit - Kernel 4.4.0-44 generic (ubuntu mainline) - CPUFreq: Performance CPU: INTEL Pentium G3258 (Haswell 22nm) 4.1Ghz + Artic Cooling Alpine 11 Plus MEMORY: 8GB DDR3 1333 (2x4) Patriot value (dual channel: 21.3 gb/s) GPU: Zotac Nvidia Geforce GT630 (GK208 28nm: 384 Shaders / 8 ROPS) Zone Edition Passive Cooling 2GB DDR3 1800Mhz 64Bit (14.4Gb/s) MAINBOARD: MSI H81M E33 -- 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 17

[Bug 38183] New: King of Dragon Pass crashes when loading a saved game
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=38183 Bug ID: 38183 Summary: King of Dragon Pass crashes when loading a saved game Product: Wine Version: 1.7.38 Hardware: x86 URL: http://a-sharp.com/files/KoDP-Tour.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- Created attachment 50954 --> https://bugs.winehq.org/attachment.cgi?id=50954 terminal output Loading a previously saved game at the title screen works properly. Loading a saved game while you are in-game results in a crash. Tested with the GOG version. The crash can be reproduced with the demo/tour version as well. The same problem in Wine 1.2.3/1.4.1/1.6.2/1.7.38. Steps to reproduce the problem with the demo version: Start the installed demo with tour.exe. Click on the highlighted <Tour>, <Skip all>, <Play> buttons. Click the button right next to <Proceed> in the lower right corner. Click <Save>...the game is saved. Now click <Restore> in the options menu and select the previously saved game. The game is loaded without errors but if you click <Proceed> the game crashes. The demo version doesn't allow to load a saved game from the title screen. KoDP-Tour.exe sha1: 445443bd6365f71257abfe0809e9a1932791d1ed -- 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 5

[Bug 26898] New: wine does not show save game screenshots
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=26898 Summary: wine does not show save game screenshots Product: Wine Version: 1.3.17 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: vaniaz(a)msn.com Screenshots are saved in dds format. When saving game, I get the following in console fixme:d3d_surface:surface_convert_format Cannot find a conversion function from format WINED3DFMT_B8G8R8A8_UNORM to WINED3DFMT_DXT1. Saved screenshot is completely black. -- 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 34

[Bug 41653] New: The Banner Saga 2 GOG (adobe air) flickering on Wine-staging
by wine-bugs＠winehq.org 13 Dec '21

13 Dec '21

https://bugs.winehq.org/show_bug.cgi?id=41653 Bug ID: 41653 Summary: The Banner Saga 2 GOG (adobe air) flickering on Wine-staging Product: Wine-staging Version: 1.9.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: donanykey(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 56035 --> https://bugs.winehq.org/attachment.cgi?id=56035 Video of flickering picture Dedicating separate bug from https://bugs.winehq.org/show_bug.cgi?id=41635 for Wine-staging. The game works in plain Wine (1.9.21), but with very poor frame rate performance, while with staging - it's much more responsive, but the picture is flickering. Video and log to be attached -- 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 25

[Bug 33309] New: No keyboard input in Slender: The Arrival
by wine-bugs＠winehq.org 12 Dec '21

12 Dec '21

http://bugs.winehq.org/show_bug.cgi?id=33309 Bug #: 33309 Summary: No keyboard input in Slender: The Arrival Product: Wine Version: 1.5.27 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: 6tsukiyami9(a)gmail.com Classification: Unclassified The title says all about it: the keyboard doesn't work at all in Slender: The Arrival. I can't even try the game itself because I can't get enter the license key and get to the main menu. I guess this may be a clue: fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. fixme:win:RegisterDeviceNotificationW (hwnd=0x1006a, filter=0x33fc6c,flags=0x00000000) returns a fake device notification handle! fixme:win:RegisterRawInputDevices Unhandled flags 0x100 for device 0. I'm attaching a full log with WINEDEBUG=-all,+keyboard,+key,+dinput,+message -- 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 15

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs October 2021