September 2016 - Wine-bugs - list.winehq.org

[Bug 16666] New: wine segfaults on launch
by wine-bugs＠winehq.org 24 Oct '21

24 Oct '21

http://bugs.winehq.org/show_bug.cgi?id=16666 Summary: wine segfaults on launch Product: Wine Version: 1.1.11 Platform: PC OS/Version: OpenBSD Status: NEW Keywords: patch, source Severity: critical Priority: P2 Component: build-env AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Created an attachment (id=18290) --> (http://bugs.winehq.org/attachment.cgi?id=18290) core dump Now for the biggest bug :-) Wine segfaults on launch of any program. Even 'wine --version' crashes. I've got this patch in place (from openbsd's port): diff --git a/loader/pthread.c b/loader/pthread.c index 4c0c892..e7f6479 100644 --- a/loader/pthread.c +++ b/loader/pthread.c @@ -96,6 +96,12 @@ static void init_thread( struct wine_pthread_thread_info *info ) /* if base is too large assume it's the top of the stack instead */ if ((char *)info->stack_base > &dummy) info->stack_base = (char *)info->stack_base - info->stack_size; +#elif defined(__OpenBSD__) + stack_t stack; + if (pthread_stackseg_np(pthread_self(), &stack) != 0) + abort (); + info->stack_base = (char *)stack.ss_sp - stack.ss_size; + info->stack_size = stack.ss_size; #else /* assume that the stack allocation is page aligned */ char dummy; @@ -163,6 +169,8 @@ static void init_current_teb( struct wine_pthread_thread_info *info ) info->pid = getpid(); #ifdef __sun info->tid = pthread_self(); /* this should return the lwp id on solaris */ +#elif defined(__OpenBSD__) + info->tid = pthread_self(); #elif defined(__APPLE__) info->tid = mach_thread_self(); #elif defined(__FreeBSD__) Though, it still segfaults without it. wine-pthread.core attached -- 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 20

[Bug 30600] New: Emergency 3 crash with page fault on read access to 0x00000000 in 32-bit code (0x100ac010)
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

http://bugs.winehq.org/show_bug.cgi?id=30600 Bug #: 30600 Summary: Emergency 3 crash with page fault on read access to 0x00000000 in 32-bit code (0x100ac010) Product: Wine Version: 1.5.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: linuxcobra(a)gmx.de Classification: Unclassified Created attachment 40041 --> http://bugs.winehq.org/attachment.cgi?id=40041 Backtrace-output when i install this Game under wine, the install works, but when i will start the game, will not work. via original Windows XP / ME ( both tested) : no problems -- 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

[Bug 36796] New: Mozilla Firefox 13.0 crashes on startup if run in Windows Vista+ mode (D3D10CreateEffectFromMemory needs more complete Direct3D 10 DXBC parser)
by wine-bugs＠winehq.org 22 Oct '21

22 Oct '21

https://bugs.winehq.org/show_bug.cgi?id=36796 Bug ID: 36796 Summary: Mozilla Firefox 13.0 crashes on startup if run in Windows Vista+ mode (D3D10CreateEffectFromMemory needs more complete Direct3D 10 DXBC parser) Product: Wine Version: 1.7.20 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3dx10 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, Henri suggested that Mozilla Firefox in Vista+ mode might be a good candidate to help implementing missing/incomplete DX10/D2D API (https://bugs.winehq.org/show_bug.cgi?id=30966#c5) Running the browser results in crash: --- snip --- $ pwd /home/focht/.wine/drive_c/Program Files/Mozilla Firefox $ wine ./firefox.exe ... fixme:win:EnumDisplayDevicesW ((null),0,0x33c030,0x00000000), stub! fixme:d3d10:D3D10CreateDevice1 Ignoring feature level D3D10_FEATURE_LEVEL_10_0. fixme:dxgi:dxgi_device_init Ignoring adapter type. fixme:win:EnumDisplayDevicesW ((null),0,0x33c030,0x00000000), stub! fixme:d3d10:D3D10CreateDevice1 Ignoring feature level D3D10_FEATURE_LEVEL_10_1. fixme:dxgi:dxgi_device_init Ignoring adapter type. fixme:d2d:d2d_factory_init Ignoring factory type and options. fixme:d3d10:D3D10CreateEffectFromMemory data 0x15d07b0, data_size 4833, flags 0, device 0x143cb0, effect_pool (nil), effect 0x428b710 stub! fixme:d3d10:skip_dword_unknown Skipping 4 unknown DWORDs (DXBC header): fixme:d3d10:skip_dword_unknown 0x5af68935 fixme:d3d10:skip_dword_unknown 0x3e88ff30 fixme:d3d10:skip_dword_unknown 0x96a39662 fixme:d3d10:skip_dword_unknown 0x35cbba93 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (DXBC header): fixme:d3d10:skip_dword_unknown 0x00000001 fixme:d3d10:parse_fx10 Unknown 0: 0 fixme:d3d10:parse_fx10 Unknown 1: 0 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (local buffer): fixme:d3d10:skip_dword_unknown 0xffffffff fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (variable): fixme:d3d10:skip_dword_unknown 0x00000000 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (variable): fixme:d3d10:skip_dword_unknown 0x00000000 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (variable): fixme:d3d10:skip_dword_unknown 0x00000000 fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (local variable): fixme:d3d10:skip_dword_unknown 0xffffffff fixme:d3d10:skip_dword_unknown Skipping 1 unknown DWORDs (local variable): fixme:d3d10:skip_dword_unknown 0xffffffff ... fixme:d3d10:parse_fx10_state_group Failed to find property info for property 0x37. err:d3d10:parse_fx10_local_variable Failed to read property list. err:d3d10:D3D10CreateEffectFromMemory Failed to parse effect fixme:dbghelp:elf_search_auxv can't find symbol in module err:seh:raise_exception Exception frame is not in stack limits => unable to dispatch exception. --- snip --- $ sha1sum Firefox\ Setup\ 13.0.exe 9002a5ae41ef54edf378506ae80c934b7e8df7dc Firefox Setup 13.0.exe $ du -sh Firefox\ Setup\ 13.0.exe 16M Firefox Setup 13.0.exe $ wine --version wine-1.7.20-122-gd2d62cf Regards -- 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 12

[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 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 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 21564] New: warning forever ignores keyboard input after losing/regaining focus
by wine-bugs＠winehq.org 21 Oct '21

21 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 21 Oct '21

21 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