May 2020 - Wine-Bugs - list.winehq.org

[Bug 48834] New: Rockstar Games Launcher CEF helper crashes (x11drv use-after-free for HWND_MESSAGE)
by WineHQ Bugzilla Aug. 14, 2020

Aug. 14, 2020

https://bugs.winehq.org/show_bug.cgi?id=48834 Bug ID: 48834 Summary: Rockstar Games Launcher CEF helper crashes (x11drv use-after-free for HWND_MESSAGE) Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: bshanks(a)codeweavers.com Distribution: --- Created attachment 66751 --> https://bugs.winehq.org/attachment.cgi?id=66751 Valgrind output showing backtraces of UAF The problem: When the Rockstar Games Launcher is launched, 3 of its helper processes (SocialClubHelper.exe) crash in XDeleteContext(). SocialClubHelper.exe is part of CEF, and the code causing the crash is ANGLE's D3D9 renderer.<https://github.com/google/angle/blob/6dfdca836806b661cd0d0e090ef2cf1dc06a2e…> Here's what I've figured out: * ANGLE creates an HWND_MESSAGE window. <https://github.com/google/angle/blob/6dfdca836806b661cd0d0e090ef2cf1dc06a2e…> In X11DRV_create_win_data(), win_data is not created for the window (comment: "don't create win data for HWND_MESSAGE windows") * ANGLE uses the window as the focus window and device window when initializing D3D9. * The wined3d CS thread starts and calls wined3d_swapchain_gl_create_context(), leading to x11drv create_gl_drawable(), then create_client_window(). create_client_window() creates win_data (comment is "explicitly create data for HWND_MESSAGE windows since they can be used for OpenGL"), using the current thread's (the CS thread's) Display pointer. I believe this is when the CS thread calls XOpenDisplay(). * This works ok, until ANGLE shuts down. It first releases all the D3D9 objects: <https://github.com/google/angle/blob/6dfdca836806b661cd0d0e090ef2cf1dc06a2e…> Releasing D3D9 triggers wined3d to stop the CS thread, which ends with calling FreeLibraryAndExitThread(). This eventually calls X11DRV_ThreadDetach(), which closes the CS thread's Display. * ANGLE then calls DestroyWindow() on the device/focus window. This leads to x11drv destroy_whole_window(), which calls XDeleteContext() using the Display from the win_data. This was the CS thread's Display, which has since been closed/freed, causing use-after-free and (in this case) a crash. Commenting out the HWND_MESSAGE exception in X11DRV_create_win_data() does fix the crash, but this is likely not the correct fix. I've attached part of a Valgrind output showing the crash and backtraces, and should be able to add an ANGLE sample exe later that reproduces the bug. -- 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 1

[Bug 46742] New: The Sims 2 demo needs support for ProcessVertices() with software vertex shaders
by wine-bugs＠winehq.org Aug. 14, 2020

Aug. 14, 2020

https://bugs.winehq.org/show_bug.cgi?id=46742 Bug ID: 46742 Summary: The Sims 2 demo needs support for ProcessVertices() with software vertex shaders Product: Wine Version: 0.9.35. Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Split off from bug 8051: "Without ProcessVertices, characters will explode in family thumbnails (and same if you disable shaders through the game's cheat menu), and explosion of vertices will also happen with little icons that pop up above characters when they make a friend or get married (you can realiably observe it by loading Pleasant family). In both cases, this pops up: fixme:d3d:wined3d_device_process_vertices Output vertex declaration not implemented yet. err:d3d:get_flexible_vertex_size Unexpected position mask: 0x0" -- 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.

2 6

[Bug 33518] New: Some floors in Star Trek (2013) are completely black
by wine-bugs＠winehq.org Aug. 13, 2020

Aug. 13, 2020

http://bugs.winehq.org/show_bug.cgi?id=33518 Bug #: 33518 Summary: Some floors in Star Trek (2013) are completely black Product: Wine Version: 1.5.29 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: eurekafag(a)eureka7.ru Classification: Unclassified This is how they look like in the game: http://i.imgur.com/sNy2z7l.png This is how they should look (at least on Xbox360): http://youtu.be/YQCUUcrLfPc?t=30m30s Outdoors and everything else seems to be ok: http://i.imgur.com/Rv2O8sM.png http://i.imgur.com/Ytoi8cC.png I see this repeating message in the terminal: fixme:d3d:resource_check_usage Unhandled usage flags 0x8. Sometimes another message appears: fixme:d3d:wined3d_swapchain_present Ignoring flags 0x80000000. These two spam the output but nothing else appears while playing. I've run the game with WINEDEBUG=+d3d and the resulting file is about 600M long compressed to 23M. Maybe it will help. I launched the game and entered to the buggy room from the screenshot above, then killed it to prevent extra output. -- 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.

2 15

[Bug 48799] New: HOTAS kit Saitek X52 Pro doesn't show all buttons
by WineHQ Bugzilla Aug. 13, 2020

Aug. 13, 2020

https://bugs.winehq.org/show_bug.cgi?id=48799 Bug ID: 48799 Summary: HOTAS kit Saitek X52 Pro doesn't show all buttons Product: Wine Version: 5.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: joy.cpl Assignee: wine-bugs(a)winehq.org Reporter: patola(a)gmail.com Distribution: Ubuntu Created attachment 66714 --> https://bugs.winehq.org/attachment.cgi?id=66714 Selecting a button higher than 32 and wine thinking it's button 1 The HOTAS kit Saitek X52 Pro has 9 axes and 39 buttons. Wine only shows 32 and when a button higher than the 32th is pressed, it either registers it as button 1 or 2 or crashes outright with a dialog the messages: wine: L"C:\\windows\\system32\\joy.cpl" is a dll, not an executable wine: Unhandled page fault on write access to 00E06DB8 at address 7D612AE0 (thread 008e), starting debugger... wine: Unhandled page fault on write access to 00E06DB8 at address 7D611AE0 (thread 0088), starting debugger... 0090:fixme:dbghelp:elf_search_auxv can't find symbol in module Specifically, when button 35 is pressed (button 34 on jscal-gtk which counts from 0 to 38), the crash happens. The two screenshots show three applications using the joystick -- wine control panel, antimicro and jstest-gtk (which uses through linux input (js) instead of evdev but it's the same hardware). Also, enabling the js device "Logitech X52 Professional H.O.T.A.S. (js)" leads to an inconditional crash when selecting it on the "test joystick" tab but I understand this might be another issue. I need the HOTAS in evdev mode only. -- 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 46770] New: Splinter Cell: Blacklist crashes in DX9 mode when using FAudio
by wine-bugs＠winehq.org Aug. 12, 2020

Aug. 12, 2020

https://bugs.winehq.org/show_bug.cgi?id=46770 Bug ID: 46770 Summary: Splinter Cell: Blacklist crashes in DX9 mode when using FAudio Product: Wine Version: 4.3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 63782 --> https://bugs.winehq.org/attachment.cgi?id=63782 log No crash in DX11 mode. -- 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.

2 11

[Bug 47254] New: Unhandled exception: page fault on write access in 32-bit code
by wine-bugs＠winehq.org Aug. 12, 2020

Aug. 12, 2020

https://bugs.winehq.org/show_bug.cgi?id=47254 Bug ID: 47254 Summary: Unhandled exception: page fault on write access in 32-bit code Product: Wine Version: 4.0.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: scw189(a)cox.net Distribution: --- Created attachment 64540 --> https://bugs.winehq.org/attachment.cgi?id=64540 Back trace dump from Wine crash. Used to run Legacy9 (genealogy software). Mostly runs Ok. But, there are latency issues There is a problem with buffering keyboard input characters. If you select an input field and start typing too fast, the first two characters will generally be ignored. There also seem to be issues with background processes where after changing windows you need to wait 4-6 seconds before input keystrokes are accepted (they are also not buffered). Randomly, the system will display a message box about "the system has experienced a serious error..." and a crash dump is displayed: "Unhandled exception: page fault on write access to 0x6d4a95c8 in 32-bit code (0x7b476e81)." The message box allows a backtrace dump to be saved. The Legacy9 program is then locked on the last display screen and is un-responsive to keyboard or mouse clicks, although the mouse pointer is still active. The computer itself is not locked up. Closing the program error message box also closes the Legacy9 application. The Legacy9 application can be restarted at that time. -- 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.

2 4

[Bug 40945] New: Post provider setup of WMI core 1.5 installer needs
by wine-bugs＠winehq.org Aug. 12, 2020

Aug. 12, 2020

https://bugs.winehq.org/show_bug.cgi?id=40945 Bug ID: 40945 Summary: Post provider setup of WMI core 1.5 installer needs Product: Wine Version: 0.9.34. Hardware: x86 URL: https://web.archive.org/web/*/http://download.microsof t.com/download/platformsdk/wmi9x/1.5/W9X/EN-US/wmi9x.e xe OS: Linux Status: NEW Keywords: download, Installer, patch Severity: minor Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- Follow up to bug 37429 You'll need to grab the exe from archive.org. Set your wineprefix to win98, and install. It will crash late in the process, with: Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x7da6799f). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:7da6799f ESP:0033c590 EBP:0033c5c8 EFLAGS:00210202( R- -- I - - - ) EAX:7d895869 EBX:7da81000 ECX:0033c580 EDX:7ffdf000 ESI:01419738 EDI:00000000 Stack dump: 0x0033c590: 7d98a460 014192b8 00000000 014192e0 0x0033c5a0: 0033c630 01419b50 0000c5d0 7d98a460 0x0033c5b0: 00000020 7da67946 0033c5dc 00b81aa0 0x0033c5c0: 00000000 0033cbe0 0033c5f8 6206ccb5 0x0033c5d0: 00000000 0033cbe0 6206ccb5 01419b50 0x0033c5e0: 00000000 0033c630 00e90690 00000000 Backtrace: =>0 0x7da6799f class_object_SpawnInstance+0x6f(iface=<couldn't compute location>, lFlags=<couldn't compute location>, ppNewInstance=<couldn't compute location>) [/home/austin/wine-git/dlls/wbemprox/class.c:221] in wbemprox (0x0033c5c8) 1 0x6206ccb5 in mofd (+0xccb4) (0x0033c5f8) 2 0x6206e94a in mofd (+0xe949) (0x0033c680) 3 0x62062199 in mofd (+0x2198) (0x0033cbec) 4 0x62074d0a in mofd (+0x14d09) (0x0033d1bc) 5 0x003428bc in wbemupgd (+0x28bb) (0x0033d408) 6 0x003410ac in wbemupgd (+0x10ab) (0x0033d9a4) 7 0x00343528 in wbemupgd (+0x3527) (0x0033d9b8) 8 0x100150d0 in glc96e7.tmp (+0x150cf) (0x0033e3d8) 9 0x1000433e in glc96e7.tmp (+0x433d) (0x0033f1c8) 0x7da6799f class_object_SpawnInstance+0x6f [/home/austin/wine-git/dlls/wbemprox/class.c:221] in wbemprox: movl 0x4(%edi),%eax 221 if (!(record->fields = heap_alloc( table->num_cols * sizeof(struct field) ))) wine-1.9.14-15-g1bcc7ce austin(a)austin2:~$ sha1sum wmi9x.exe 62752e9c1b879688c26f205eebf07d3783906c3e wmi9x.exe austin(a)austin2:~$ du -sh wmi9x.exe 3.0M wmi9x.exe -- 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.

2 8

[Bug 49255] New: wineboot fails to start
by WineHQ Bugzilla Aug. 12, 2020

Aug. 12, 2020

https://bugs.winehq.org/show_bug.cgi?id=49255 Bug ID: 49255 Summary: wineboot fails to start Product: Wine-staging Version: 5.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aaronaz(a)protonmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- After installing the latest staging (5.9), 'winecfg' gives the following error: 002c:err:module:__wine_process_init failed to load L"C:\\windows\\system32\\wineboot.exe", error c0000018 0024:err:environ:run_wineboot failed to start wineboot c0000018 0024:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0034:err:module:__wine_process_init failed to load L"C:\\windows\\system32\\explorer.exe", error c0000018 003c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 003c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 003c:err:winediag:nodrv_CreateWindow The explorer process failed to start. I've removed/cleaned all files and reinstalled both staging and development a number of times over the past 1-2 weeks and each time get the above error, though stable works fine. I'm on Xubuntu 20.04, AMD64, installed from official repo. A number of others report the same... https://www.reddit.com/r/wine_gaming/comments/gkbxp6/getting_error_about_dr… -- 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 2

[Bug 49185] New: Wine staging branch results in incorrect keyboard mapping
by WineHQ Bugzilla Aug. 12, 2020

Aug. 12, 2020

https://bugs.winehq.org/show_bug.cgi?id=49185 Bug ID: 49185 Summary: Wine staging branch results in incorrect keyboard mapping Product: Wine-staging Version: 5.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janpieter.sollie(a)kabelmail.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: Gentoo Created attachment 67201 --> https://bugs.winehq.org/attachment.cgi?id=67201 runtime output When using the Staging branch, I have keyboard remappings which do not make sense, eg: the character 'i' is mapped to é (whereas the é character works fine). I'm using an nl_be keyboard layout (Azerty) - Tested with respondus lockdown browser - Tested with notepad !!This issue also occurs with Wine 5.7 Staging!! !! This issue does not occur with Wine 5.8 /5.7 Vanilla!! gentoo emerge flags: app-emulation/wine-staging-5.8:5.8::gentoo USE="X alsa dos gcrypt gecko jpeg mono mp3 ncurses netapi nls png pulseaudio run-exes ssl (staging) threads truetype udev unwind v4l vkd3d vulkan xml -capi -cups -custom-cflags -faudio -fontconfig -gphoto2 -gsm -gssapi -gstreamer -kerberos -lcms -ldap -odbc -openal -opencl -opengl -osmesa -oss -pcap -perl -pipelight -prelink -realtime -samba -scanner -sdl (-selinux) -test -themes -udisks -vaapi -xcomposite -xinerama" ABI_X86="32 64 (-x32)" wine-vanilla does not have this problem, same USE flags applied. Following fonts have been installed with WINETRICKS: comicsans andale arial courier georgia impact times trebuchet verdana webdings corefonts opensymbol -- 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 44106] New: Call of Duty Black Ops III Crashes
by wine-bugs＠winehq.org Aug. 12, 2020

Aug. 12, 2020

https://bugs.winehq.org/show_bug.cgi?id=44106 Bug ID: 44106 Summary: Call of Duty Black Ops III Crashes Product: Wine-staging Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lilwins(a)hotmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59829 --> https://bugs.winehq.org/attachment.cgi?id=59829 Call of Duty Black Ops III crash log Game crashes at start up, having similar issues with other Call of Duty titles. -- 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.

2 3