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

[Bug 45554] winex11.drv build fail with GCC 4.5

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45554 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joseph.kucia(a)gmail.com --- Comment #1 from Józef Kucia <joseph.kucia(a)gmail.com> --- Created attachment 61977 --> https://bugs.winehq.org/attachment.cgi?id=61977 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.

Aug. 2, 2018

[Bug 45554] New: winex11.drv build fail with GCC 4.5

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45554 Bug ID: 45554 Summary: winex11.drv build fail with GCC 4.5 Product: Wine-staging Version: 3.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Zenitur(a)yandex.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- With GCC 4.6 it successfully builds. gcc -m64 -c -o vulkan.o vulkan.c -I. -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe \ -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers \ -Wstrict-prototypes -Wtype-limits -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op -gdwarf-2 \ -gstrict-dwarf -DLDAP_DEPRECATED=1 -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0 vulkan.c:60:17: error: redefinition of typedef 'VkXlibSurfaceCreateFlagsKHR' ../../include/wine/vulkan.h:392:17: note: previous declaration of 'VkXlibSurfaceCreateFlagsKHR' was here make[1]: *** [vulkan.o] Error 1 make[1]: Leaving directory `/usr/src/packages/BUILD/wine-3.13/dlls/winex11.drv' make: *** [dlls/winex11.drv] Error 2 -- 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.

Aug. 2, 2018

[Bug 44052] Temple+ does not run due to missing D2D device and device context and multiple API stubs

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44052 --- Comment #35 from Zhenya <Zenitur(a)yandex.ru> --- Now Wine 3.13 is successfully building with GCC 4.5. -- 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.

Aug. 2, 2018

[Bug 44457] Hearthstone crashes on exit in d3d9 mode

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44457 zzzzzyzz(a)hacari.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz(a)hacari.org -- 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.

Aug. 2, 2018

[Bug 45327] League of Legends 8.12 crashes when starting a game

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45327 zzzzzyzz(a)hacari.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz(a)hacari.org -- 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.

Aug. 2, 2018

[Bug 45550] League of legends NA 8.15 Crashes after champ selection.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45550 zzzzzyzz(a)hacari.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz(a)hacari.org -- 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.

Aug. 2, 2018

[Bug 45478] World of Warcrafft: graphical artifacts since 8.0 (BfA)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45478 zzzzzyzz(a)hacari.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz(a)hacari.org -- 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.

Aug. 2, 2018

[Bug 45452] [World of Tanks] 64bit Crashes on startup since wine 3.8; 3.7 works perfect

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45452 zzzzzyzz(a)hacari.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz(a)hacari.org -- 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.

Aug. 2, 2018

[Bug 41652] Uplay cannot connect/login to Server

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=41652 --- Comment #34 from Maik Wagner <maiktapwagner(a)aol.com> --- Created attachment 61976 --> https://bugs.winehq.org/attachment.cgi?id=61976 Console output (wine 3.13-staging) Logging in works fine with 3.13-staging. -- 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.

Aug. 2, 2018

[Bug 2082] DirectDraw games only showing black screen

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=2082 --- Comment #170 from Saulius K. <saulius2(a)gmail.com> --- Found some MSDN article called "Redirecting GDI, DirectX, and WPF applications" [4]. How do devs think, can it bring some simplicity for the situation? --- quote --- Mixed DirectX and GDI Windows The other reasonably common rendering to a top level window involves mixing DirectX and GDI. There are two forms of "mixing" here, one is perfectly fine, and the other is problematic. _The form of mixing that is fine_ is when there is a window tree of the top level HWND and child HWNDs (and further children, etc), where each individual HWND is either rendered by DirectX or by GDI. In this situation, the redirection component of the DWM forms its own "composition tree" where each node in the tree represents a node or a set of "homogenously rendered nodes" in the "window tree" rooted at the top level HWND. Rendering occurs by having each of these render to their own surface, and then compositing this tree of surfaces to the desktop. Thus, mixed DirectX and GDI rendering works well, so long as the boundary between them is at least at the child HWND level. _The form of mixing that _doesn't work well_ is when an application uses DirectX and GDI to target the same HWND. This has never been a supported scenario with DirectX, but there have been scenarios where it has happened to work. Under the DWM, this is much more problematic, because there can be no guarantee of ordering between the DirectX and the GDI rendering. This is most troublesome when GDI and DirectX are not only rendering to the same HWND, but to overlapping areas of the same HWND. As such, this usage pattern is not supported. Note that there is an alternative that can often work for an application -- DirectX is capable of handing back a DC to a DirectX surface, and applications can perform GDI rendering to that DC. From the DWM's perspective, that DirectX surface remains purely rendered by DirectX, and all is well. --- quote --- [4] https://blogs.msdn.microsoft.com/greg_schechter/2006/05/03/redirecting-gdi-… -- 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.

Aug. 2, 2018