June 2018 - Wine-Bugs - list.winehq.org

[Bug 43761] New: World of Warcraft d3d11 textures rendering regression and other... Wine Staging 2.17
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=43761 Bug ID: 43761 Summary: World of Warcraft d3d11 textures rendering regression and other... Wine Staging 2.17 Product: Wine-staging Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zefkerrigan(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59257 --> https://bugs.winehq.org/attachment.cgi?id=59257 World of Warcraft d3d11 textures rendering regression. Wine Staging 2.17 Sorry, but I really do not have the opportunity to find out if this bug is in the development Wine branch, because World of Warcraft can only be launched in Wine Staging, but it can not be launched in a "vanilla" development Wine branch. So, I using only Wine Staging. I could not get the output of the console, because, unfortunately, when I tried to run the game through the console, I did not manage to run the game until the stage of character management/movement. That is, the game hangs up every time the progress bar ends after clicking on the "Enter the World" button. But, I was surprised that the game is normally run through a shortcut on the dock bar, which also contains the same command in the line Exec=wine64 'c:/Program Files (x86)/World of Warcraft/Wow-64.exe' which I entered into the console (but, without "Exec=", of course). When I used Wine Staging 2.16 I did not have any noticeable rendering bugs with the World of Warcraft in DirectX11 mode, or DirectX9. But, with Wine Staging 2.17 I began to see what's on the attached screenshot if WoW is running in DirectX11 mode. But, in DirectX9 mode this bug does not appear, and there are no any distortions in the graphics. My specs: Arch Linux x86_64 with latest updates, GNOME. GPU Radeon HD7770 with latest Mesa. Wine Staging 2.17 with CSMT is on, x64 Wine prefix, 64bit WoW build. -- 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 16

[Bug 43793] New: d3d11-Deferred_Context patchset is missing dependency on wined3d-1DTextures
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=43793 Bug ID: 43793 Summary: d3d11-Deferred_Context patchset is missing dependency on wined3d-1DTextures Product: Wine-staging Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- When d3d11-Deferred_Context is applied, compilation fails like this: gcc -m64 -c -o wspool.o /home/user/build/wine-git/wine-source/dlls/winspool.drv/wspool.c -I. \ -I/home/user/build/wine-git/wine-source/dlls/winspool.drv -I../../include \ -I/home/user/build/wine-git/wine-source/include -D__WINESRC__ -D_SPOOL32_ -D_REENTRANT -fPIC \ -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers \ -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla \ -Wwrite-strings -Wpointer-arith -Wlogical-op -O3 ../../tools/winegcc/winegcc -o winscard.dll.so -B../../tools/winebuild -m64 -fasynchronous-unwind-tables -shared /home/user/build/wine-git/wine-source/dlls/winscard/winscard.spec \ winscard.o rsrc.res ../../libs/port/libwine_port.a /home/user/build/wine-git/wine-source/dlls/wined3d/resource.c: In function ‘wined3d_resource_update_info’: /home/user/build/wine-git/wine-source/dlls/wined3d/resource.c:403:32: error: ‘WINED3D_RTYPE_TEXTURE_1D’ undeclared (first use in this function); did you mean ‘WINED3D_RTYPE_TEXTURE_3D’? else if (resource->type == WINED3D_RTYPE_TEXTURE_1D || ^~~~~~~~~~~~~~~~~~~~~~~~ WINED3D_RTYPE_TEXTURE_3D Explicitly adding wined3d-1DTextures helps. -- 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 2

[Bug 42815] New: Autodetection of drives in winecfg crashes Wine in Wine ( Staging)
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=42815 Bug ID: 42815 Summary: Autodetection of drives in winecfg crashes Wine in Wine (Staging) Product: Wine-staging Version: 2.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: frail.knight(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 57876 --> https://bugs.winehq.org/attachment.cgi?id=57876 Backtrace Autodetection of drives in winecfg crashes Wine in Wine (Staging) I did a clean system install. I did a clean install of Wine 2.5 (Staging). $ wine --version wine-2.5 (Staging) I was going through the basic setup in Wine. I started winecfg. I clicked the Drives tab. I clicked the Autodetect button on the Drives tab. Wine Crashes. This has not happened to me in previous versions such as Wine 2.4 Staging. Uploading the backtrace and console output... -- 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 43435] New: x32dbg hangs when starting program
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=43435 Bug ID: 43435 Summary: x32dbg hangs when starting program Product: Wine-staging Version: 2.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de CC: dmitry(a)baikal.ru, erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- When starting a program to debug, it displays a message like "Breakpoint at 1000154C7 set" and then freezes. Bisected to commit 9c509cbf8879a4283cb134321764c1024bcaf855 Author: Dmitry Timoshkov <dmitry(a)baikal.ru> Date: Wed Mar 16 20:23:28 2016 +0800 kernel32: Implement K32GetMappedFileName. (v2) Reverting fixes 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 5

[Bug 41544] New: Pressing L-ALT key loses focus from game
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=41544 Bug ID: 41544 Summary: Pressing L-ALT key loses focus from game Product: Wine-staging Version: 1.9.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xkendy(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Uppon started game, after I press button L-ALT, the game lose mouse focus. Focus mouse pointer is in system (above the game window). After another pressing L-ALT, or mouse click focus is returned to game. Affected (tested) games: World Of Tanks (patch 0.9.16), World Of Warplanes (patch 1.9.6). How to reproduce: Fresh instalation WOT and WOWP using this guide for WOT: https://www.youtube.com/watch?v=CTU0vICF9O4 WOT: 1.9.20-staging L-ALT problem present 1.9.19-staging (or lower): wot not work WOWP: 1.9.20-staging L-ALT problem present 1.9.19-staging (or lower): L-ALT work correctly Tested on: - old installed game WOT - fresh installed WOT (using guid on youtube) - fresh installed WOWP (using guid on youtube for WOT) System: UBUNTU 14.04 LTS x86_64, Graphics: GeForce GT640 (driver 340, tested also version 372), 8GB RAM, CPU: i5 -- 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 44639] New: wine-staging build 9999806838 breaks bcrypt/ gnutls Battle.net
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=44639 Bug ID: 44639 Summary: wine-staging build 9999806838 breaks bcrypt/gnutls Battle.net Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vhaarr+wine(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 60635 --> https://bugs.winehq.org/attachment.cgi?id=60635 stacktrace Hi, This build: https://dev.wine-staging.com/builder/group/428/ which is this commit: https://github.com/wine-staging/wine-staging/commit/99998068380d7c5f714d83f… Produces the attached stacktrace when I launch battle.net. The previous build (427 is a non-staging build): https://dev.wine-staging.com/builder/group/426/ which is the commit immediately before the 428 build: https://github.com/wine-staging/wine-staging/commit/d3bcb6143632d35c8ce62db… Does not crash battle.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 8

[Bug 43511] New: Crash when launching Assassins Creed 4
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=43511 Bug ID: 43511 Summary: Crash when launching Assassins Creed 4 Product: Wine-staging Version: 2.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jgarciaalo(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 58896 --> https://bugs.winehq.org/attachment.cgi?id=58896 Crash log An error occurs when starting Assassins Creed 4. The game arrives to the first screen but throws a fatal error (seems a nullpointer). Note that this game worked on 2.7-Staging, 2.8-Staging and 2.9-Staging. The next version I checked was the 2.13-staging that had another crash already solved. Now in 2.14-staging it crash here. Submited files: Error screenshot: ac4_error.png Crash log: ac4_error.txt -- 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 43063] New: MetaTrader 4 has no internet connection
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=43063 Bug ID: 43063 Summary: MetaTrader 4 has no internet connection Product: Wine-staging Version: 2.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: danielbermond(a)yahoo.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 58234 --> https://bugs.winehq.org/attachment.cgi?id=58234 MT4 startup log After starting MetaTrader 4 the message 'Common error' is shown in connection status (bottom right corner of the window). All charts shows a big message 'Waiting for update'. No graphics/data is shown on charts. MetaTrader 4 was working fine until wine-staging 2.7. This problem is occurring only in wine-staging 2.8. Downgrading wine-staging to version 2.7 "fixes" the problem. Using regular wine version _2.8_ also "fixes" it. So it seems to be a regression of wine-staging 2.8. The bug also seems to be _not_ present in the regular wine version. System information: OS: Arch Linux x86_64 wine: 2.8 staging Notes: 1) MetaQuotes do not provide the (unbranded) MT4 download in their website anymore. Now there are only broker-branded versions and the links the can found at broker websites. For example, FxPro MT4 can be downloaded from: https://download.mql5.com/cdn/web/fxpro.financial.services/mt4/fxprocom4set… 2) MT4 seems to need gnutls for proper installation (dependency lib32-gnutls is needed for install). 3) Using comctl32 from winetricks fixes tooltips problems in charts. -- 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 44660] New: Microsoft Office: smoothing does not apply
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=44660 Bug ID: 44660 Summary: Microsoft Office: smoothing does not apply Product: Wine-staging Version: 3.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: genaloner(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 60664 --> https://bugs.winehq.org/attachment.cgi?id=60664 On fisrt window vanilla wine with good-looking fonts. On second - staging branch with weird fonts `winetricks fontsmooth=rgb` don't work with Office applications. On wanilla wine this command makes fonts smooth. But on staging it does nothing. -- 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 42287] New: Shantae and the Pirate' s Curse - moving sprites leave smudges behind them
by wine-bugs＠winehq.org Aug. 20, 2018

Aug. 20, 2018

https://bugs.winehq.org/show_bug.cgi?id=42287 Bug ID: 42287 Summary: Shantae and the Pirate's Curse - moving sprites leave smudges behind them Product: Wine-staging Version: 2.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ikk_pl(a)yahoo.co.uk CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 56997 --> https://bugs.winehq.org/attachment.cgi?id=56997 Screenshot of the problem Any moving sprites in the game cinematics leave behind a solitaire-like smudge. (Note that the game doesn't run on vanilla wine, it needs staging patches for the CreateDeferredContext call.) -- 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