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

[Bug 38886] AArch64 platforms: ABI Problems wrt varargs ( needs arm64 specific __builtin_ms_va_list)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=38886 --- Comment #9 from André H. <nerv(a)dawncrow.de> --- just for future reference, because it is not that easy to find all the pieces, the story goes: Much earlier for x86_64 varargs ( https://bugs.llvm.org/show_bug.cgi?id=8851 ): { r186144: https://github.com/llvm-mirror/llvm/commit/ac226bbf457f6b5e5210a4a82b1ce678… r189644: https://github.com/llvm-mirror/clang/commit/e8519c31a6ef853b627d557702ac189… r245990: https://github.com/llvm-mirror/llvm/commit/7e96f0f6fffbdebfdac238ae76cc3a79… discussions: http://reviews.llvm.org/D1622 r247941: https://github.com/llvm-mirror/clang/commit/69b5694b76d36fde04c1f3511459a57… discussions: http://reviews.llvm.org/D1623 } r308208: https://github.com/llvm-mirror/llvm/commit/6c132cb749932c66a27c9e19ea542617… discussions: https://reviews.llvm.org/D34474 r308209: https://github.com/llvm-mirror/clang/commit/ebe8bde59376321af40abf168495ef8… r308218: https://github.com/llvm-mirror/clang/commit/ba419afb8473f35d5e1d3931c9e8891… discussions: https://reviews.llvm.org/D34475 -- 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.

Oct. 31, 2018

[Bug 46066] New: GeForceNOW doen`t start: err:module: import_dll Library qwave.dll (which is needed by L"Z: \\home\\louis\\Desktop\\troep\\GeForceNOW\\CEF\\Bifrost2.dll") not found

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=46066 Bug ID: 46066 Summary: GeForceNOW doen`t start: err:module:import_dll Library qwave.dll (which is needed by L"Z:\\home\\louis\\Desktop\\troep\\GeForceNOW\\CEF\\Bi frost2.dll") not found Product: Wine Version: 3.19 Hardware: x86 URL: https://download.nvidia.com/gfnpc/GeForceNOW-release.e xe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Regression SHA1: download Distribution: Ubuntu Created attachment 62665 --> https://bugs.winehq.org/attachment.cgi?id=62665 patch: add stub dll qwave sha1sum ~/Desktop/troep/GeForceNOW-release.exe f9f0fda0811c509421500e61d8819c658b8a60ab /home/louis/Desktop/troep/GeForceNOW-release.exe The app doens't start for me: wine GeForceNOW.exe wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe" 000b:err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2) 0026:err:module:import_dll Library qwave.dll (which is needed by L"Z:\\home\\louis\\Desktop\\troep\\GeForceNOW\\CEF\\Bifrost2.dll") not found 0026:err:module:import_dll Library Bifrost2.dll (which is needed by L"Z:\\home\\louis\\Desktop\\troep\\GeForceNOW\\CEF\\GeForceNOW.exe") not found 0026:err:module:import_dll Library qwave.dll (which is needed by L"Z:\\home\\louis\\Desktop\\troep\\GeForceNOW\\CEF\\Bifrost2.dll") not found 0026:err:module:import_dll Library Bifrost2.dll (which is needed by L"Z:\\home\\louis\\Desktop\\troep\\GeForceNOW\\CEF\\Geronimo.dll") not found 0026:err:module:import_dll Library Geronimo.dll (which is needed by L"Z:\\home\\louis\\Desktop\\troep\\GeForceNOW\\CEF\\GeForceNOW.exe") not found 0026:err:module:attach_dlls Importing dlls for L"Z:\\home\\louis\\Desktop\\troep\\GeForceNOW\\CEF\\GeForceNOW.exe" failed, status c0000135 qwave.dll seems to be present on winversions >= winVista (on testbots) Attached patch fixes the issue, GeforceNow starts then. -- 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.

Oct. 31, 2018

[Bug 46065] New: intel_do_flush_locked failed: Input/output error

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=46065 Bug ID: 46065 Summary: intel_do_flush_locked failed: Input/output error Product: Wine Version: 3.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rtentser(a)yandex.ru Distribution: --- I use Intel Extreme Graphics 2 videocard in my system. When i try to start any graphic application in wine it fails with "intel_do_flush_locked failed: Input/output error". After that dmesg shows GPU Hang. I reported the bug to kernel team: https://bugs.freedesktop.org/show_bug.cgi?id=103901. I think it's a driver problem. But i still want to know what in wine triggers it. It's not a kernel regression (i've checked with old kernels), it's not wine's regression (i've checked with stable releases from 1.6 and with 3.19 now). I need help to find out problem's source. What can i do? Here is log with "WINEDEBUG=all" (too large for attachment): https://yadi.sk/d/eOT8BZHAXKgoPg -- 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.

Oct. 31, 2018

[Bug 46064] JustFOV (Just cause 3 mod) is missing MSVCR100_CLR0400.dll.__C_specific_handler ( winetricks dotnet45 leaves winversion at win2003)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=46064 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com Keywords| |dotnet, download URL| |https://github.com/xforce/j | |ustfov/releases/tag/1.4 Summary|JustFOV (Just cause 3 mod) |JustFOV (Just cause 3 mod) |is missing |is missing |MSVCR100_CLR0400.dll.__C_sp |MSVCR100_CLR0400.dll.__C_sp |ecific_handler |ecific_handler (winetricks | |dotnet45 leaves winversion | |at win2003) --- Comment #2 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Just for the info: I reported this at winetricks, and Austin replied that winversion after ``winetricks dotnet45`` should stay at win2003 to be backward compatible with wine-stable 3.0, which seemed reasonable to me. (I don`t know enough to make a statement about this...) -- 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.

Oct. 31, 2018

[Bug 45917] battle.net launcher and mouse position on high DPI monitor

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45917 --- Comment #1 from Kimball <kdt3rd(a)gmail.com> --- further update: If I regedit and change HKEY_CURRENT_USER\Control Panel\Desktop\LogPixels from 161 (correct value for my monitor) to 96, then the UI interaction in the battle.net UI is correct, and I can click on the buttons without having to move the buttons to the 0,0 upper left corner of the monitor. This however makes the fonts and such incredibly tiny and unusable on things like regedit and winecfg. Which points to a missing scale somewhere in the code recently added in the previous few releases. In running with WINEDEBUG=-all,+win,+cursor, I notice the following pattern when moving the mouse around in the Battle.net app: 002b:trace:cursor:X11DRV_GetCursorPos pointer at (475,617) server pos (475,617) 002b:trace:win:GetWindowRect hwnd 0x600d6 (10,10)-(1167,666) 002b:trace:win:WINPOS_WindowFromPoint scope 0x600d6 (283,368) returning 0x600d6 002b:trace:win:TrackMouseEventProc point (283,368) hwnd 0x600d6 hittest 1 002b:trace:win:TrackMouseEventProc tracked pos (374,394), current pos (283,368), hover width 4, hover height 4 002b:trace:win:TrackMouseEventProc hwnd 0x600d6, msg 0118, id 7e93b844, time 218513192 0 when looking at the code for WindowFromPoint, I notice that it ends up calling point_thread_to_win_dpi, which then calls GetDpiForWindow, which then ends up calling either get_monitor_dpi or get_win_monitor_dpi based on which window is being queried. However, both of those have FIXME in them, and additionally, none of that code seems to pay attention to the DpiAwareness bits. So I presume this is just a missing segment of the DPI awareness implementation. I unfortunately don't know enough of how this is all intended to work to be able to propose a solution, although at first glance, it seems like changing the calls to get_monitor_dpi and get_win_monitor_dpi in GetDpiForWindow to using get_thread_dpi instead may work (although not sure what to do about get_win_monitor_dpi)? I will keep poking at it and see if I can figure out what it is all about, unless someone can pipe in and say "this is what it should be". -- 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.

Oct. 31, 2018

[Bug 46064] JustFOV (Just cause 3 mod) is missing MSVCR100_CLR0400.dll.__C_specific_handler

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=46064 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- This bug is invalid, see: https://bugs.winehq.org/show_bug.cgi?id=41628#c4 Resolving. -- 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.

Oct. 31, 2018

[Bug 46060] Just Cause 3 spams "thread: NtSetInformationThread info class 7 not supported yet"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=46060 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from Gijs Vermeulen <gijsvrm(a)gmail.com> --- Resolving. -- 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.

Oct. 31, 2018

[Bug 46060] Just Cause 3 spams "thread: NtSetInformationThread info class 7 not supported yet"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=46060 --- Comment #3 from C0rn3j <spleefer90(a)gmail.com> --- Then I guess this can be closed as invalid. -- 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.

Oct. 31, 2018

[Bug 46060] Just Cause 3 spams "thread: NtSetInformationThread info class 7 not supported yet"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=46060 --- Comment #2 from Nikolay Sivov <bunglehead(a)gmail.com> --- Terminal output is not a bug, you can disable it if it bothers you. -- 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.

Oct. 31, 2018

[Bug 46060] Just Cause 3 spams "thread: NtSetInformationThread info class 7 not supported yet"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=46060 --- Comment #1 from C0rn3j <spleefer90(a)gmail.com> --- Alright got it to launch, I didn't realize that the older 396.xx driver needs __GL_NextGenCompiler=1 to use the new compiler that's used by default on newer drivers. Plays well, the spam still occurs so the issue is valid. -- 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.

Oct. 31, 2018