April 2019 - Wine-Bugs - list.winehq.org

[Bug 45854] New: Magic the Gathering demo graphical glitch with virtual desktop
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=45854 Bug ID: 45854 Summary: Magic the Gathering demo graphical glitch with virtual desktop Product: Wine Version: 3.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spzakulec(a)gmail.com Distribution: --- Created attachment 62340 --> https://bugs.winehq.org/attachment.cgi?id=62340 Console output when running the Magic the Gathering demo with a virtual desktop Hi, the Magic the Gathering demo (the one by Microprose) works fine in a 32 bit wine prefix on 3.16 devel with OS set to Win 95, but key parts of the interface disappear or are solid black if the program is run in a virtual desktop. While I am not totally sure this is the same issue that affects all of the Microprose Magic the Gathering games, in practice the issue and the symptoms are identical. You can download the demo here: https://archive.org/details/mtgdemo I'm on Kubuntu 17.10 64 bit, using the official WineHQ repository. To reproduce this: Run mtgdemo.exe, which extracts to a folder. In the extracted folder, run DUEL.EXE in a 32 bit wine prefix with OS set to Win95. You'll see a screen without any black boxes or blobs on it- most importantly, the large Magic card on the left is visible. Click exit. Set DUEL.EXE to a virtual desktop- 1024x768 shows this issue. The card that was visible without the virtual desktop is now a giant black blob. Should you try to play the game, other graphical glitches will happen- cards disappear and only re-appear when you go to the next turn or right-click on the playing field, choose Duel Options, and then press OK. -- 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 45325] New: Ubisoft detection tool dont recognize correctly cpu
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=45325 Bug ID: 45325 Summary: Ubisoft detection tool dont recognize correctly cpu Product: Wine Version: 3.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdeathjr28(a)yahoo.es Distribution: --- Detection tool app used by various ubisoft titles case: assasins creed 1, prince of persia forgotten sands, prince of persia 2008 dont detect real name cpu and only shows intel pentium 4 2.40ghz However in side shows correct cpu cores and non overclocked frecuency Overclocked frecuency dont detected Also occur in batman arkham asylum installer too Thanks -- 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 20082] New: Driver Create and Close displatch routines should be called
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

http://bugs.winehq.org/show_bug.cgi?id=20082 Summary: Driver Create and Close displatch routines should be called Product: Wine Version: 1.1.29 Platform: PC URL: http://rh-software.com/ OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntoskrnl AssignedTo: wine-bugs(a)winehq.org ReportedBy: ray(a)pobox.co.uk Currently when a CreateFile() is done the IRP_MJ_CREATE dispatch routine is not called ! This is a major oversight and caused the v4.00 SIVDRIVER to crash. For 4.01 I worked around this, but failing to call the driver when the CreateFile() is done is a major failing and needs to be corrected. The IRP_MJ_CLOSE routine also needs to get called for the CloseHandle(). -- 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 10

[Bug 32086] New: LBA2 black screen above diagonal from bottom left to upper right
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

http://bugs.winehq.org/show_bug.cgi?id=32086 Bug #: 32086 Summary: LBA2 black screen above diagonal from bottom left to upper right Product: Wine Version: 1.5.15 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net Classification: Unclassified Created attachment 42299 --> http://bugs.winehq.org/attachment.cgi?id=42299 wine-1.5.15 terminal output in full screen mode DirectDrawRenderer=opengl became the default some time ago. As of 1.5.15, Little Big Adventure 2 aka. LBA2 displays a black screen above a diagonal from bottom left to upper right across its 640x480 virtual desktop. fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to 8 err:d3d_surface:d3dfmt_p8_init_palette This code should never get entered for DirectDraw!, expect problems -- indeed The black diagonal persists across all menus, intro videos and game play. Moving the virtual desktop around you momentarily unhides the missing half screen. Reopened bug #23921 is about using DirectDrawRenderer=gdi The black triangle also affects full screen mode. Terminal output is attached. Does OpenGL decompose the rectangular window into two triangles? -- 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 9

[Bug 24429] New: fifaconfig.exe: save function don`t work when Wine uses Mono 2.6 instead of dotnet20
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

http://bugs.winehq.org/show_bug.cgi?id=24429 Summary: fifaconfig.exe: save function don`t work when Wine uses Mono 2.6 instead of dotnet20 Product: Wine Version: 1.3.2 Platform: x86 URL: http://static.itmages.ru/i/10/0916/h_1284660639_8d8add adee.png OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: pzinin(a)gmail.com fifaconfig.exe - FIFA 11 config app written in .net (see link for get demo). When Wine uses Mono 2.6, I can`t save any settings using this app: it crashes. But a bug http://bugs.winehq.org/show_bug.cgi?id=24428 is not present on Mono. -- 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 13

[Bug 46917] New: Redirect an issue "wine's d3d8/ 9 visual tests fail on i965" to WineHQ
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=46917 Bug ID: 46917 Summary: Redirect an issue "wine's d3d8/9 visual tests fail on i965" to WineHQ Product: WineHQ Bugzilla Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: asimiklit.work(a)gmail.com CC: austinenglish(a)gmail.com Distribution: --- Mesa issue description: """ d3d8: visual.c:2728: Test failed: Expected color 0x0000ff00 at 400,60, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x00ff0000 at 560,60, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x0000ff00 at 400,180, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x00ff0000 at 560,180, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x0000ff00 at 80,300, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x0000ff00 at 240,300, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x0000ff00 at 400,300, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x00ff0000 at 560,300, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x00ff0000 at 80,420, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x00ff0000 at 240,420, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x00ff0000 at 400,420, got 0x000000ff. visual.c:2728: Test failed: Expected color 0x00ff0000 at 560,420, got 0x000000ff. d3d9: visual.c:12337: Test failed: Expected color 0x0000ff00 at 400,60, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x00ff0000 at 560,60, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x0000ff00 at 400,180, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x00ff0000 at 560,180, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x0000ff00 at 80,300, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x0000ff00 at 240,300, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x0000ff00 at 400,300, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x00ff0000 at 560,300, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x00ff0000 at 80,420, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x00ff0000 at 240,420, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x00ff0000 at 400,420, got 0x000000ff. visual.c:12337: Test failed: Expected color 0x00ff0000 at 560,420, got 0x000000ff. Fedora 20 [austin(a)localhost ~]$ yum list installed | grep -e intel -e mesa mesa-dri-drivers.i686 10.0.4-1.20140312.fc20 @updates mesa-dri-drivers.x86_64 10.0.4-1.20140312.fc20 @updates mesa-filesystem.i686 10.0.4-1.20140312.fc20 @updates mesa-filesystem.x86_64 10.0.4-1.20140312.fc20 @updates mesa-libEGL.i686 10.0.4-1.20140312.fc20 @updates mesa-libEGL.x86_64 10.0.4-1.20140312.fc20 @updates mesa-libEGL-devel.x86_64 10.0.4-1.20140312.fc20 @updates mesa-libGL.i686 10.0.4-1.20140312.fc20 @updates mesa-libGL.x86_64 10.0.4-1.20140312.fc20 @updates mesa-libGL-devel.i686 10.0.4-1.20140312.fc20 @updates mesa-libGL-devel.x86_64 10.0.4-1.20140312.fc20 @updates mesa-libGLU.i686 9.0.0-4.fc20 @updates mesa-libGLU.x86_64 9.0.0-4.fc20 @updates mesa-libGLU-devel.i686 9.0.0-4.fc20 @updates mesa-libGLU-devel.x86_64 9.0.0-4.fc20 @updates mesa-libOSMesa.x86_64 10.0.4-1.20140312.fc20 @updates mesa-libOSMesa-devel.x86_64 10.0.4-1.20140312.fc20 @updates mesa-libgbm.i686 10.0.4-1.20140312.fc20 @updates mesa-libgbm.x86_64 10.0.4-1.20140312.fc20 @updates mesa-libglapi.i686 10.0.4-1.20140312.fc20 @updates mesa-libglapi.x86_64 10.0.4-1.20140312.fc20 @updates mesa-libwayland-egl.x86_64 10.0.4-1.20140312.fc20 @updates mesa-libxatracker.x86_64 10.0.4-1.20140312.fc20 @updates xorg-x11-drv-intel.x86_64 2.21.15-5.fc20 @updates """ Looks it is a wine issue here according to: https://www.khronos.org/registry/OpenGL/extensions/ARB/ARB_framebuffer_obje… "- If the attachment sizes are not all identical, rendering will be limited to the largest area that can fit in all of the attachments (i.e. an intersection of rectangles having a lower left of (0,0) and an upper right of (width,height) for each attachment) - If the attachment sizes are not all identical, the values of pixels outside the common intersection area after rendering are undefined." This issue came from mesa issue: https://bugs.freedesktop.org/show_bug.cgi?id=77312 -- 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 14415] New: Monkey Island 3 demo slow
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

http://bugs.winehq.org/show_bug.cgi?id=14415 Summary: Monkey Island 3 demo slow Product: Wine Version: 1.1.0 Platform: PC URL: ftp://ftp.lucasarts.com/demos/pc/cursedemo.exe OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: tsalacinski(a)gmail.com Monkey Island 3 works pretty slow with Wine 1.1.0. It happens only in complex locations, where there is a waterfall etc. COMI works very slow, even on my Core2Duo 2.53 GHZ (which is pretty good for that game I think). The strange thing is, when the screen is scrolling (eg. the character moves to the other part of the scene and the scene is scrolling) it work properly. When the scene is static (eg. no scrolling, only animated parts like waterfall or rain etc) it works very bad. In this demo you can see this when you are shooting with the cannon. A part of walkthrough (on how to get to the cannon): After the intro you'll find yourself captive in LeChuck's ship. Start talking to the small pirate and you'll realize that it's your old friend Wally. Make him see that he is no good as a pirate and he will soon drop his hook and start crying. Pick up the plastic hook from the floor and pick up the ramrod from the wall. Use the cannon and sink the four boats full of skeletons. Thanks -- 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 22

[Bug 46205] New: Multiple kernel drivers need implementation of ' ntoskrnl.ObReferenceObjectByHandle' for 'PsThreadType' (PETHREAD)
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=46205 Bug ID: 46205 Summary: Multiple kernel drivers need implementation of 'ntoskrnl.ObReferenceObjectByHandle' for 'PsThreadType' (PETHREAD) Product: Wine Version: 3.21 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 44588 (and partially bug 44910) --- snip --- $ WINEDEBUG=+seh,+loaddll,+process,+service,+ntoskrnl wineboot >>log.txt 2>&1 ... 000f:trace:service:scmdatabase_load_services Loading service L"bizVSerial" 000f:trace:service:load_service_config Image path = L"System32\\drivers\\bizVSerialNT.sys" 000f:trace:service:load_service_config Group = (null) 000f:trace:service:load_service_config Service account name = L"LocalSystem" 000f:trace:service:load_service_config Display name = L"Franson VSerial" 000f:trace:service:load_service_config Service dependencies : (none) 000f:trace:service:load_service_config Group dependencies : (none) ... 0017:trace:service:service_thread 0x10d60 0017:trace:service:SERV_OpenSCManagerW ((null),(null),0x00000001) 0015:trace:service:svcctl_OpenSCManagerW ((null), (null), 1) 0017:trace:service:SERV_OpenSCManagerW returning 0x11920 0017:trace:service:RegisterServiceCtrlHandlerExW L"winedevice" 0x7f47d7011ab0 0x11800 0017:trace:service:SetServiceStatus 0x110c0 30 4 5 0 0 0 0 ... 000f:trace:service:process_send_start_message 0x143b0 L"bizVSerial" (nil) 0 0016:trace:service:service_handle_control L"winedevice" control 2147483648 data 0x11bb2 data_size 22 0016:trace:ntoskrnl:ZwLoadDriver (L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\bizVSerial") ... 0016:trace:service:QueryServiceConfigW Image path = L"System32\\drivers\\bizVSerialNT.sys" 0016:trace:service:QueryServiceConfigW Group = L"" 0016:trace:service:QueryServiceConfigW Dependencies = L"" 0016:trace:service:QueryServiceConfigW Service account name = L"LocalSystem" 0016:trace:service:QueryServiceConfigW Display name = L"Franson VSerial" 0016:trace:ntoskrnl:open_driver opened service for driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\bizVSerial" 0016:trace:service:SetServiceStatus 0x12e50 30 2 0 0 0 0 2710 0014:trace:service:svcctl_SetServiceStatus (0x15e80, 0x15754) 0016:trace:ntoskrnl:IoCreateDriver (L"\\Driver\\bizVSerial", 0x7f47c8c949c0) 0016:trace:ntoskrnl:load_driver loading driver L"System32\\drivers\\bizVSerialNT.sys" 0016:trace:loaddll:load_native_dll Loaded L"C:\\windows\\System32\\drivers\\bizVSerialNT.sys" at 0x460000: native 0016:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x468034 ip=468034 tid=0016 0016:trace:seh:NtRaiseException info[0]=0000000000000000 0016:trace:seh:NtRaiseException info[1]=fffff78000000320 0016:trace:seh:NtRaiseException rax=fffff78000000320 rbx=0000000000013178 rcx=0000000000013010 rdx=0000000000013178 0016:trace:seh:NtRaiseException rsi=00007f47d73b84b1 rdi=00007f47c8cd1c71 rbp=000000000033f8a0 rsp=000000000033f788 0016:trace:seh:NtRaiseException r8=0000000000466100 r9=00002b992ddfa232 r10=000000000000a000 r11=0000000000012ee0 0016:trace:seh:NtRaiseException r12=0000000000013010 r13=0000000000000000 r14=0000000000011b18 r15=0000000000468008 0016:trace:seh:call_vectored_handlers calling handler at 0x7f47c8c93260 code=c0000005 flags=0 0016:trace:seh:call_vectored_handlers handler at 0x7f47c8c93260 returned ffffffff 0016:trace:ntoskrnl:IoCreateDevice (0x13010, 496, L"\\Device\\bizvSerialMgr", 34, 0, 0, 0x33f790) 0016:trace:ntoskrnl:IoCreateSymbolicLink L"\\DosDevices\\bizSerialMgr" -> L"\\Device\\bizvSerialMgr" 0016:trace:ntoskrnl:KeInitializeEvent event 0x136e8, type 0, state 0. 0016:trace:ntoskrnl:KeInitializeEvent event 0x136c8, type 0, state 0. 0016:fixme:ntoskrnl:ObReferenceObjectByHandle stub: 0x3c 1fffff (nil) 0 0x136e0 (nil) 0016:trace:ntoskrnl:init_driver init done for L"bizVSerial" obj 0x13010 0016:trace:ntoskrnl:init_driver - DriverInit = 0x468008 0016:trace:ntoskrnl:init_driver - DriverStartIo = (nil) 0016:trace:ntoskrnl:init_driver - DriverUnload = 0x4613c0 0016:trace:ntoskrnl:init_driver - MajorFunction[0] = 0x461180 0016:trace:ntoskrnl:init_driver - MajorFunction[1] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[2] = 0x461228 0016:trace:ntoskrnl:init_driver - MajorFunction[3] = 0x46133c 0016:trace:ntoskrnl:init_driver - MajorFunction[4] = 0x461304 0016:trace:ntoskrnl:init_driver - MajorFunction[5] = 0x461398 0018:trace:ntoskrnl:KeWaitForMultipleObjects count 2, objs 0x56fd80, wait_type 1, reason 0, mode 0, alertable 0, timeout (nil), wait_blocks 0x56fd90. 0016:trace:ntoskrnl:init_driver - MajorFunction[6] = 0x461398 0016:trace:ntoskrnl:init_driver - MajorFunction[7] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[8] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[9] = 0x461398 0016:trace:ntoskrnl:init_driver - MajorFunction[10] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[11] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[12] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[13] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[14] = 0x4612e0 0016:trace:ntoskrnl:init_driver - MajorFunction[15] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[16] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[17] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[18] = 0x461374 0016:trace:ntoskrnl:init_driver - MajorFunction[19] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[20] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[21] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[22] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[23] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[24] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[25] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[26] = 0x7f47c8c997b0 0016:trace:ntoskrnl:init_driver - MajorFunction[27] = 0x7f47c8c997b0 0016:trace:service:SetServiceStatus 0x12e50 30 4 5 0 0 0 0 0015:trace:service:svcctl_SetServiceStatus (0x15e80, 0x15cf4) ... 0017:trace:ntoskrnl:unload_driver L"\\Driver\\bizVSerial" 0017:trace:service:SetServiceStatus 0x12e50 30 3 0 0 0 0 0 ... 0017:trace:ntoskrnl:KeSetEvent event 0x136c8, increment 0, wait 0. 0017:trace:ntoskrnl:KeWaitForMultipleObjects count 1, objs 0x44f900, wait_type 1, reason 6, mode 0, alertable 0, timeout (nil), wait_blocks (nil). 0018:trace:ntoskrnl:KeResetEvent event 0x136c8. 0017:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x7f47c8ca3183 ip=7f47c8ca3183 tid=0017 0017:trace:seh:NtRaiseException info[0]=0000000000000001 0017:trace:seh:NtRaiseException info[1]=00000000deadbeb7 0017:trace:seh:NtRaiseException rax=00000000deadbeaf rbx=000000000044f900 rcx=00007f47d6aed879 rdx=0000000000000000 0017:trace:seh:NtRaiseException rsi=000000000044f5c0 rdi=0000000000000000 rbp=000000000044f8a0 rsp=000000000044f580 0017:trace:seh:NtRaiseException r8=0000000000000000 r9=0000000000000000 r10=000000000044f340 r11=0000000000000246 0017:trace:seh:NtRaiseException r12=0000000000013010 r13=0000000000000001 r14=000000000044f908 r15=000000000044f900 0017:trace:seh:call_vectored_handlers calling handler at 0x7f47c8c93260 code=c0000005 flags=0 ... wine: Unhandled page fault on write access to 0xdeadbeb7 at address 0x7f47c8ca3183 (thread 0017), starting debugger... 0017:trace:seh:start_debugger Starting debugger "winedbg --auto 17 60" 0017:trace:process:CreateProcessInternalW app (null) cmdline L"winedbg --auto 17 60" 0017:trace:process:find_exe_file looking for L"winedbg" 0017:trace:process:find_exe_file Trying native exe L"C:\\windows\\system32\\winedbg.exe" 0017:trace:process:CreateProcessInternalW starting L"C:\\windows\\system32\\winedbg.exe" as Win64 binary (10000000-10018000, x86_64) 0017:err:seh:start_debugger Couldn't start debugger ("winedbg --auto 17 60") (1115) --- snip --- The kernel driver creates a secondary thread via 'PsCreateSystemThread' and wait s in driver unload routine for the thread to exit. Wine's 'ObReferenceObjectByHandle' is currently a stub, returning a fake (invalid) handle. This causes 'KeWaitForSingleObject' to dereference an invalid handle later. The sequence is pretty standard for Windows kernel drivers. One of the many driver examples on Github: https://github.com/Microsoft/Windows-driver-samples/blob/master/general/can… --- snip --- ... NTSTATUS DriverEntry(_In_ PDRIVER_OBJECT DriverObject, _In_ PUNICODE_STRING RegistryPath) { ... // // Start the polling thread. // devExtension->ThreadShouldStop = FALSE; status = PsCreateSystemThread(&threadHandle, (ACCESS_MASK)0, NULL, (HANDLE) 0, NULL, CsampPollingThread, deviceObject ); if ( !NT_SUCCESS( status )) { IoDeleteSymbolicLink( &unicodeDosDeviceName ); IoDeleteDevice( deviceObject ); return status; } // // Convert the Thread object handle into a pointer to the Thread object // itself. Then close the handle. // ObReferenceObjectByHandle(threadHandle, THREAD_ALL_ACCESS, NULL, KernelMode, &devExtension->ThreadObject, NULL ); ZwClose(threadHandle); } ... VOID CsampPollingThread( _In_ PVOID Context) { ... // // Now enter the main IRP-processing loop // for(;;) { ... // // See if thread was awakened because driver is unloading itself... // if ( DevExtension->ThreadShouldStop ) { PsTerminateSystemThread( STATUS_SUCCESS ); } ... } ... } ... VOID CsampUnload( _In_ PDRIVER_OBJECT DriverObject) { ... // // Set the Stop flag // devExtension->ThreadShouldStop = TRUE; ... // // Wait for the thread to terminate // KeWaitForSingleObject(devExtension->ThreadObject, Executive, KernelMode, FALSE, NULL ); ObDereferenceObject(devExtension->ThreadObject); ... } --- snip --- Microsoft docs: https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/wdm/n… Wine source: https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/ntoskrnl.exe/ntoskrn… --- snip --- 2580 /*********************************************************************** 2581 * ObReferenceObjectByHandle (NTOSKRNL.EXE.@) 2582 */ 2583 NTSTATUS WINAPI ObReferenceObjectByHandle( HANDLE obj, ACCESS_MASK access, 2584 POBJECT_TYPE type, 2585 KPROCESSOR_MODE mode, PVOID* ptr, 2586 POBJECT_HANDLE_INFORMATION info) 2587 { 2588 FIXME( "stub: %p %x %p %d %p %p\n", obj, access, type, mode, ptr, info); 2589 2590 if(ptr) 2591 *ptr = UlongToHandle(0xdeadbeaf); 2592 2593 return STATUS_SUCCESS; 2594 } --- snip --- $ sha1sum GpsGateClient.exe bd5ac140199054a7b4502994439fcc78009fee35 GpsGateClient.exe $ du -sh GpsGateClient.exe 2.5M GpsGateClient.exe $ wine --version wine-3.21-87-g65677e2b2f 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 4

[Bug 8036] The Spirit Engine's save/load functionality does not work
by wine-bugs＠winehq.org April 12, 2019

April 12, 2019

https://bugs.winehq.org/show_bug.cgi?id=8036 Vijay Kamuju <infyquest(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |infyquest(a)gmail.com Status|STAGED |RESOLVED Fixed by SHA1| |be678a52e163111085ab3694b6c | |1f3af8e4d4a4a Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #46 from Vijay Kamuju <infyquest(a)gmail.com> --- Fixed by commit be678a52e163111085ab3694b6c1f3af8e4d4a4a in wine 4.5 --- Comment #47 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 4.6. -- 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 0

[Bug 46944] New: Compatibility issue in creating D3D10/ 11 device on AMD graphics with XP drivers
by wine-bugs＠winehq.org April 10, 2019

April 10, 2019

https://bugs.winehq.org/show_bug.cgi?id=46944 Bug ID: 46944 Summary: Compatibility issue in creating D3D10/11 device on AMD graphics with XP drivers Product: Wine Version: 3.18 Hardware: x86 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: svyatpro(a)gmail.com Created attachment 64067 --> https://bugs.winehq.org/attachment.cgi?id=64067 GPU caps report Latest releases of WineD3D for Windows do not work with AMD graphics on Windows XP for OpenGL compatibility reasons I can't figure out. NVIDIA + XP drivers - works AMD + XP drivers - doesn't It is claimed that GLSL 4.30 is supported but in fact no D3D10/11 application works. No registry keys helps. I tried "shader_backend=glsl", "MaxVersionGL=dword:30002". In no vain. -- 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