January 2019 - Wine-bugs - list.winehq.org

[Bug 46251] New: some (all?) crinkler compressed executables crash because they parse in-memory DLL export tables
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=46251 Bug ID: 46251 Summary: some (all?) crinkler compressed executables crash because they parse in-memory DLL export tables Product: Wine Version: 3.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: p2(a)psychaos.be Distribution: --- Created attachment 62950 --> https://bugs.winehq.org/attachment.cgi?id=62950 crash dump and disassembly of decompressor and symbol resolver Some crinkler compressed executables crash when building the imported symbol table. The routine which does this relies on parsing the in-memory copy of KERNEL32.DLL first to retrieve the address for LoadModuleA. This is later used to load other DLLs. Symbol name matching is done using a hash function. The executable only stores the hashes of the symbols it wants to import. For each symbol has in the executable, the symbol resolver routine iterates over all exported symbol names of the DLL and stores the symbol address if the hashes match. The symbol resolver routine crashes because it seems the in-memory copy of KERNEL32.DLL does not have a exported symbol names table. Attached: winhello_asm.txt: the crash dump and a dissassembly of both the decompressor and the symbol resolver. winhello.zip: source code for the trivial program, obj file, normally linked executable (winhello.exe), crinkler linked executable (winhello_cr.exe)_and the msvcrt.lib as recommended by the crinkler manual. Toolchain used was VS2013 community edition. crinker can be found here: http://crinkler.net/ -- 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 39815] New: BitComet 1.4 crashed on launch
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=39815 Bug ID: 39815 Summary: BitComet 1.4 crashed on launch Product: Wine-staging Version: 1.8-rc4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: litimetal(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 53151 --> https://bugs.winehq.org/attachment.cgi?id=53151 terminal_output.txt 0. Download BitComet(a BitTorrent client) from http://www.bitcomet.com/ $ sha1sum BitComet_1.40_x86_setup.exe 47ebec6261ec6d06c058fc10260016b889478aa5 BitComet_1.40_x86_setup.exe 1. wine BitComet_1.40_x86_setup.exe You can choose the installer's language 2. cd ~/.wine/drive_c/Program Files/BitComet wine BitComet.exe With wine, it works (mostly well) With wine-staging, it crashed at start up -- 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 9

[Bug 45599] New: Support for FILE_FLAG_WRITE_THROUGH in CreateFile breaks Wargaming.net Game Center
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45599 Bug ID: 45599 Summary: Support for FILE_FLAG_WRITE_THROUGH in CreateFile breaks Wargaming.net Game Center Product: Wine-staging Version: unspecified Hardware: x86 URL: http://redirect.wargaming.net/WGC/Wargaming_Game_Cente r_Install_TWA_EU.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- The program closes with the message "Unable to launch the application because of critical errors." Guilty patch is "ml-patches/0027-kernel32-Add-support-for-FILE_FLAG_WRITE_THROUGH-to-.patch" - reverting it fixes the issue. To test just run the installer and then run "drive_c/Program Files/Wargaming.net/GameCenter/wgc.exe" in a fresh(!) WINEPREFIX. Running the program without the guilty patch, and then with the guilty patch again seems to fix the issue, also. -- 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 46052] New: Spellforce: regression: black square around mouse pointer
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=46052 Bug ID: 46052 Summary: Spellforce: regression: black square around mouse pointer Product: Wine-staging Version: 3.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: idarktemplar(a)mail.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 62637 --> https://bugs.winehq.org/attachment.cgi?id=62637 Screenshot.jpeg After upgrading from wine-staging 3.17 to 3.18, when running Spellforce, I'm getting black square around mouse cursor. The cursor itself is visible, but it looks like a texture transparency issue. Black square appears even in main menu and during starting movies, and it is present during actual gameplay. If I disable 'Enable CSMT for better graphics performance (deprecated)' in winecfg, there is a chance that black square doesn't appear right from start, but it may appear on some cursor change and disappear later, but it's still pretty reproducible for me. I'm reproducing it with high chance by hovering over gates to another map. I've tried running wine-staging 3.17, and couldn't reproduce issue. I've also tried running wine-vanilla 3.18 and couldn't reproduce issue either. Native libraries: from d3dx9_24 till d3dx9_43. I've tried clean wine prefix, issue remained. Also, I've compared output of wine, and for wine-staging-3.18 I'm getting a lot of following lines: 003c:fixme:d3d:surface_cpu_blt Unsupported flags 0x80000000. I didn't get such lines for wine-staging-3.17 or wine-vanilla-3.18. OS: Gentoo Linux x86_64. Video driver: nvidia-drivers-387.34 -- 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 9

[Bug 43891] New: RAGE (Steam) crashes after start in wine-staging
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=43891 Bug ID: 43891 Summary: RAGE (Steam) crashes after start in wine-staging Product: Wine-staging Version: unspecified Hardware: x86 URL: http://store.steampowered.com/app/9200/RAGE/ OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59507 --> https://bugs.winehq.org/attachment.cgi?id=59507 terminal output The game starts properly in the development version of Wine (2.19), but crashes in the Staging version (tested with the following Staging versions: 2.10, 2.14, 2.18 and with current Staging-git). Reproduced the crash with the following Nvidia driver versions: 378.13, 384.59 and with current 387.12. With nouveau and Mesa 17.2.2 the game crashes in a different way (both in Staging and the development version), that's probably bug #38969. The patch in Staging which causes the problem: https://github.com/wine-compholio/wine-staging/blob/master/patches/opengl32… Arch Linux x86_64 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 387.12 -- 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 45875] New: Desperados: Jerky mouse cursor ingame, ok in menu ( fine in wine-vanilla)
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45875 Bug ID: 45875 Summary: Desperados: Jerky mouse cursor ingame, ok in menu (fine in wine-vanilla) Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: phaidros(a)gmx.at CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- With wine-staging, I get jumping mouse cursor in the game Desperados. The cursor seems to jump back uncontrollably, which makes the game unplayable. Interestingly, the cursor works fine in the game main menu. It also works in the im-game menu (pressing Esc in the game), only in the actual game where the characters are controlled with the mouse it shows the jerky behaviour. I get this with wine-staging 3.13, 3.14, 3.15 and 3.16. Wine-vanilla 3.0, 3.2, and 3.16 does not have this problem, here the mouse works fine in the menu and in-game. -- 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 12

[Bug 40028] New: Tumblebugs 2 crashes with wined3d-csmt.dll, works with wined3d.dll
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=40028 Bug ID: 40028 Summary: Tumblebugs 2 crashes with wined3d-csmt.dll, works with wined3d.dll Product: Wine-staging Version: 1.7.54 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Formerly this game was an indicator for DXTn textures support. It uses DXT5 textures for bugs. So this game some time worked with wine-staging? Not now. Enable redirect wined3d-csmt.dll ~~~~ fixme:winediag:start_process Wine Staging 1.9.1 is a testing version containing experimental patches. fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll" fixme:winediag:wined3d_dll_init Experimental wined3d CSMT feature is currently disabled. fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled err:winediag:init_driver_info Invalid GPU override 1002:6740 specified, ignoring. fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a ... wine: Unhandled exception 0x40000015 in thread 29 at address 0x280bb5d (thread 0029), starting debugger... ~~~ disable ~~~~ fixme:winediag:start_process Wine Staging 1.9.1 is a testing version containing experimental patches. fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling back to byte mode. fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled err:winediag:init_driver_info Invalid GPU override 1002:6740 specified, ignoring. fixme:ddraw:ddraw7_Initialize Ignoring guid {aeb2cdd4-6e41-43ea-941c-8361cc760781}. fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #3: fixme:d3d_shader:print_glsl_info_log WARNING: Could not find vertex shader attribute 'vs_in2' to match BindAttributeLocation request. fixme:ddraw:ddraw_surface7_Flip Ignoring flags 0x1. fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #5: fixme:d3d_shader:print_glsl_info_log WARNING: Could not find vertex shader attribute 'vs_in2' to match BindAttributeLocation request. err:d3d_surface:surface_convert_format Failed to create a destination surface for conversion. err:d3d_surface:surface_convert_format Failed to create a destination surface for conversion. err:d3d_surface:surface_convert_format Failed to create a destination surface for conversion. err:d3d_surface:surface_convert_format Failed to create a destination surface for conversion. ~~~~ To check if this is my mistake I download ready-to-use WineStage-1.9.1 binary. Tested also with wine-staging-1.7.54. Tested wine Crossover 15.0 Same result. The game crashes. It works with main WineHQ with black insects and balls. -- 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 46104] New: winepulse-PulseAudio_Support patch cause application to hang with native dsound.dll
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=46104 Bug ID: 46104 Summary: winepulse-PulseAudio_Support patch cause application to hang with native dsound.dll Product: Wine-staging Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hi. Recently I wanted to play to some old games that were using DirectMusic. In particular "Imperivm Great Battles of Rome" So following the procedures I installed the directmusic component and the native dsound.dll However when I tried the game I was encountered by an hanged application. (the application opened it's window and rendered the cursor, but nothing else) I was on wine-staging as I have some games that require staging patches. However as I recalled this game worked before, so I tried vanilla wine. It worked almost flawless (encountering bug Bug 44540 with quartz.dll as native). Then I tried with older wine-staging version. I started with the wine-staging 3.3 that was the older one in my pacman package cache, and worked flawless. I then discovered that the first bad wine-staging release is the 3.13 release. After checking the patch modified between the 3.12 and 3.13 releases, I found that if I compile wine-staging from source without applying the winepulse-PulseAudio_Support the issue disappears. Unfortunatly Imperivm GBR doesn't have an aviable demo, but recently an udated version was released on steam, and you can ask for a key at FX Interactive for free. Check the FAQ in the Imperium World forum on Discord. Normal Log is totally unhelpful as the only thing it give is a: 0009:fixme:thread:create_user_shared_data_thread Creating user shared data update thread. Two others affected application are: Rise of Nation Rise of Nation Throne and Patriots Others bug associated with winepulse-PulseAudio_Support and 3.13 Release (potentially not duplicates): Bug 45582 - Bug 45623 - Bug 45502 -- 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 12

[Bug 40060] New: Crash dialog button unclickable
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=40060 Bug ID: 40060 Summary: Crash dialog button unclickable Product: Wine-staging Version: 1.9.2 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Created attachment 53538 --> https://bugs.winehq.org/attachment.cgi?id=53538 The windows in question If a game crashes (for example elevated_1024x768.exe) then dialog windows appeared with two buttons "Show details" and "Close". These buttons are unclickable because of patch https://github.com/wine-compholio/wine-staging/blob/master/patches/user32-M… Reverting the patch resolves the issue. -- 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 12

[Bug 45856] New: wine stuck installing python in silent mode
by wine-bugs＠winehq.org 31 Mar '19

31 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=45856 Bug ID: 45856 Summary: wine stuck installing python in silent mode Product: Wine-staging Version: 3.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sbonazzo(a)redhat.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: Fedora On Fedora 28: download https://www.python.org/ftp/python/2.7.14/python-2.7.14.msi $ wine msiexec /i /tmp/python-2.7.14.msi /qn ADDLOCAL=ALL 000b:fixme:winediag:start_process Wine Staging 3.16 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 0028:fixme:dwmapi:DwmIsCompositionEnabled 0x6dc825d4 002d:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69ec7e28, context 0x91e480, init_notify 0, handle 0x11dfa10): stub 003f:fixme:dwmapi:DwmIsCompositionEnabled 0x6dc825d4 0041:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69ec7e28, context 0x91e480, init_notify 0, handle 0x11dfa10): stub wine: configuration in '/home/sbonazzo/.wine' has been updated. 0009:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet 0053:err:msiexec:custom_action_server Failed to create custom action server pipe: 2 wine get stuck here and doesn't complete the silent install. Reproducible 100% with wine 3.14-1.fc28 and 3.16-1.fc28 Worked fine in wine 3.8-1.fc28 (https://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc28…) -- 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 12