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

[Bug 42010] New: ReactOS Calc does not show dots in radio buttons.
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=42010 Bug ID: 42010 Summary: ReactOS Calc does not show dots in radio buttons. Product: Wine Version: 1.9.24 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: carlo.bramix(a)libero.it Distribution: --- Created attachment 56449 --> https://bugs.winehq.org/attachment.cgi?id=56449 ReactOS Calc running in WINE. I tried to run my ReactOS Calc on WINE. It works fine but it does not show the dots inside the radio buttons. It works fine from Windows 9x to Windows 7, but not in WINE. Tested in lubuntu with latest trunk. -- 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 24

[Bug 41404] New: WPS Office 10.1.0.5775 unhandled exception on installation
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=41404 Bug ID: 41404 Summary: WPS Office 10.1.0.5775 unhandled exception on installation Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 2460acc(a)gmail.com Distribution: --- Created attachment 55759 --> https://bugs.winehq.org/attachment.cgi?id=55759 Backtrace file for error When trying to install WPS Office in Wine 1.8 (installation file wps_office_free_10.1.0.5775_en.exe), I get a serious error. Backtrace is attatched. -- 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 45523] New: FIFA 18 Demo errors out after launch
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=45523 Bug ID: 45523 Summary: FIFA 18 Demo errors out after launch Product: Wine Version: 3.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: throwawayaccx(a)gmail.com Distribution: --- Created attachment 61909 --> https://bugs.winehq.org/attachment.cgi?id=61909 Screenshot of the error. Immediately after launch the game exits with "Invalid license. Reason code = Missing DLL: kernel32.dll Function: SetProcessWorkingSetSizeEx" -- 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 41039] New: can't run virtualbox.exe
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=41039 Bug ID: 41039 Summary: can't run virtualbox.exe Product: Packaging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: 1934337507a(a)gmail.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 55214 --> https://bugs.winehq.org/attachment.cgi?id=55214 ss 无法运行virtualbox.exe，提示有严重错误 wine '/home/xiejinggang/.wine/drive_c/Program Files/Oracle/VirtualBox/VirtualBox.exe' wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe" err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2) fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:advapi:RegisterEventSourceW ((null),L"QPCore"): stub fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000000,(nil),0x0001,0x00000000,0x72e764,(nil)): stub fixme:advapi:DeregisterEventSource (0xcafe4242) stub fixme:ntoskrnl:KeInitializeEvent stub: 0x5532ac 0 0 fixme:ntoskrnl:KeInitializeEvent stub: 0x5532bc 0 0 fixme:ntoskrnl:KeInitializeEvent stub: 0x555410 1 0 fixme:ntoskrnl:KeEnterCriticalRegion : stub fixme:ntoskrnl:KeLeaveCriticalRegion : stub fixme:ntoskrnl:MmGetSystemRoutineAddress L"PsGetCurrentProcessWin32Process" not found fixme:ntoskrnl:MmGetSystemRoutineAddress L"PsGetCurrentThreadWin32Thread" not found fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeEnterCriticalRegion : stub fixme:ntoskrnl:KeLeaveCriticalRegion : stub fixme:ntoskrnl:MmGetSystemRoutineAddress L"ObRegisterCallbacks" not found fixme:ntoskrnl:MmGetSystemRoutineAddress L"ObUnRegisterCallbacks" not found fixme:ntoskrnl:PsSetCreateProcessNotifyRoutine stub: 0x54f7ce 0 fixme:ntoskrnl:PsSetCreateThreadNotifyRoutine stub: 0x54f8b8 fixme:ntoskrnl:PsSetLoadImageNotifyRoutine (0x54f8f6) stub fixme:ntoskrnl:CmRegisterCallback (0x54f934 (nil) 0x5553f8): stub fixme:ntoskrnl:KeEnterCriticalRegion : stub fixme:ntoskrnl:KeLeaveCriticalRegion : stub fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:PsSetCreateProcessNotifyRoutine stub: 0x54f7ce 1 fixme:ntoskrnl:PsRemoveCreateThreadNotifyRoutine stub: 0x54f8b8 fixme:ntoskrnl:PsRemoveLoadImageNotifyRoutine stub: 0x54f8f6 fixme:ntoskrnl:KeEnterCriticalRegion : stub fixme:ntoskrnl:KeLeaveCriticalRegion : stub fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeDelayExecutionThread (0, 0, 0x53e664): stub fixme:ntoskrnl:KeGetCurrentIrql stub! fixme:ntoskrnl:KeDelayExecutionThread (0, 0, 0x53e664): stub fixme:ntoskrnl:__regs_ExAcquireFastMutex 0x555404: stub fixme:ntoskrnl:__regs_ExReleaseFastMutex 0x555404: stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f6c8 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f4c8 1 C) semi-stub fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:wtsapi:WTSFreeMemory Stub (nil) wine: Call from 0x7b43bc2c to unimplemented function ntoskrnl.exe.FsRtlIsNameInExpression, aborting wine: Unimplemented function ntoskrnl.exe.FsRtlIsNameInExpression called at address 0x7b43bc2c (thread 0041), starting debugger... wine: Unhandled page fault on write access to 0x00545000 at address 0x7bc5474d (thread 0049), starting debugger... wine: Unhandled page fault on write access to 0x00544000 at address 0x7bc5474d (thread 0051), starting debugger... fixme:ntdll:EtwRegisterTraceGuidsW (0x2382c8d0, 0x23842738, {36c38d96-a693-4a22-b4b7-81510d39f547}, 1, 0x33fa04, (null), (null), 0x23842768): stub fixme:ntdll:EtwRegisterTraceGuidsW register trace class {6e5e5cbc-8acf-4fa6-98e4-0c63a075323b} fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x75da58 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x75daf8 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x75d8c8 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x75dab8 1 C) semi-stub err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded. err:winediag:nulldrv_CreateWindow The explorer process failed to start. fixme:ntdll:NtQueryInformationProcess (process=0xf0) Unimplemented information class: ProcessSessionInformation fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:msg:ChangeWindowMessageFilter 4a 00000001 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:ntdll:NtLockFile I/O completion on lock not implemented yet wine: Unhandled page fault on read access to 0x0000000f at address 0x41629a (thread 0009), starting debugger... fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:iphlpapi:NotifyAddrChange (Handle 0x18de9e4, overlapped 0x18de9c4): stub fixme:iphlpapi:CancelIPChangeNotify (overlapped 0x18de9c4): stub fixme:process:WTSGetActiveConsoleSessionId stub fixme:wtsapi:WTSQueryUserToken 1 0x82df80 fixme:wtsapi:WTSQueryUserToken 1 0x82df88 fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub fixme:advapi:EventRegister {dc55d4d9-138d-441a-80cb-77aec617e3f7}, 0x10089e00, 0x10100678, 0x10100670 fixme:advapi:EventUnregister deadbeef: stub fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b290 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 74080 (device=7 access=1 func=20 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b298 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b23c fixme:wtsapi:WTSQueryUserToken 1 0x82b244 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b290 fixme:wtsapi:WTSQueryUserToken 1 0x82b298 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b23c fixme:wtsapi:WTSQueryUserToken 1 0x82b244 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b290 fixme:wtsapi:WTSQueryUserToken 1 0x82b298 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b230 fixme:wtsapi:WTSQueryUserToken 1 0x82b238 err:rpc:I_RpcGetBuffer no binding fixme:crypt:CryptProtectMemory (0x143ac8 112 00000001): stub fixme:crypt:CryptUnprotectMemory (0x10ac1c0 112 00000001): stub fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82dcfc fixme:wtsapi:WTSQueryUserToken 1 0x82dd04 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b118 fixme:wtsapi:WTSQueryUserToken 1 0x82b120 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b214 fixme:wtsapi:WTSQueryUserToken 1 0x82b21c fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b1c8 fixme:wtsapi:WTSQueryUserToken 1 0x82b1d0 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b134 fixme:wtsapi:WTSQueryUserToken 1 0x82b13c fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b17c fixme:wtsapi:WTSQueryUserToken 1 0x82b184 fixme:wtsapi:WTSQueryUserToken 1 0x82b268 fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d1400 (device=2d access=0 func=500 method=0) fixme:wtsapi:WTSQueryUserToken 1 0x82b1e0 fixme:wtsapi:WTSQueryUserToken 1 0x82b1e8 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 Unhandled exception: page fault on read access to 0x0000000f in 32-bit code (0x0041629a). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b EIP:0041629a ESP:0033e9c4 EBP:0033e9d4 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00000004 EBX:00473c80 ECX:00000050 EDX:000000f5 ESI:004a03d0 EDI:00473c80 Stack dump: 0x0033e9c4: 004a03d8 00000270 000000f5 000000f5 0x0033e9d4: 0033f624 00416760 00473c80 00000000 0x0033e9e4: 00409590 7ffdf000 7b636000 00000000 0x0033e9f4: 00000000 00000000 00000000 00000000 0x0033ea04: 00000000 00000000 00000000 00000000 0x0033ea14: 00000000 00000000 00000000 00000000 Backtrace: =>0 0x0041629a in virtualbox (+0x1629a) (0x0033e9d4) 1 0x00416760 in virtualbox (+0x1675f) (0x0033f624) 2 0x004095b0 in virtualbox (+0x95af) (0x0033fe40) 3 0x7b45f81c call_process_entry+0xb() in kernel32 (0x0033fe58) 4 0x7b46084a start_process+0x59(peb=<couldn't compute location>) [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/kernel32/process.c:1108] in kernel32 (0x0033fe88) 5 0x7bc80760 call_thread_func_wrapper+0xb() in ntdll (0x0033fea8) 6 0x7bc8371d call_thread_func+0xfc(entry=0x7b4607f0, arg=0x7ffdf000, frame=0x33ffc8) [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/ntdll/signal_i386.c:2759] in ntdll (0x0033ffa8) 7 0x7bc8073e call_thread_entry_point+0x11() in ntdll (0x0033ffc8) 8 0x7bc52d17 start_process+0x16(kernel_start=0x7b4607f0) [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/ntdll/loader.c:3038] in ntdll (0x0033ffe8) 9 0xb7583b8d wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 10 0xb7583cf0 wine_switch_to_stack+0x1f(func=0x7bc52d00, arg=0x7b4607f0, stack=0x340000) [/home/xiejinggang/闊充箰/wine-1.9.15/libs/wine/port.c:77] in libwine.so.1 (0xbf929cb8) 11 0x7bc58ce9 LdrInitializeThunk+0x228(kernel_start=<couldn't compute location>, unknown2=<couldn't compute location>, unknown3=<couldn't compute location>, unknown4=<couldn't compute location>) [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/ntdll/loader.c:3094] in ntdll (0xbf929cf8) 12 0x7b46697a __wine_kernel_init+0xa69() [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/kernel32/process.c:1302] in kernel32 (0xbf92ae68) 13 0x7bc59bc3 __wine_process_init+0x152() [/home/xiejinggang/闊充箰/wine-1.9.15/dlls/ntdll/loader.c:3303] in ntdll (0xbf92aed8) 14 0xb7581d47 wine_init+0x2c6(argc=0x2, argv=0xbf92b434, error="", error_size=0x400) [/home/xiejinggang/闊充箰/wine-1.9.15/libs/wine/loader.c:956] in libwine.so.1 (0xbf92af38) 15 0x7c000ac2 main+0x81(argc=<is not available>, argv=<is not available>) [/home/xiejinggang/闊充箰/wine-1.9.15/loader/main.c:254] in <wine-loader> (0xbf92b388) 16 0xb738e72e __libc_start_main+0xdd() in libc.so.6 (0x00000000) 0x0041629a: movb 0x0000000f,%al Modules: Module Address Debug info Name (17 modules) PE 400000- 4f0000 Export virtualbox ELF 7b400000-7b7e0000 Dwarf kernel32<elf> \-PE 7b410000-7b7e0000 \ kernel32 ELF 7bc00000-7bcf5000 Dwarf ntdll<elf> \-PE 7bc10000-7bcf5000 \ ntdll ELF 7c000000-7c004000 Dwarf <wine-loader> ELF 7ef51000-7ef5f000 Deferred libnss_files.so.2 ELF 7ef5f000-7ef6c000 Deferred libnss_nis.so.2 ELF 7ef6c000-7ef87000 Deferred libnsl.so.1 ELF 7ef87000-7efd4000 Deferred libm.so.6 ELF b7371000-b7376000 Deferred libdl.so.2 ELF b7376000-b7531000 Dwarf libc.so.6 ELF b7532000-b754f000 Deferred libpthread.so.0 ELF b7571000-b757b000 Deferred libnss_compat.so.2 ELF b757b000-b7732000 Dwarf libwine.so.1 ELF b7734000-b7758000 Deferred ld-linux.so.2 ELF b775a000-b775b000 Deferred [vdso].so Threads: process tid prio (all id:s are in hex) 00000008 (D) C:\Program Files\Oracle\VirtualBox\VirtualBox.exe 00000009 0 <== 0000000e services.exe 00000057 0 00000056 0 00000037 0 0000002b 0 00000024 0 0000001c 0 00000017 0 00000016 0 00000014 0 00000010 0 0000000f 0 00000012 winedevice.exe 00000019 0 00000018 0 00000013 0 0000001a plugplay.exe 0000001f 0 0000001e 0 0000001b 0 00000020 QQProtect.exe 00000066 0 00000065 0 00000064 0 00000063 -1 0000005f 0 0000005e 0 0000005d 0 00000028 0 00000027 0 00000026 0 00000021 0 00000029 winedevice.exe 0000002e 0 0000002d 0 0000002a 0 0000002f QQPMSRV.exe 0000003b 0 00000039 0 00000036 0 00000030 0 00000031 explorer.exe 00000035 0 00000034 0 00000033 0 00000032 0 00000052 svchost.exe 0000005c 0 0000005b 0 00000059 0 00000058 0 00000053 0 System information: Wine build: wine-1.9.15 Platform: i386 Version: Windows XP Host system: Linux Host version: 4.2.0-42-generic fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:wtsapi:WTSEnumerateSessionsW Stub (nil) 0x00000000 0x00000001 0xa3e874 0xa3e870 fixme:msvcrt:__clean_type_info_names_internal (0x1005f874) stub fixme:msvcrt:__clean_type_info_names_internal (0x237207a0) stub fixme:advapi:UnregisterTraceGuids deadbeef: stub fixme:msvcrt:__clean_type_info_names_internal (0x238426f0) stub fixme:wtsapi:WTSQueryUserToken 1 0x82d418 fixme:wtsapi:WTSQueryUserToken 1 0x82d440 fixme:wtsapi:WTSQueryUserToken 1 0x82d8e4 fixme:wtsapi:WTSQueryUserToken 1 0x82d8ec fixme:advapi:RegisterEventSourceW ((null),L"QPCore"): stub fixme:advapi:ReportEventW (0xcafe4242,0x0004,0x0000,0x00000000,(nil),0x0001,0x00000000,0x72e780,(nil)): stub fixme:advapi:DeregisterEventSource (0xcafe4242) stub -- 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 43464] New: Elite Dangerous Horizons fails to connect to server with CRC error
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=43464 Bug ID: 43464 Summary: Elite Dangerous Horizons fails to connect to server with CRC error Product: Wine Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pecisk(a)gmail.com Distribution: --- Created attachment 58839 --> https://bugs.winehq.org/attachment.cgi?id=58839 EDH launching trace Version: Wine 2.13 on Fedora 26 Winetricks: WINE=/usr/bin/win64 ./winetricks dotnet452 corefonts quartz vcrun2012 1. Install ED Launcher wine64 EliteDangerous-Client-Installer.exe 2. Launch ED Launcher wine64 /.wine/drive_c/Program\ Files\ \(x86\)/Frontier/EDLaunch/EDLaunch.exe 3. Install Elite Dangerous Horizons 4. Press Play Expected result: EDH main menu appears Actual result: EDH compiles shaders but gets CRC error for server connection along the way at the left bottom corner. Compiling ends with game showing error message about not being able to verify connection with server. Note: ED 32-bit version which is separate client, does not receive same error and seems to be connecting to game just fine. Goal of this bug report to understand what might cause this CRC error. -- 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 31

[Bug 45724] New: Multiple EndScene calls result in multiple glFlush ( FF XIV)
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=45724 Bug ID: 45724 Summary: Multiple EndScene calls result in multiple glFlush (FF XIV) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: awesie(a)gmail.com Distribution: --- While investigating the performance of FF XIV (DirectX 9), one major issue is that it will call EndScene multiple times per frame. MSDN discourages this behavior, and on Wine it introduces a significant performance penalty because a flush is emitted for every call to wined3d_device_end_scene. I removed the call to wined3d_cs_emit_flush in wined3d_device_end_scene which significantly improved (~40%) the fps in my test area. Mileage may vary depending on other patches. -- 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 14

[Bug 45673] New: Calling delegated proxy methods returns 0x800706b5 ( RPC_S_UNKNOWN_IF), "err:rpc: RpcAssoc_BindConnection syntax {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, 0.0 not supported"
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=45673 Bug ID: 45673 Summary: Calling delegated proxy methods returns 0x800706b5 (RPC_S_UNKNOWN_IF), "err:rpc:RpcAssoc_BindConnection syntax {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, 0.0 not supported" Product: Wine Version: 3.14 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ole32 Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Created attachment 62097 --> https://bugs.winehq.org/attachment.cgi?id=62097 test program The test program demonstrates the problem fairly clearly. In Wine, IShellBrowser delegates proxy methods to its parent IOleWindow. If you obtain a proxy to an IShellBrowser (e.g. via ShellWindows) you can call IShellBrowser methods without difficulty, but the RPC runtime will throw up RPC_S_UNKNOWN_IF if you try to call IOleWindow methods: 0009:err:rpc:RpcAssoc_BindConnection syntax {00000114-0000-0000-c000-000000000046}, 0.0 not supported 0009:fixme:ole:NdrClearOutParameters (0x61fc7c,0x7ebc63c6,0x61fdb0): stub got 0x800706b5 (N.b. 00000144-etc. is the IID of IOleWindow.) However, after you query for IOleWindow, calling IOleWindow methods on the original IShellBrowser interface will succeed. The underlying problem is this: When an interface is marshalled by ole32, it creates a stub on the server side and then registers that stub with rpcrt4. The interface ID that is used in RpcServerRegisterIf() is the IID of the interface itself, in this case IID_IShellBrowser. The stub creation functions live in rpcrt4 and end up delegating some methods to the stub of IOleWindow, which is different (e.g. it lives in ole32 instead of actxprxy). However, this stub never is registered with rpcrt4. When the program calls proxy methods, the proxy goes through ndr_client_call() -> NdrProxyGetBuffer() -> ClientRpcChannelBuffer_GetBuffer() [in ole32/rpc.c] -> I_RpcGetBuffer(). NdrProxyGetBuffer() passes the IID of the proxied interface to IRpcChannelBuffer_GetBuffer(), and that interface is eventually used by rpcrt4 as the ifid for the transaction. When that interface is IID_IShellBrowser, the server will recognize it, and the transaction works fine. However, when the program calls IOleWindow proxy methods, the proxy object is 'swapped out' (by the assembly thunks in fill_delegated_proxy_table()) and so the IID that NdrProxyGetBuffer() passes is the IID of the *parent* interface. Since this interface was never registered with RPC on the server side, the server refuses connection ("syntax not supported") and the proxy call fails. As a corollary, if you query that parent interface—even if you then throw away the resulting proxy—it will have been registered on the server side, and so calls to the delegated methods on the original object will miraculously start to succeed. I don't know what the correct way is to solve this problem. As far as I understand it's not something that can be tested—all of this is quite deep inside of OLE/RPC implementation details. It doesn't seem like there's any appropriate place to tell OLE about the delegated stub, at least not given the current infrastructure, and I'm not sure how RPC could appropriately inform OLE about the stub location. On the other hand I'd guess that maybe the child IID (i.e. IID_IShellBrowser) should be passed somewhere along the line on the client side; i.e. the standard proxy implementation should store the original IID inside the delegated proxy, and that original IID should be used by NdrProxyGetBuffer(). -- 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 43890] New: Divinity: Original Sin 2 does not successfully launch
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=43890 Bug ID: 43890 Summary: Divinity: Original Sin 2 does not successfully launch Product: Wine Version: 2.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: arnfranke(a)yahoo.com Distribution: --- https://appdb.winehq.org/objectManager.php?sClass=version&iId=35767 Before it tries to launch, it throws an error about failing to create a rendering device and that DX11 is required. https://appdb.winehq.org/appimage.php?iId=52049 When it tries to launch, it creates a window but draws nothing to it - if I move it, it simply contains an image of my desktop that moves. This might be a new problem, as older reports seem to indicate it works, or it might be because I'm using an Nvidia GPU and the people who had success used AMD and Intel GPUs. I don't know enough to be sure, or have enough machines to test. It also might be caused by this `dxgi` component that it's reporting, so I've decided to set this bug's component to `directx-d3d`. Also, plenty of stubs from `msvcp`, `win`, `xinput`, `ntdll`, and `msctf`. See the AppDB page for more information and a full terminal log. -- 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 18

[Bug 40828] New: Switching resolution in desktop mode makes task bar redraw on top of full screen game
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=40828 Bug ID: 40828 Summary: Switching resolution in desktop mode makes task bar redraw on top of full screen game Product: Wine Version: 1.9.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- I got this issue with Aliens versus Predator Classic 2000 on Steam. Preamble : The game uses 800x600 screen size to render cinematic and the main menu. The gameplay uses whatever screen resolution is set in the game video options menu. It switches between those two resolutions when starting or abandoning a level or when showing an in-game cinematic. The Wine virtual desktop mode is set to the native screen resolution that is the same resolution used for gameplay. When the game does not run, the Steam window and the task bar are visible and working properly. Steam puts an icon in the notification tray of the task bar. Issue : When the game is launched it switches the desktop to 800x600 to show the intro cinematic. The task bar is visible and covers the bottom of the full-screen game. The cinematics are letter-boxed and the menu has nothing of importance on those few bottom pixels so it's not that much a problem. When starting a level, the game switches to the native screen resolution, but the task bar still covers the bottom of the screen. The game can be played as the task bar does not hide much but it contrasts with the game and should be hidden by the full-screen app anyway. Workaround : The game grabs the mouse, so it is by default not possible to click on the window button on the task bar to refresh the game window, but activating the Steam game overlay frees the mouse cursor, and allow to click on the window button on the task bar. Clicking on that button twice makes the game window redraw over the task bar. The Steam overlay can then be closed and the game can be played with the task bar hidden. However, starting/abandoning a level or viewing a cinematic makes the game switch resolution and the task bar come back. -- 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 45

[Bug 43358] New: xaudio crashes in EVE Online during launch
by wine-bugs＠winehq.org March 3, 2019

March 3, 2019

https://bugs.winehq.org/show_bug.cgi?id=43358 Bug ID: 43358 Summary: xaudio crashes in EVE Online during launch Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: Commander.Alchemy(a)gmail.com Distribution: --- Created attachment 58718 --> https://bugs.winehq.org/attachment.cgi?id=58718 Backtrace with wine-staging compiled with -g and using winedbg. When launching EVE - Online the game crashed with backtraces to Xaudio (se logs) This happens with Wine 2.12 or Wine-Staging 2.12 from local repos in Arch or self compiled. However works fine with using wine or wine-staging binaries from PlayOnLinux. This was introduced somewhat lately since it worked fine couple of months before. Maybe a GCC thing? -- 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