November 2017 - Wine-bugs - list.winehq.org

[Bug 43441] New: NVAPI unimplemented functions
by wine-bugs＠winehq.org 25 Nov '17

25 Nov '17

https://bugs.winehq.org/show_bug.cgi?id=43441 Bug ID: 43441 Summary: NVAPI unimplemented functions Product: Wine-staging Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: byi5000(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Since the staging part of wine just started working on the nvapi, i have "collected" more common nvapi calls. In this case none of the reported functions are breaking, but asked for by games. Rise of the Tomb Raider and Tomb Raider 2013: fixme:nvapi:unimplemented_stub function 0xdc6dc8d3 is unimplemented! Spintires: fixme:nvapi:unimplemented_stub function 0x6c2d048c is unimplemented! Beamng.Drive: fixme:nvapi:unimplemented_stub function 0x694d52e is unimplemented! -- 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 3

[Bug 43965] New: Project ERROR: Cannot run compiler 'g++' . Maybe you forgot to setup the environment?
by wine-bugs＠winehq.org 24 Nov '17

24 Nov '17

https://bugs.winehq.org/show_bug.cgi?id=43965 Bug ID: 43965 Summary: Project ERROR: Cannot run compiler 'g++'. Maybe you forgot to setup the environment? Product: Wine Version: 2.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alpha_one_x86(a)first-world.info Distribution: --- Hi, I have copied Qt 5.9.1 to my wine and put it into the PATH, I have this bug: wine qmake fixme:file:FindFirstFileExW flags not implemented 0x00000002 Project ERROR: Cannot run compiler 'g++'. Maybe you forgot to setup the environment? g++ is well detected: wine g++ g++.exe: fatal error: no input files compilation terminated. * same problem with official and compiled with mingw version * no problem with full windows into qemu Cheers. -- 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 3

[Bug 44006] New: Can't use valgrind with wine-staging ( works with vanilla wine)
by wine-bugs＠winehq.org 24 Nov '17

24 Nov '17

https://bugs.winehq.org/show_bug.cgi?id=44006 Bug ID: 44006 Summary: Can't use valgrind with wine-staging (works with vanilla wine) Product: Wine Version: 2.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, valgrind Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo While looking at https://github.com/Winetricks/winetricks/issues/810, I noticed that wine-staging has some memory corruption in msxml3 that does not occur under wine. I tried running the dotnet35sp1 installer under valgrind, which quickly crashed. I then ran a more simple test (scripts/suppressions at https://github.com/austin987/wine-valgrind-scripts) $ . vg-wrapper.sh $ wine start /min winemine $ valgrind wine notepad works fine, only output is: austin(a)austin2:~$ valgrind wine notepad preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 If I try the same under wine-staging, however: $ . vg-wrapper.sh $ wine-staging start /min winemine $ valgrind wine-staging notepad I get a nastly valgrind crash: austin(a)austin2:~$ valgrind wine-staging notepad preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 valgrind: m_debuginfo/debuginfo.c:551 (check_CFSI_related_invariants): Assertion 'cfsi_fits' failed. host stacktrace: ==9003== at 0x58039CF7: show_sched_status_wrk (m_libcassert.c:355) ==9003== by 0x58039E01: report_and_quit (m_libcassert.c:426) ==9003== by 0x58039EE3: vgPlain_assert_fail (m_libcassert.c:492) ==9003== by 0x5806855E: check_CFSI_related_invariants (debuginfo.c:551) ==9003== by 0x5806855E: di_notify_ACHIEVE_ACCEPT_STATE (debuginfo.c:766) ==9003== by 0x5806855E: vgPlain_di_notify_mmap (debuginfo.c:1063) ==9003== by 0x58090184: vgModuleLocal_generic_PRE_sys_mmap (syswrap-generic.c:2388) ==9003== by 0x580C199A: vgSysWrap_x86_linux_sys_mmap2_before (syswrap-x86-linux.c:989) ==9003== by 0x5808D022: vgPlain_client_syscall (syswrap-main.c:1857) ==9003== by 0x58089E90: handle_syscall (scheduler.c:1126) ==9003== by 0x5808B5C6: vgPlain_scheduler (scheduler.c:1443) ==9003== by 0x58099223: thread_wrapper (syswrap-linux.c:103) ==9003== by 0x58099223: run_a_thread_NORETURN (syswrap-linux.c:156) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 9003) ==9003== at 0x4018F10: mmap (mmap.c:32) ==9003== by 0x4006806: _dl_map_segments (dl-map-segments.h:90) ==9003== by 0x4006806: _dl_map_object_from_fd (dl-load.c:1183) ==9003== by 0x4008A19: _dl_map_object (dl-load.c:2199) ==9003== by 0x40138B7: dl_open_worker (dl-open.c:226) ==9003== by 0x43B09C6: _dl_catch_error (dl-error-skeleton.c:198) ==9003== by 0x40133A1: _dl_open (dl-open.c:649) ==9003== by 0x4447C72: dlopen_doit (dlopen.c:66) ==9003== by 0x43B09C6: _dl_catch_error (dl-error-skeleton.c:198) ==9003== by 0x44484B1: _dlerror_run (dlerror.c:163) ==9003== by 0x4447D2D: dlopen@@GLIBC_2.1 (dlopen.c:87) ==9003== by 0x404522E: wine_dlopen (loader.c:1051) ==9003== by 0x40458F5: wine_init (loader.c:977) ==9003== by 0x7C000C01: main (in /usr/lib64/wine-staging-2.17/bin/wine) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. Note, I only had wine-staging 2.17 installed, I can retest in 2.20 if needed. I havne't filed a valgrind bug, as it seems more likely to be a staging bug, but I can file one upstream if needed. -- 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 3

[Bug 43946] New: wineboot crashes with stack smashing on aarch64
by wine-bugs＠winehq.org 24 Nov '17

24 Nov '17

https://bugs.winehq.org/show_bug.cgi?id=43946 Bug ID: 43946 Summary: wineboot crashes with stack smashing on aarch64 Product: Wine Version: 2.19 Hardware: aarch64 OS: Linux Status: NEW Keywords: download, regression, source Severity: normal Priority: P2 Component: loader Assignee: nerv(a)dawncrow.de Reporter: austinenglish(a)gmail.com Regression SHA1: 27e92e550c2b86d5ebd4966926c1fcde03838dcc Distribution: Ubuntu austin(a)gcc116:~/wine-git$ rm -rf ~/.wine ; ./wine wineboot wine: created the configuration directory '/home/austin/.wine' *** stack smashing detected ***: C:\windows\system32\rundll32.exe terminated wine: Assertion failed at address 0x7f966f6af8 (thread 0010), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 15 100") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger fixme:seh:RtlUnwind Not implemented on ARM64 err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly. *** stack smashing detected ***: C:\windows\syswow64\rundll32.exe terminated wine: Assertion failed at address 0x7fa289caf8 (thread 0016), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 21 56") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger fixme:seh:RtlUnwind Not implemented on ARM64 wine: configuration in '/home/austin/.wine' has been updated. Noticed on GCC Compiler farm machine. -- 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 43332] New: rsaenh: Warning and notes while building (GCC 7.1.1)
by wine-bugs＠winehq.org 24 Nov '17

24 Nov '17

https://bugs.winehq.org/show_bug.cgi?id=43332 Bug ID: 43332 Summary: rsaenh: Warning and notes while building (GCC 7.1.1) Product: Wine Version: 2.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: rsaenh Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- rsaenh.c: In function ‘create_container_key.constprop’: rsaenh.c:156:23: warning: ‘%s’ directive writing up to 259 bytes into a region of size 235 [-Wformat-overflow=] #define RSAENH_REGKEY "Software\\Wine\\Crypto\\RSA\\%s" ^ rsaenh.c:156:23: note: in definition of macro ‘RSAENH_REGKEY’ #define RSAENH_REGKEY "Software\\Wine\\Crypto\\RSA\\%s" ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ rsaenh.c:1102:5: note: ‘sprintf’ output between 26 and 285 bytes into a destination of size 260 sprintf(szRSABase, RSAENH_REGKEY, pKeyContainer->szName); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ wine-2.12-103-g989a9dc917 -- 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 3

[Bug 43333] New: shell32: Warning and notes while building (GCC 7.1.1)
by wine-bugs＠winehq.org 24 Nov '17

24 Nov '17

https://bugs.winehq.org/show_bug.cgi?id=43333 Bug ID: 43333 Summary: shell32: Warning and notes while building (GCC 7.1.1) Product: Wine Version: 2.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- In file included from ../../include/windef.h:266:0, from shfldr_fs.c:35: shfldr_fs.c: In function ‘ISFHelper_fnCopyItems’: ../../include/winnt.h:5438:44: warning: ‘memset’ used with length equal to number of elements without multiplication by element size [-Wmemset-elt-size] #define RtlZeroMemory(Destination, Length) memset((Destination),0,(Length)) ^ ../../include/winbase.h:2790:24: note: in expansion of macro ‘RtlZeroMemory’ #define ZeroMemory RtlZeroMemory ^~~~~~~~~~~~~ shfldr_fs.c:1318:13: note: in expansion of macro ‘ZeroMemory’ ZeroMemory(wszDstPath, MAX_PATH+1); wine-2.12-103-g989a9dc917 -- 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 3

[Bug 43335] New: wintrust: Warning and note while building (GCC 7.1.1)
by wine-bugs＠winehq.org 24 Nov '17

24 Nov '17

https://bugs.winehq.org/show_bug.cgi?id=43335 Bug ID: 43335 Summary: wintrust: Warning and note while building (GCC 7.1.1) Product: Wine Version: 2.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wintrust Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- asn.c: In function ‘CRYPT_AsnDecodeOidIgnoreTag’: asn.c:1847:50: warning: ‘snprintf’ output may be truncated before the last format character [-Wformat-truncation=] snprintf(firstTwo, sizeof(firstTwo), "%d.%d", ^~~~~~~ asn.c:1847:13: note: ‘snprintf’ output between 4 and 7 bytes into a destination of size 6 snprintf(firstTwo, sizeof(firstTwo), "%d.%d", ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ pbEncoded[1 + lenBytes] / 40, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ pbEncoded[1 + lenBytes] - (pbEncoded[1 + lenBytes] / 40) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * 40); ~~~~~ wine-2.12-103-g989a9dc917 -- 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 3

[Bug 44037] New: Bricscad v17 crashes on startup
by wine-bugs＠winehq.org 24 Nov '17

24 Nov '17

https://bugs.winehq.org/show_bug.cgi?id=44037 Bug ID: 44037 Summary: Bricscad v17 crashes on startup Product: Wine Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tolikk91(a)yandex.ru Distribution: --- Created attachment 59703 --> https://bugs.winehq.org/attachment.cgi?id=59703 console output Bricscad v17.2.08 crashes on startup Maybe this is due to a flaw in the ADVAPI32.dll component -- 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 43336] New: propsys: Warning and notes while building (GCC 7.1.1)
by wine-bugs＠winehq.org 24 Nov '17

24 Nov '17

https://bugs.winehq.org/show_bug.cgi?id=43336 Bug ID: 43336 Summary: propsys: Warning and notes while building (GCC 7.1.1) Product: Wine Version: 2.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: propsys Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- propvar.c: In function ‘PropVariantChangeType’: propvar.c:61:23: warning: ‘.’ directive output may be truncated writing 1 byte into a region of size between 0 and 16 [-Wformat-truncation=] format, ^~~~~~ propvar.c:61:23: note: directive argument in the range [0, 65535] propvar.c:60:13: note: ‘snprintf’ output between 24 and 42 bytes into a destination of size 35 snprintf( ppropvarDest->u.pszVal, sizeof(format), ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ format, ~~~~~~~ time.wYear, time.wMonth, time.wDay, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ time.wHour, time.wMinute, time.wSecond, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ time.wMilliseconds ); ~~~~~~~~~~~~~~~~~~~~ wine-2.12-103-g989a9dc917 -- 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 3

[Bug 44060] New: DirectX 10 not running DirectX 8
by wine-bugs＠winehq.org 24 Nov '17

24 Nov '17

https://bugs.winehq.org/show_bug.cgi?id=44060 Bug ID: 44060 Summary: DirectX 10 not running DirectX 8 Product: Wine Version: 2.21 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx10 Assignee: wine-bugs(a)winehq.org Reporter: techno197(a)hotmail.com Created attachment 59771 --> https://bugs.winehq.org/attachment.cgi?id=59771 Call for DirectX 8 implication So I'm trying to run a specialized program that my work used to have on PC's. Company was bought out and everyone was given a Mac. Some people kept there PC's for the program. But those PC's are desktops and not laptops like the Mac's are. I can install the program with no problems. When I run the program it says that Vista machines run DirectX 10 and can not install DirectX 8. The program continues to run. When I get a certain point to load data, it uses DirectX for visualizations, no way around it. It then completely crashes. -- 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