June 2017 - Wine-bugs - list.winehq.org

[Bug 41317] New: WOLF RPG Editor (Game.exe): Arrow keys don' t work properly when gamepad is connected
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=41317 Bug ID: 41317 Summary: WOLF RPG Editor (Game.exe): Arrow keys don't work properly when gamepad is connected Product: Wine Version: 1.9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: kakurasan(a)gmail.com Regression SHA1: c126b21a34be008534e4fbd2a0f8bb8ea08c6c2b Distribution: --- Created attachment 55651 --> https://bugs.winehq.org/attachment.cgi?id=55651 Input test program which uses DX Library (source) When gamepad is connected, the cursor or character moves automatically and arrow keys doesn't work properly. Workaround: Disable all gamepads using joy.cpl, or use native dinput.dll Note: WOLF RPG Editor uses a DirectX wrapper library called "DX Library" (open source). Downloads (Japanese): * WOLF RPG Editor: http://www.silversecond.com/WolfRPGEditor/Download.html * DX Library: http://dxlib.o.oo7.jp/ ----- Result of regression testing ----- c126b21a34be008534e4fbd2a0f8bb8ea08c6c2b is the first bad commit commit c126b21a34be008534e4fbd2a0f8bb8ea08c6c2b Author: Andrew Nguyen <anguyen(a)codeweavers.com> Date: Tue Jul 5 07:19:17 2011 -0500 dinput: Extract the DirectInput instance creation and initialization in DirectInputCreateEx to separate functions. :040000 040000 f904caf8d290195557d1c2733d12288d8b4f9cf4 02e3e0e5a1ad1ee2fbb02e91bb09f093766c0e0e M dlls -- 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 23

[Bug 42434] New: Gamepad listed twice
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=42434 Bug ID: 42434 Summary: Gamepad listed twice Product: Wine Version: 2.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: gabriel.corona(a)enst-bretagne.fr Distribution: --- Created attachment 57270 --> https://bugs.winehq.org/attachment.cgi?id=57270 Example program enumerating the same device twice. The gamepads seem to be listed twice by DiectInput. The problem manifests itself in Lego games (eg. "Lego the Hobbit" and "Lego Star Wars Episode 7"). The same gamepad is exposed twice and is thus used for both players: the same gamepad controls both players and it is not possible to play single player. A quick workaround is to use `rm /dev/input/js*`. AFAIU, the problem is that both the /dev/input/eventX and the /dev/input/jsX device of the gamepad are enumerated. You'll find in attachement a program which demonstrates the issue: Thrustmaster Dual Trigger 3-in-1 (event) ({B323044F-0000-0000-0000-504944564944}) -- Thrustmaster Dual Trigger 3-in-1 (event) ({9E573EDA-7734-11D2-8D4A-23903FB6BDF7}) Thrustmaster Dual Trigger 3-in-1 (js) ({B323044F-0000-0000-0000-504944564944}) -- Thrustmaster Dual Trigger 3-in-1 (js) ({9E573ED9-7734-0000-8D4A-23903FB6BDF7}) Using Wine 2.1 on Debian testing with Linux 4.9.0. -- 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 6

[Bug 41080] New: Need For Speed Most Wanted 2005 not working after upgrade from Ubuntu 14.04 to 16.04
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=41080 Bug ID: 41080 Summary: Need For Speed Most Wanted 2005 not working after upgrade from Ubuntu 14.04 to 16.04 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: naheelazawy(a)gmail.com Distribution: --- Created attachment 55265 --> https://bugs.winehq.org/attachment.cgi?id=55265 backtrace The game was working great on Ubuntu 14.04 but now after upgrading to 16.04 it just doesn't work. And by the way, I tried various versions of wine and nothing worked so far. -- 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 43

[Bug 34297] New: Allow reconnecting to disconnected joysticks
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

http://bugs.winehq.org/show_bug.cgi?id=34297 Bug #: 34297 Summary: Allow reconnecting to disconnected joysticks Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: achurch+wine(a)achurch.org Classification: Unclassified Created attachment 45660 --> http://bugs.winehq.org/attachment.cgi?id=45660 Proof-of-concept patch Currently, if a joystick is disconnected and then reconnected (because the cable is pulled out, for example), Wine acts as though the joystick is present but stuck at the last state it reported, and it fails to report any subsequent changes in device state, which is an arguably suboptimal user experience. The attached patch (against 1.7.0) changes the Linux evdev driver to attempt to reopen a joystick device after a read fails. This patch uses the simple heuristic of "if it's on the same device file and has the same name, it's the same joystick", which means (1) it won't reconnect if the device file changes and (2) it could falsely reconnect if there are multiple input devices with the same name, but it works for simple circumstances. Naturally, one could iterate over all possible input devices to try and find the device, but that could be fairly expensive to do on every poll operation, and it would probably involve concurrency issues relating to checking whether the device is already known as a different joystick. In the long run, it might be better to monitor the /dev/input directory for added and removed devices (perhaps using inotify) and use those events to handle reconnection. -- 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 10

[Bug 42695] New: PoE fail to start when launching with dx11 enabled
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=42695 Bug ID: 42695 Summary: PoE fail to start when launching with dx11 enabled Product: Wine-staging Version: 2.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gufideg(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 57663 --> https://bugs.winehq.org/attachment.cgi?id=57663 console output I get an error from Poe that says: "Failed to retrive IDXGIFactory from adapter": In source code file: ..\Device \D3D11\DeviceD3D11.cpp at line 336, Processing file: Failed to retrive IDXGIFactory from adapter Error: E_NOINTERFACE Description: Message: Then I click OK and the game closes. Works nicely with dx9 and dx9 ex -- 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 69

[Bug 38696] New: Messy screen in DxTex.exe
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=38696 Bug ID: 38696 Summary: Messy screen in DxTex.exe Product: Wine Version: 1.7.44 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Created attachment 51621 --> https://bugs.winehq.org/attachment.cgi?id=51621 messy screen with wine-hq Steps to reproduce: Start DxTex.exe that is included in DirectxSDK available for download from https://www.microsoft.com/en-us/download/details.aspx?id=6812 1. New texture. Settings default 2. Open onto this surface and choose any graphic file. 3. see... With wine-stage the screen is good. To be sure: I used unmodified sources on wine-hq and wine-stage. There are no my patches at all. All settings are the same, just changed wine prefix. The logs difference is probably in this line ---- fixme:win:EnumDisplayDevicesW ((null),0,0x33f42c,0x00000000), stub! ---- -- 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 19

[Bug 40658] New: Joystick POW hat switch rotated for JOYDEVDRIVER=(js) while JOYDEVDRIVER=(event) is Ok
by wine-bugs＠winehq.org 21 Oct '21

21 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=40658 Bug ID: 40658 Summary: Joystick POW hat switch rotated for JOYDEVDRIVER=(js) while JOYDEVDRIVER=(event) is Ok Product: Wine Version: 1.9.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: otty(a)gmx.net Distribution: --- I have a Saitek AV8R-01 joystick with a POV hat switch. When using the JOYDEVDRIVER=(event) device (dinput/joystick_linuxinput.c), the orientation is Ok both in the Wine Control Panel (control.exe) Joystick test POV area and in the games, i.e when moving the hat switch horizontally to the right the indicator moves towards the right, when moving the hat switch vertically up, the indicator moves up. Hoever the JOYDEVDRIVER=(js) device (dinput/joystick_linux.c) has its orientation mixed up: * when moving the hat switch horizontally to the right the indicator moves down. * when moving the hat switch vertically up, the indicator moves left. This happens on wine-1.9.9 on Ubuntu 14.04 (LTS) installed from http://ppa.launchpad.net/wine/wine-builds/ubuntu trusty main, but is also present in earlier versions, e.g. 1.6.1 Unfortunately I need to use the (js) device as I cannot get the game to recognise the rudder and thrust axes with the (event) device. (BTW, does the (event) device recognize the [HKEY_CURRENT_USER\Software\Wine\DirectInput] registry key in the same way as teh (js) device?) BR, -- 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 37

[Bug 42191] New: Diablo 3 2.4.3 was unable to initialize D3D
by wine-bugs＠winehq.org 20 Oct '21

20 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=42191 Bug ID: 42191 Summary: Diablo 3 2.4.3 was unable to initialize D3D Product: Wine Version: 2.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: nfamail(a)gmail.com Distribution: --- Created attachment 56824 --> https://bugs.winehq.org/attachment.cgi?id=56824 Diablo 3 Debug Log When I try to run the game in 64 bit after that I get the grey screen and the error creating d3d. Click ok a couple of times and it then gives you the option to retry/cancel and will do nothing. If you go to the battle.net app and go to game settings and change it to "Open game with 32-bit version instead" it will open just fine... Winehq 2.0-rc4 Ubuntu 16.04 64bit (latest updates) Intel® Core™ i7-4510U CPU @ 2.00GHz × 4 GeForce 840M/PCIe/SSE2 Battle.net 1.6.0.8265 (2.9.2.5362) Diablo 3 2.4.3.42934 -- 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 41

[Bug 21564] New: warning forever ignores keyboard input after losing/regaining focus
by wine-bugs＠winehq.org 20 Oct '21

20 Oct '21

http://bugs.winehq.org/show_bug.cgi?id=21564 Summary: warning forever ignores keyboard input after losing/regaining focus Product: Wine Version: 1.1.37 Platform: x86 URL: http://www18.big.or.jp/~hikoza/Prod/index_e.html OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: madewokherd(a)gmail.com Steps to reproduce: * Install Warning Forever from the linked website. * Start the program by running c:\wf\wf.exe. (The installer does not create a shortcut. This is the same on Windows.) * Select "Window mode". * Verify that the 'z' key can be used to make selections in the menu. * Switch to another window. * Switch back to Warning Forever window. * Verify that keyboard input no longer works. -- 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 22

[Bug 22369] New: A child window without WS_EX_MDICHILD style should not be tiled by the WM_MDITILE message.
by wine-bugs＠winehq.org 20 Oct '21

20 Oct '21

http://bugs.winehq.org/show_bug.cgi?id=22369 Summary: A child window without WS_EX_MDICHILD style should not be tiled by the WM_MDITILE message. Product: Wine Version: unspecified Platform: All OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: a.m.winehq(a)gmail.com In user32/mdi.c -> MDITile -> #L763(wine-1.1.42) for-loop "remove all the windows we don't want", the windows without WS_EX_MDICHILD window style should be also removed from win_array. MDICascade is also. -- 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 37