March 2019 - Wine-Bugs - list.winehq.org

[Bug 46806] New: The Sims has invisible sims
by wine-bugs＠winehq.org March 31, 2019

March 31, 2019

https://bugs.winehq.org/show_bug.cgi?id=46806 Bug ID: 46806 Summary: The Sims has invisible sims Product: Wine Version: 4.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: haakobja(a)gmail.com Distribution: --- Created attachment 63830 --> https://bugs.winehq.org/attachment.cgi?id=63830 2019-03-09:d3d trace log Hi, I tried The Sims with Wine-staging 4.3, but it shows no sims. The enviroment, like the rooms in the house, furniture, trees etc. shows up, but no sims. The sims in game showed up in Wine-staging 4.2, even though their faces was not showing correctly. -- 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 17

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

March 31, 2019

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 March 31, 2019

March 31, 2019

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 46599] New: GNUTLS_PK_ECDSA not found in recent gnutls.h
by wine-bugs＠winehq.org March 31, 2019

March 31, 2019

https://bugs.winehq.org/show_bug.cgi?id=46599 Bug ID: 46599 Summary: GNUTLS_PK_ECDSA not found in recent gnutls.h Product: Wine Version: 4.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Distribution: --- Compilation in macOS 10.13.6 with Xcode10.1 and recent gnutls library installed by MacPort failed with claim that GNUTLS_PK_ECDSA is undefined. dll/bcrypt/gnutls.c ~~~ #if GNUTLS_VERSION_MAJOR < 3 #define GNUTLS_CIPHER_AES_192_CBC 92 #define GNUTLS_CIPHER_AES_128_GCM 93 #define GNUTLS_CIPHER_AES_256_GCM 94 #define GNUTLS_PK_ECC 4 #define GNUTLS_PK_ECDSA 4 ~~~~ But file gnutls.h having version #define GNUTLS_VERSION "3.3.12" and doesn't contain GNUTLS_PK_ECDSA so I just replace it by GNUTLS_PK_ECC that has the same value. I don't know initial idea of (#if GNUTLS_VERSION_MAJOR < 3) so I can't propose the common patch. -- 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 4

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

March 31, 2019

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 46781] New: (Regression) iZotope Ozone: Shows black window since Wine 4.3
by wine-bugs＠winehq.org March 31, 2019

March 31, 2019

https://bugs.winehq.org/show_bug.cgi?id=46781 Bug ID: 46781 Summary: (Regression) iZotope Ozone: Shows black window since Wine 4.3 Product: Wine Version: 4.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: ajduck(a)outlook.com Distribution: --- Created attachment 63793 --> https://bugs.winehq.org/attachment.cgi?id=63793 Ozone in Wine 4.3 (GUI not working) Since Wine 4.3 Staging, the VST plugin iZotope Ozone shows a black window instead of it's GUI (both version 7 and 8). It shows correctly on Wine 4.2 Staging. It may be related to the d3d or d3dx9 components because the plugin uses them to render it's GUI. Both logs attached are Ozone ran in FL Studio with WINEDEBUG='+d3d,+d3d9,+loaddll'. In both logs I did exactly these steps: I opened FL, loaded the Ozone plugin, closed the Ozone window/GUI and then closed FL. The relevant part of both logs is after the loading of iZOzone8.dll. There's a similar discussion about a 4.3-staging regression involving a black window mentioned in bug #24983, but I'm not sure if it's related because neither d3dx or D3DXLoadSurfaceFromMemory show up when ran with WINEDEBUG=+d3dx. If it's indeed d3d or d3dx9, possibly one of these commits has something to do with it?: https://source.winehq.org/git/wine.git/?a=search&h=refs%2Ftags%2Fwine-4.3&s… -- 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 10

[Bug 46052] New: Spellforce: regression: black square around mouse pointer
by wine-bugs＠winehq.org March 31, 2019

March 31, 2019

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 March 31, 2019

March 31, 2019

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 46825] New: Regression: Black Screen when loading Warcraft 3
by wine-bugs＠winehq.org March 31, 2019

March 31, 2019

https://bugs.winehq.org/show_bug.cgi?id=46825 Bug ID: 46825 Summary: Regression: Black Screen when loading Warcraft 3 Product: Wine Version: 4.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: da2ce7(a)gmail.com Distribution: --- Created attachment 63854 --> https://bugs.winehq.org/attachment.cgi?id=63854 Log of trying to run Warcraft 3. On Fedora. In Wine 4.2 Warcraft 3 (III) worked without issue. In Wine 4.3 Warcraft 3 loads, however only a blank black screen is shown. -- 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 March 31, 2019

March 31, 2019

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