January 2021 - Wine-Bugs - list.winehq.org

[Bug 50474] New: Papyrus 10, from "R.O.M. GmbH" refuses starting after updating to version 10.1
by WineHQ Bugzilla Jan. 11, 2021

Jan. 11, 2021

https://bugs.winehq.org/show_bug.cgi?id=50474 Bug ID: 50474 Summary: Papyrus 10, from "R.O.M. GmbH" refuses starting after updating to version 10.1 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeijei(a)gmx.net Distribution: --- Created attachment 69110 --> https://bugs.winehq.org/attachment.cgi?id=69110 Papyrus 10 refuse starting after updating to Papyrus 10.1 Papyrus 10, from "R.O.M. GmbH" refuses starting after updating to version 10.1 -- 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 18296] New: DInput has issues with KDE4.2 keyboard input repeat.
by wine-bugs＠winehq.org Jan. 11, 2021

Jan. 11, 2021

http://bugs.winehq.org/show_bug.cgi?id=18296 Summary: DInput has issues with KDE4.2 keyboard input repeat. Product: Wine Version: 1.1.20 Platform: PC-x86-64 URL: http://www.coh.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: wine(a)eternaldusk.com After upgrading to Kubuntu Jaunty, City of Heroes characters show a horrible staggering when you try move consistently in any direction. The character animation resets at the interval equivalent to the keyboard delay. So, it's as if the application is seeing you press the key over and over - instead of holding it down. Turning off keyboard repeat in the system options eliminates this issue. Modifying the delay only slows the initial staggering. -- 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 41

[Bug 47436] New: `winetricks -q dotnet30sp1` fails
by wine-bugs＠winehq.org Jan. 11, 2021

Jan. 11, 2021

https://bugs.winehq.org/show_bug.cgi?id=47436 Bug ID: 47436 Summary: `winetricks -q dotnet30sp1` fails Product: Wine Version: 4.11 Hardware: x86 OS: Linux Status: NEW Keywords: dotnet, download, Installer, regression Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: download, regression, installer, dotnet Distribution: Gentoo To reproduce: winetricks -q dotnet30p1 Regression introduced by: commit 705d3eed86f3ff96ee1190dbc694148c21c4939c Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Wed May 1 18:24:04 2019 -0500 setupapi: Fill out all source file parameters in SetupQueueDefaultCopy(). Later, it hangs because of: commit 9ccf1dd88b89530977923058a7334816e6b368d4 Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Tue May 7 18:04:10 2019 -0500 setupapi: Avoid passing a NULL source filename to SetupQueueDefaultCopy(). Fixes a regression introduced by 705d3eed86f3ff96ee1190dbc694148c21c4939c. And that hang is fixed by (but the installer still fails): 8bc25b24af0276985ad080c8364c11cfff3a1fe5 is the first bad commit commit 8bc25b24af0276985ad080c8364c11cfff3a1fe5 Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Fri May 17 17:36:53 2019 -0500 setupapi: Don't fail a queued copy if no copy was necessary. This fixes a regression introduced by 3e5c9798a80641e0e39e95e4467c60405b22b062. With wine-4.11: The .NET Runtime Optimization Service is started and paused. 0078:fixme:msvcrt:__clean_type_info_names_internal (0x64085a64) stub 0017:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d0c00 (device=2d access=0 func=300 method=0) 0017:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 2d0c00 (device=2d access=0 func=300 method=0) 0075:fixme:advapi:LsaOpenPolicy ((null),0x32ddb4,0x00000001,0x32dda8) stub 0075:fixme:advapi:GetWindowsAccountDomainSid (0x32dd24 0x16765c 0x32dd20): semi-stub 0075:fixme:secur32:GetComputerObjectNameW NameFormat 7 not implemented 0075:fixme:advapi:LsaClose (0xcafe) stub 0075:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet Microsoft (R) CLR Native Image Generator - Version 2.0.50727.1433 Copyright (c) Microsoft Corporation. All rights reserved. The .NET Runtime Optimization Service is running. 0082:fixme:msvcrt:__clean_type_info_names_internal (0x64085a64) stub ------------------------------------------------------ exit status 236 - dotnet30sp1 installation failed ------------------------------------------------------ -- 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 50355] New: Commandos 2: Men of Courage hangs after starting
by WineHQ Bugzilla Jan. 8, 2021

Jan. 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=50355 Bug ID: 50355 Summary: Commandos 2: Men of Courage hangs after starting Product: Wine Version: 5.21 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: baskanov(a)gmail.com Regression SHA1: a73460bca0e7f97fc371264bd5ad669357882b68 Distribution: --- Commandos 2 (legacy version, not the HD remaster) hangs completely after starting, showing only a black screen with the game cursor visible on the screen. This was tested with the GOG.com version. Maybe not a real regression because videos, including the intro video didn't work correctly before (intro video was simply skipped and the game was loading the main menu). The current problem is present since commit a73460bca0e7f97fc371264bd5ad669357882b68 amstream: Wait for the state transition to complete in AMMultiMediaStream::SetState. With the commit reverted, the game works just as before (no intro video, but the main menu is accessible). Plain terminal output shows only 0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0024:err:winediag:MIDIMAP_drvOpen No software synthesizer midi port found, Midi sound output probably won't work. wine-6.0-rc2-52-g0aa6f8e2ea1 -- 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 50151] New: World of Tanks fails to launch if LC_LANG/LC_ALL are set ja_JP
by WineHQ Bugzilla Jan. 8, 2021

Jan. 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=50151 Bug ID: 50151 Summary: World of Tanks fails to launch if LC_LANG/LC_ALL are set ja_JP Product: Wine Version: 5.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ankouslash(a)yahoo.co.jp Distribution: --- Created attachment 68659 --> https://bugs.winehq.org/attachment.cgi?id=68659 WoT's python.log including failed case and launched case Since wine-4.20, World of Tanks fails to launch if LC_LANG and LC_ALL are set ja_JP.UTF-8. Error is recorded in python.log of WoT, please see attached. Steps to reproduce: 1. Launch Wargaming.net Game Center 2. Click"PLAY" button in WORLD OF TANKS tab Actual result: World of Tanks fails while syncing data on launching. In the following case, WoT is launched properly: - Use wine-4.19 - Use latest wine with LC_LANG/LC_ALL=en_US.UTF-8 Version: wine & wine-staging 4.20-5.21 Platform: Arch Linux (64bit) https://worldoftanks.com/ -- 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 17

[Bug 49511] New: Kontakt (Native Instruments) runtime is broken (regression)
by WineHQ Bugzilla Jan. 8, 2021

Jan. 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=49511 Bug ID: 49511 Summary: Kontakt (Native Instruments) runtime is broken (regression) Product: Wine Version: 5.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pianoist(a)ya.ru Distribution: --- Created attachment 67637 --> https://bugs.winehq.org/attachment.cgi?id=67637 error example After migrating from the 5.01 to 5.10 (Ubuntu 19.10 to 20.20) Native instruments KONTAKT stopped load instruments, producing very strange list of errors like one attached. Such errors are not typical for KONTAKT and appear only when processing envelopes or LFO (internal structures, managed by GUI). After installing wine-stable 5.01 the problem disappeared -- 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 50454] New: Icons have non-transparent background in HxD
by WineHQ Bugzilla Jan. 8, 2021

Jan. 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=50454 Bug ID: 50454 Summary: Icons have non-transparent background in HxD Product: Wine Version: 6.0-rc5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: gabrielopcode(a)gmail.com Distribution: --- Created attachment 69068 --> https://bugs.winehq.org/attachment.cgi?id=69068 Icons with pink background Since 61b9209221d28d5d02379791ac1316c1fc2ca3b7, adding 32bpp images to an image list doesn't mask out the background via mask anymore, even though the mask is processed properly. Icons in HxD, for example, have pink background instead of transparent. (see attachment) Prior to that patch, the alpha itself was modified for the background, which was also wrong as tests show. I've sent a patch to wine-devel that masks out the background while preserving the alpha channel. -- 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 50453] New: CDB (Part of Debugging Tools for Windows) fails resume debugging after entry point break (continue debug event: 'DBG_EXCEPTION_HANDLED' is an alias for 'DBG_CONTINUE')
by WineHQ Bugzilla Jan. 8, 2021

Jan. 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=50453 Bug ID: 50453 Summary: CDB (Part of Debugging Tools for Windows) fails resume debugging after entry point break (continue debug event: 'DBG_EXCEPTION_HANDLED' is an alias for 'DBG_CONTINUE') Product: Wine Version: 6.0-rc5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. Found while trying to debug .NET executable with SOS Debugging Extension for windbg/cdb. --- snip --- ... 00d8: queue_exception_event( first=1, code=80000003, flags=00000000, record=00000000, address=7bc46838, len=24, params={00000000,00000000,00000000} ) 00d8: *sent signal* signal=10 00d8: queue_exception_event() = 0 { handle=003c } ... 0024:Ret KERNEL32.WaitForDebugEvent() retval=00000001 ret=022f28c5 0024:Call KERNEL32.SuspendThread(0000007c) ret=022f1d59 0024:Call ntdll.NtSuspendThread(0000007c,0031e0d4) ret=7b04c5a3 0024: suspend_thread( handle=007c ) 0024: suspend_thread() = 0 { count=0 } 0024:Ret ntdll.NtSuspendThread() retval=00000000 ret=7b04c5a3 0024:Ret KERNEL32.SuspendThread() retval=00000000 ret=022f1d59 0024:Call KERNEL32.GetThreadContext(0000007c,007f3aa0) ret=022f2009 0024: get_thread_context( handle=007c, flags=0000003f ) 00d8: *signal* signal=19 0024: get_thread_context() = 0 { self=0, handle=0000, context={cpu=x86,eip=7bc46839,esp=0031ef68,ebp=0031efcc,eflags=00000246,cs=0023,ss=002b,ds=002b,es=002b,fs=0063,gs=006b,eax=ffffffff,ebx=7bc6d2c0,ecx=0031ef7c,edx=0031efc4,esi=0031ef6c,edi=7ffc2000,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,fp.ctrl=ffff027f,fp.status=ffff0020,fp.tag=ffffffff,fp.err_off=f7ccf321,fp.err_sel=00000023,fp.data_off=0031e800,fp.data_sel=ffff002b,fp.cr0npx=00000020,fp.reg0=0,fp.reg1=0,fp.reg2=0,fp.reg3=0,fp.reg4=0,fp.reg5=0,fp.reg6=0,fp.reg7=1.16561e+12,extended={0020027f,...,00000000}} } ... 0024:Call KERNEL32.ReadProcessMemory(00000078,7bc46838,0031eaaf,00000001,0031e9f8) ret=022f1432 0024:Call ntdll.NtReadVirtualMemory(00000078,7bc46838,0031eaaf,00000001,0031e9f8) ret=7b0294ec 0024: read_process_memory( handle=0078, addr=7bc46838 ) 00d8: *signal* signal=19 0024: read_process_memory() = 0 { data={cc} } 0024:Ret ntdll.NtReadVirtualMemory() retval=00000000 ret=7b0294ec 0024:Ret KERNEL32.ReadProcessMemory() retval=00000001 ret=022f1432 ... 0024:Call KERNEL32.SetThreadContext(0000007c,007f3aa0) ret=022f2095 0024:Call ntdll.NtSetContextThread(0000007c,007f3aa0) ret=7b04be93 0024: set_thread_context( handle=007c, context={cpu=x86,eip=7bc46839,esp=0031ef68,ebp=0031efcc,eflags=00000246,cs=0023,ss=002b,ds=002b,es=002b,fs=0063,gs=006b,eax=ffffffff,ebx=7bc6d2c0,ecx=0031ef7c,edx=0031efc4,esi=0031ef6c,edi=7ffc2000,dr0=00000000,dr1=00000000,dr2=00000000,dr3=00000000,dr6=00000000,dr7=00000000,fp.ctrl=ffff027f,fp.status=ffff0020,fp.tag=ffffffff,fp.err_off=f7ccf321,fp.err_sel=00000023,fp.data_off=0031e800,fp.data_sel=ffff002b,fp.cr0npx=00000020,fp.reg0=0,fp.reg1=0,fp.reg2=0,fp.reg3=0,fp.reg4=0,fp.reg5=0,fp.reg6=0,fp.reg7=1.16561e+12,extended={0020027f,...,00000000}} ) 0024: set_thread_context() = 0 { self=0 } 0024:Ret ntdll.NtSetContextThread() retval=00000000 ret=7b04be93 0024:Ret KERNEL32.SetThreadContext() retval=00000001 ret=022f2095 ... 0024:Call KERNEL32.ResumeThread(0000007c) ret=022f1de9 0024:Call ntdll.NtResumeThread(0000007c,0031e614) ret=7b04be53 0024: resume_thread( handle=007c ) 0024: resume_thread() = 0 { count=1 } 0024:Ret ntdll.NtResumeThread() retval=00000000 ret=7b04be53 0024:Ret KERNEL32.ResumeThread() retval=00000001 ret=022f1de9 ... 0024:Call KERNEL32.ContinueDebugEvent(000000d4,000000d8,00010001) ret=022f2b24 0024: continue_debug_event( pid=00d4, tid=00d8, status=65537 ) 0024: continue_debug_event() = INVALID_PARAMETER 0024:Call ntdll.RtlNtStatusToDosError(c000000d) ret=7b00f5ff 0024:Ret ntdll.RtlNtStatusToDosError() retval=00000057 ret=7b00f5ff 0024:Ret KERNEL32.ContinueDebugEvent() retval=00000000 ret=022f2b24 0024:Call KERNEL32.GetLastError() ret=022f2b2e 0024:Ret KERNEL32.GetLastError() retval=00000057 ret=022f2b2e ... 0024:Call KERNEL32.WideCharToMultiByte(00000000,00000000,02338080 L"Win32 error 0n87",ffffffff,00000000,00000000,00000000,00000000) ret=020f669a ... 0024:Call KERNEL32.WideCharToMultiByte(00000000,00000000,020285d8 L"This usually indicates that the debuggee has been\nkilled out from underneath the debugger.\nYou can use .tlist to see if the debuggee still exists.\n",ffffffff,00000000,00000000,00000000,00000000) ret=020f669a --- snip --- Microsoft docs: https://docs.microsoft.com/en-us/windows/win32/api/debugapi/nf-debugapi-con… It's not listed there but common knowledge that 'DBG_EXCEPTION_HANDLED' is an alias for 'DBG_CONTINUE' in 32-bit environment. Also mentioned here: https://source.winehq.org/git/wine.git/commitdiff/fe36b7baca253f1e95cc790b8… ("ntdll: Made DBG_EXCEPTION_HANDLED a synonym of DBG_CONTINUE for exception handlers."), in 2005 --- snip --- $ grep -Hrni DBG_EXCEPTION_HANDLED include/ntstatus.h:1694:#define DBG_EXCEPTION_HANDLED ((NTSTATUS) 0x00010001) include/winerror.h:640:#define ERROR_DBG_EXCEPTION_HANDLED 766 include/winnt.h:652:#define DBG_EXCEPTION_HANDLED ((DWORD) 0x00010001) dlls/ntdll/error.c:196: ERROR_DBG_EXCEPTION_HANDLED, /* 00010001 (DBG_EXCEPTION_HANDLED) */ dlls/ntdll/tests/error.c:543: cmp2(DBG_EXCEPTION_HANDLED, ERROR_DBG_EXCEPTION_HANDLED); dlls/ntdll/unix/thread.c:430: if (status == DBG_CONTINUE || status == DBG_EXCEPTION_HANDLED) dlls/ntdll/unix/signal_arm64.c:669: if (status == DBG_CONTINUE || status == DBG_EXCEPTION_HANDLED) dlls/ntdll/unix/signal_i386.c:1615: if (status == DBG_CONTINUE || status == DBG_EXCEPTION_HANDLED) dlls/ntdll/unix/signal_x86_64.c:1982: if (status == DBG_CONTINUE || status == DBG_EXCEPTION_HANDLED) dlls/ntdll/unix/signal_arm.c:571: if (status == DBG_CONTINUE || status == DBG_EXCEPTION_HANDLED) dlls/ntdll/make_errors:67: DBG_EXCEPTION_HANDLED ERROR_DBG_EXCEPTION_HANDLED --- snip --- Wine source: https://source.winehq.org/git/wine.git/blob/9b12eae9ea445bbdeae196312fb65d2… --- snip --- 674 /* Continue a debug event */ 675 DECL_HANDLER(continue_debug_event) 676 { 677 struct process *process; 678 679 if (req->status != DBG_EXCEPTION_NOT_HANDLED && 680 req->status != DBG_CONTINUE && 681 req->status != DBG_REPLY_LATER) 682 { 683 set_error( STATUS_INVALID_PARAMETER ); 684 return; 685 } 686 687 if ((process = get_process_from_id( req->pid ))) 688 { 689 struct thread *thread = get_thread_from_id( req->tid ); 690 if (thread) 691 { 692 continue_debug_event( process, thread, req->status ); 693 release_object( thread ); 694 } 695 release_object( process ); 696 } 697 } ---- snip --- Following relevant changes made this a regression: * https://source.winehq.org/git/wine.git/commitdiff/7332de64a5a204cc285bdc1f8… ("server: Validate status in continue_debug_event."), Part of Wine 5.2 * https://source.winehq.org/git/wine.git/commitdiff/e2a1f00a3850dbce89ec0f85b… ("server: Implement DBG_REPLY_LATER handling.") With a fix applied, debugging (resuming) with CDB works again. $ wine --version wine-6.0-rc5 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 5

[Bug 50437] New: wineserver crashes when running SteelSeries Engine client
by WineHQ Bugzilla Jan. 8, 2021

Jan. 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=50437 Bug ID: 50437 Summary: wineserver crashes when running SteelSeries Engine client Product: Wine Version: 5.20 Hardware: x86-64 URL: https://web.archive.org/web/20210101175629/https://eng ine.steelseriescdn.com/SteelSeriesEngine3.17.3Setup.ex e OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Regression SHA1: 0bbd3f66178abdc6ea15d30d2eb3b033367f8407 Distribution: --- The crash is due to heap corruption. It can usually be triggered by running the client through `wine start "SteelSeries Engine 3 Launcher.lnk"`; it either crashes almost immediately or after trying to close the main window. Needs `winetricks -q corefonts` (bug 32342). -- 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 49500] New: Wine is not displaying any windows
by WineHQ Bugzilla Jan. 8, 2021

Jan. 8, 2021

https://bugs.winehq.org/show_bug.cgi?id=49500 Bug ID: 49500 Summary: Wine is not displaying any windows Product: Wine Version: 5.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vld10(a)yandex.ru Distribution: --- If no monitor attached, wine is not displaying any windows. Trying to run winecfg. On wine-4.0.3 all works as expected. On wine-5.0 & wine-5.11 no window is displayed, although programs seems to work. In both cases, running winecfg via terminal, produces an output. Setup: start X via /etc/init.d/xdm; connect to display via x11vnc when necessary. Workaround1: do xinit -- /usr/bin/X -extension RANDR. Workaround2: do xinit -- /usr/bin/Xvfb Here is my xrandr output for default Setup: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096 VGA-1 disconnected primary (normal left inverted right x axis y axis) Here is my xrandr output for Workaround 2: xrandr: Failed to get size of gamma for output screen Screen 0: minimum 1 x 1, current 1280 x 1024, maximum 1280 x 1024 screen connected 1280x1024+0+0 0mm x 0mm 1280x1024 0.00* I think this is enough info to reproduce. Let me know what logs to provide. -- 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 29