February 2018 - Wine-bugs - list.winehq.org

[Bug 15789] New: Regression for Icewind Dale 2 : very low framerate
by wine-bugs＠winehq.org 22 Apr '18

22 Apr '18

http://bugs.winehq.org/show_bug.cgi?id=15789 Summary: Regression for Icewind Dale 2 : very low framerate Product: Wine Version: 1.1.7 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: gizmm0(a)hotmail.com CC: stefan(a)codeweavers.com I get very low fps, around 4 or 5 i would say. This renders the game unplayable. Every animation in the game seems affected, even mouse movement is not smooth. This does not affect menus, the problem only appears once a game is launched. The problem is still there with wine-1.1.7. In case it might be useful, the video card used is Nvidia 8600M GT, with nvidia drivers 177.80. A git bisection gave: e178ddd9e1e16d1a3f52492799692e289eefcf8c is first bad commit commit e178ddd9e1e16d1a3f52492799692e289eefcf8c Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Tue Aug 5 14:23:00 2008 -0500 wined3d: Use a swapchain for GDI surfaces. This is a long-needed cleanup aimed at removing the ddraw_primary, ddraw_window, ddraw_width and ddraw_height members from IWineD3DDeviceImpl, which just do not belong there. Destination window and screen handling is supposed to be done by swapchains. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 25

[Bug 37356] New: Multiple software protection/DRM schemes need ntoskrnl 'IoGetDeviceObjectPointer' implementation (Tages v5.x, ProtectDISC 6.x)
by wine-bugs＠winehq.org 16 Apr '18

16 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=37356 Bug ID: 37356 Summary: Multiple software protection/DRM schemes need ntoskrnl 'IoGetDeviceObjectPointer' implementation (Tages v5.x, ProtectDISC 6.x) Product: Wine Version: 1.7.27 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, split off from bug 9484 and also mentioned here: https://github.com/compholio/wine-compholio/issues/80 Can be reproduced with Tagès drivers version 5.x alone (two stacked/layered drivers). Also needed for other DRM schemes, such as ProtectDISC 6.x --- snip --- ... 0016:Call KERNEL32.CreateProcessW(00000000,00119fa8 L"C:\\windows\\system32\\winedevice.exe lirsgt",00000000,00000000,00000000,00000400,00540000,00000000,0084e4c8,0084e50c) ret=7edb5d3f ... 0038:Call KERNEL32.__wine_kernel_init() ret=7bc5a00d 0016:Ret KERNEL32.CreateProcessW() retval=00000001 ret=7edb5d3f ... 003c:Starting thread proc 0x7ed9b77b (arg=0x119670) ... 003c:Call advapi32.RegisterServiceCtrlHandlerExW(001152aa L"lirsgt",7edfc61f,00000000) ret=7edfc86c 003c:Ret advapi32.RegisterServiceCtrlHandlerExW() retval=0011a968 ret=7edfc86c ... 0009:Call KERNEL32.CreateFileW(0033c4d0 L"\\\\.\\lirsgt",c0000000,00000000,00000000,00000003,40000000,00000000) ret=0040108f ... 0009:Ret KERNEL32.CreateFileW() retval=00000064 ret=0040108f ... 0009:Call KERNEL32.DeviceIoControl(00000064,0022e013,0033c6fc,00000000,0033c6fc,00000000,0033c6f8,00000000) ret=00401ac3 ... 003c:Call driver dispatch 0x542140 (device=0x11aeb0,irp=0x53e780) 003c:Call ntoskrnl.exe.IoAllocateMdl(0011b4c0,00000005,00000000,00000000,00000000) ret=005416bd 003c:Call ntdll.RtlAllocateHeap(00110000,00000008,00000020) ret=7ed2eb34 003c:Ret ntdll.RtlAllocateHeap() retval=0011b0e0 ret=7ed2eb34 003c:fixme:ntoskrnl:IoGetCurrentProcess () stub 003c:Ret ntoskrnl.exe.IoAllocateMdl() retval=0011b0e0 ret=005416bd 003c:Call ntoskrnl.exe.MmProbeAndLockPages(0011b0e0,00000001,00000001) ret=005416d9 003c:fixme:ntoskrnl:MmProbeAndLockPages (0x11b0e0, 1, 1): stub 003c:Ret ntoskrnl.exe.MmProbeAndLockPages() retval=0000003f ret=005416d9 003c:Call ntoskrnl.exe.MmMapLockedPagesSpecifyCache(0011b0e0,00000000,00000001,00000000,00000000,00000020) ret=005429c4 003c:fixme:ntoskrnl:MmMapLockedPagesSpecifyCache (0x11b0e0, 0, 1, (nil), 0, 32): stub 003c:Ret ntoskrnl.exe.MmMapLockedPagesSpecifyCache() retval=00000000 ret=005429c4 003c:Call ntdll.RtlInitUnicodeString(0053e640,0053e648 L"\\Device\\atksgt") ret=00540387 003c:Ret ntdll.RtlInitUnicodeString() retval=0053e640 ret=00540387 003c:Call ntoskrnl.exe.IoGetDeviceObjectPointer(0053e640,00020000,0053e63c,0053e638) ret=005403a1 003c:fixme:ntoskrnl:IoGetDeviceObjectPointer stub: L"\\Device\\atksgt" 20000 0x53e63c 0x53e638 003c:Ret ntoskrnl.exe.IoGetDeviceObjectPointer() retval=c0000002 ret=005403a1 003c:trace:seh:raise_exception code=c0000005 flags=0 addr=0x5403c1 ip=005403c1 tid=003c 003c:trace:seh:raise_exception info[0]=00000001 003c:trace:seh:raise_exception info[1]=00000000 003c:trace:seh:raise_exception eax=00000000 ebx=7ed47000 ecx=0053e640 edx=0053ef8c esi=0011af68 edi=0053e944 003c:trace:seh:raise_exception ebp=00000000 esp=0053e638 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010282 003c:trace:seh:call_vectored_handlers calling handler at 0x7ed2d73c code=c0000005 flags=0 003c:trace:seh:call_vectored_handlers handler at 0x7ed2d73c returned 0 003c:trace:seh:call_stack_handlers calling handler at 0x7bc9de37 code=c0000005 flags=0 003c:Call KERNEL32.UnhandledExceptionFilter(0053e104) ret=7bc9de71 wine: Unhandled page fault on write access to 0x00000000 at address 0x5403c1 (thread 003c), starting debugger... ... --- snip --- $ sha1sum TagesSetup.exe b360bfc82b0c807c1caa7e423dfa4bc6515830a9 TagesSetup.exe $ du -sh TagesSetup.exe 204K TagesSetup.exe $ wine --version wine-1.7.27-113-g5afbb6b Regards -- 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 41265] New: Far Cry 1: game crashes when using mouse wheel
by wine-bugs＠winehq.org 15 Apr '18

15 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=41265 Bug ID: 41265 Summary: Far Cry 1: game crashes when using mouse wheel Product: Wine Version: 1.9.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: DanBrake0819(a)freenet.de Distribution: --- Created attachment 55565 --> https://bugs.winehq.org/attachment.cgi?id=55565 logfile Far Cry 1.4 (and unofficial 1.5 patch) crashes when using the mouse wheel. It happens in the latest Wine version (1.9.18). I also tested the latest stable version (1.8.4) and an older stable version (1.6.2)... the same thing: crash when using the mouse wheel. -- 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 42378] New: Diablo 3 2.4.3 - incorrect and slow rendering on x64 client
by wine-bugs＠winehq.org 14 Apr '18

14 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=42378 Bug ID: 42378 Summary: Diablo 3 2.4.3 - incorrect and slow rendering on x64 client Product: Wine Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: f.volejnik(a)gmail.com Distribution: --- Created attachment 57164 --> https://bugs.winehq.org/attachment.cgi?id=57164 Wine-staging 2.0 log of diablo3 running the d3d11 x64 client. Since the release wine-staging 2.0, diablo 3 is able to start in the 64bit mode, which utilizes d3d11 for rendering (Thanks!). It is not without issues, yet, though. Namely, the performance is really bad, on my machine (core i5, GTX 770) it renders about 3 frames per second (whereas the 32bit version runs with >60 FPS). The rendering is not without issues, too. Characters look matte and dark, very different look from the one one sees in the 32bit client. I am attaching a log from my machine (Arch linux, 64bit, nvidia blob 375.26, wine-staging 2.0). -- 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 6

[Bug 43046] New: Civilization VI (Windows version) - Crashed on startup
by wine-bugs＠winehq.org 14 Apr '18

14 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=43046 Bug ID: 43046 Summary: Civilization VI (Windows version) - Crashed on startup Product: Wine Version: 2.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: runemadsen16(a)hotmail.com Distribution: --- Created attachment 58208 --> https://bugs.winehq.org/attachment.cgi?id=58208 The output from wine (without fixme messages) Trying to run Civilization VI (Windows version) with wine-2.8 (also tried with wine-2.8 staging, same result) on Ubuntu, the game crashing, showing a black screen and starting "Firaxis Crash Reporter", however not visible until the Civilization process has been killed. I am running it with (starting it as a DX11 game): env WINEDEBUG=error+all,fixme-all env WINEPREFIX="[dir]" wine C:\\windows\\command\\start.exe steam://rungameid/289070 >> games-log.txt 2>&1 The content of games-log.txt has been attached. -- 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

[Bug 24011] New: Trackmania Nations Forever graphics test does not work
by wine-bugs＠winehq.org 13 Apr '18

13 Apr '18

http://bugs.winehq.org/show_bug.cgi?id=24011 Summary: Trackmania Nations Forever graphics test does not work Product: Wine Version: 1.3.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: diafero(a)arcor.de On first startup, Trackmania Nations Forever (free download at http://www.trackmania.com/index.php?rub=downloads ) usually makes a benchmark to set useful graphics detail settings. However, this does not work on wine: Instead of a benchmark, the actual full game is started. When I quit, the launcher tells me that the graphics data could not be found. I then get the normal launcher, and can start the game again. This happens each time I start the launcher. Trackmania United Forever has the same issue. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 43051] New: Rise of the Tomb Raider needs unimplemented function msvcr110.dll.__crtCapturePreviousContext
by wine-bugs＠winehq.org 13 Apr '18

13 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=43051 Bug ID: 43051 Summary: Rise of the Tomb Raider needs unimplemented function msvcr110.dll.__crtCapturePreviousContext Product: Wine Version: 2.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: fincer89(a)hotmail.com Distribution: --- Created attachment 58214 --> https://bugs.winehq.org/attachment.cgi?id=58214 ROTTR, unimplemented function msvcr110.dll.__crtCapturePreviousContext As stated in the title, Rise of the Tomb Raider (64-bit Steam game) requires unimplemented function msvcr110.dll.__crtCapturePreviousContext Basically, Wine complains about: wine: Call from 0x7b4567ea to unimplemented function msvcr110.dll.__crtCapturePreviousContext, aborting Lack of the function makes playing the game impossible (you can still access the main menu but go no further). Short log (relevant part) as an attachment. Full log file here: https://www.dropbox.com/s/s2ft59wg8jv81hn/rottr-unimplemented-msvcr110-func… Full log includes the following steps: 1) Launching 64-bit Steam client 2) Launching the game 3) Accessing the main menu 4) Trying to start a new game 5) ROTTR doesn't show the intro movie which is presented before the actual gameplay. Only black screen appears. 6) Killing ROTTR.exe & quitting Steam client -- 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 22

[Bug 19241] New: winemenubuilder crashes when running any application including notepad
by wine-bugs＠winehq.org 13 Apr '18

13 Apr '18

http://bugs.winehq.org/show_bug.cgi?id=19241 Summary: winemenubuilder crashes when running any application including notepad Product: Wine Version: 1.1.25 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: tmhikaru(a)gmail.com Created an attachment (id=22260) --> (http://bugs.winehq.org/attachment.cgi?id=22260) snapshot of the crash dialog whenever I run any application, winemenubuilder crashes. Disabling it via winecfg in the libraries section (specifically putting winemenubuilder.exe and toggling it to disabled) makes wine complain that it can't find the component but it no longer crashes. For a basic reproducable test I'll be running 'wine notepad' as an example here. I don't know what this component does or what it's a part of, but this crash did not happen under any previous version of wine. I'll be attaching a picture of the crash dialog as well as the stderr information. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 32

[Bug 43994] New: page fault when running droid4x-0-9-0.exe
by wine-bugs＠winehq.org 13 Apr '18

13 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=43994 Bug ID: 43994 Summary: page fault when running droid4x-0-9-0.exe Product: Wine Version: 2.0.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kenorb(a)gmail.com Distribution: --- File URL: https://droid4x.en.softonic.com/download $ wine droid4x-0-9-0.exe wine: Unhandled page fault on read access to 0x00000001 at address 0x4b10d0 (thread 0009), starting debugger... fixme:service:QueryServiceConfig2W Level 6 not implemented Unhandled exception: page fault on read access to 0x00000001 in 32-bit code (0x004b10d0). Backtrace: =>0 0x004b10d0 in droid4x-0-9-0 (+0xb10d0) (0x0032ccfc) 1 0x0040b15a in droid4x-0-9-0 (+0xb159) (0x0032cfb4) -- 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 7

[Bug 43096] New: rtpMidi cannot install.
by wine-bugs＠winehq.org 13 Apr '18

13 Apr '18

https://bugs.winehq.org/show_bug.cgi?id=43096 Bug ID: 43096 Summary: rtpMidi cannot install. Product: Wine Version: 1.6.1 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: massivenaked(a)yahoo.com rtpMidi cannot install. this is log. [0036:0037][2017-05-27T22:59:07]i323: Registering package dependency provider: {80D8C295-E035-4C68-B4F3-0DB34393A2C2}, version: 1.2.11.41, package: teVirtualMIDI32MSI [0036:0037][2017-05-27T22:59:07]i301: Applying execute package: teVirtualMIDI32MSI, action: Install, path: C:\users\Public\Application Data\Package Cache\{80D8C295-E035-4C68-B4F3-0DB34393A2C2}v1.2.11.41\teVM32Burn.msi, arguments: ' ALLUSERS="1" ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" USING_BURN="yes" SUPPRESSWHQL="1"' [0036:0037][2017-05-27T22:59:57]e000: Error 0x80070643: Failed to install MSI package. [0036:0037][2017-05-27T22:59:57]e000: Error 0x80070643: Failed to execute MSI package. [0031:0032][2017-05-27T22:59:57]e000: Error 0x80070643: Failed to configure per-machine MSI package. [0031:0032][2017-05-27T22:59:57]i319: Applied execute package: teVirtualMIDI32MSI, result: 0x80070643, restart: None [0031:0032][2017-05-27T22:59:57]e000: Error 0x80070643: Failed to execute MSI package. [0036:0037][2017-05-27T22:59:57]e000: Error 0x8007000e: Failed to allocate data for message. [0036:0037][2017-05-27T22:59:57]e000: Error 0x8007000e: Failed to get message over pipe [0036:0037][2017-05-27T22:59:57]e000: Error 0x8007000e: Failed to pump messages in child process. [0031:0032][2017-05-27T22:59:57]i319: Applied rollback package: teVirtualMIDI32MSI, result: 0x0, restart: None [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write message type to pipe. [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write send message to pipe. [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to send BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_PACKAGE_PROVIDER message to per-machine process. [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to register the package provider on per-machine package. [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write message type to pipe. [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write send message to pipe. [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to send message to per-machine process. [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to end session in per-machine process. [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write message type to pipe. [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write send message to pipe. [0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to send message to per-machine process. [0031:0032][2017-05-27T22:59:58]i399: Apply complete, result: 0x80070643, restart: None, ba requested restart: No -- 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