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

[Bug 46216] New: Lords of the Fallen needs ThreadEnableAlignmentFaultFixup
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=46216 Bug ID: 46216 Summary: Lords of the Fallen needs ThreadEnableAlignmentFaultFixup Product: Wine Version: 3.21 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Spamming output after launching: fixme:thread:NtSetInformationThread info class 7 not supported yet wine-3.21-114-g1582ae6b04 -- 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 26541] New: Dragon Saga doesn't start
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

http://bugs.winehq.org/show_bug.cgi?id=26541 Summary: Dragon Saga doesn't start Product: Wine Version: 1.3.16 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Installing DragonSagaInstaller-0.1.29-20110216.msi went fine, but $ cd ~/.wine/drive_c/Program Files/Gravity/Dragon Saga $ wine Release/DragonSaga.EXE fails like this: fixme:ntdll:NtQueryInformationProcess (process=0xffffffff) Unimplemented information class: ProcessDebugFlags Unhandled exception: privileged instruction in 32-bit code (0x0123980c). Backtrace: =>0 0x0123980c in dragonsaga (+0xe4980c) (0x0032fea0) 1 0x7edaa2fc call_process_entry+0xb() in kernel32 (0x0032feb8) 2 0x7edac593 start_process+0x52(peb=0x1) [dlls/kernel32/process.c:1086] in kernel32 -- 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 6

[Bug 28089] New: exception handling code touches stack for exceptions handled by the debugger
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

http://bugs.winehq.org/show_bug.cgi?id=28089 Summary: exception handling code touches stack for exceptions handled by the debugger Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: bernhardloos(a)googlemail.com Created an attachment (id=35971) --> (http://bugs.winehq.org/attachment.cgi?id=35971) a hack to work around the problem Wine places the CONTEXT and EXCEPTION_RECORD structures onto the stack past ESP during the unix signal handler and continues with most of the exception handling code outside of the signal handler. Unfortunately and contrary to windows behavior the debugger gets notified only after this happens. Windows doesn't touch the stack at all, if the exception is handled by the debugger. This makes it very hard to single step trough code which keeps useful data past ESP (securom 8 for example). it's easy to show with this small test: void foo() { char *x = 0, *y = 0, *from = 0, *to = 0; char c; x = &c; y = &c - 500; while (y != x) *y++ = 0x55; c = 0x77; /* single step a few times here */ y = &c - 500; while (y != x) { if (*y != 0x55) if (from) to = y; else from = y; y++; } /* to and from shoudl be NULL */ } -- 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 13

[Bug 43567] New: Vietcong - game crashes during radiocalls
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=43567 Bug ID: 43567 Summary: Vietcong - game crashes during radiocalls Product: Wine Version: 2.14 Hardware: x86-64 URL: http://www.moddb.com/games/vietcong/downloads/vietcong -singleplayer-demo OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: havran.jan(a)email.cz Distribution: ArchLinux Created attachment 58977 --> https://bugs.winehq.org/attachment.cgi?id=58977 Vietcong - terminal log Vietcong crashes when radiocall icon is shown. This bug is also reproduciable on Windows > Vista, but it works on Windows XP. There exists community tool: VCStarter, which fixes this for newer Windows and also for Wine. I have spoke with VCStarter creator and he told me that the game uses some dirty assembler in that part (maybe part of anticheat protection or no-cd crack?). I have doubts if it is really Wine bug, but since this game works on Windows <= XP, it should also work on Wine (with Win XP compatibility). PS: You will not be able tu run this game probably because of bug #9337. As a workaround, you can use VCStarter (version 1.7 only, older versions did not fix the bug) or patch from bug #39057 - all this is described in bug #9337 PPS: While patch from bug #39057 fixes bug #9337 crashing for all Vietcong versions, VCStarter works only with Vietcong 1.60 (so it does not work with Vietcong demo version). -- 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 13

[Bug 50171] New: 32-bit PE entry point no longer called through BaseThreadInitThunk() assembly wrapper when Wine is built with LLVM MinGW
by WineHQ Bugzilla Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=50171 Bug ID: 50171 Summary: 32-bit PE entry point no longer called through BaseThreadInitThunk() assembly wrapper when Wine is built with LLVM MinGW Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, while investigating bug 28332 I found a regression introduced by https://source.winehq.org/git/wine.git/commitdiff/0c631ebb2354334eaf309bc07… ("kernel32: Build with msvcrt."). With 32-bit kernel32 cross-compiled to PE format, the stack on app entry point is now aligned to 16-byte boundary. This makes the game from bug 28332 "magically" work while the 32-bit non-PE kernel32 causes a crash (expected due to Wine quartz bug). https://bugs.winehq.org/show_bug.cgi?id=28332#c17 The stack alignment from entry point, including selected functions from the call chain up to alloca() caller. --- snip --- EIP | PE ESP | non-PE ESP | comment 0x42D5E3 | 0x31FF60 +00 | 0x31FF44 +00 | entry point main thread 0x42A720 | 0x31FEA0 +C0 | 0x31FE84 +C0 | 0x4200C5 | 0x31FE54 +4C | 0x31FE38 +4C | 0x40D8B7 | 0x31FE4C +08 | 0x31FE30 +08 | 0x40D570 | 0x31FE48 +04 | 0x31FE2C +04 | 0x40D6FF | 0x31FB1C +32C | 0x31FB00 +32C | before alloca(0) 0x40D704 | 0x31FB10 +0C | 0x31FB00 +00 | after alloca(0) --- snip --- It seems in 32-bit PE kernel32.dll, the thread entry point is called through the fastcall "C" version of BaseThreadInitThunk() instead of the fastcall assembly wrapper. 32-bit non-PE kernel32.dll.so works correctly, the thread entry point is called through __fastcall_BaseThreadInitThunk() assembly wrapper. https://source.winehq.org/git/wine.git/blob/bedfb9cae224a369efa4588332a5518… --- snip --- 36 #ifdef __i386__ 37 __ASM_STDCALL_FUNC( __fastcall_BaseThreadInitThunk, 12, 38 "pushl %ebp\n\t" 39 __ASM_CFI(".cfi_adjust_cfa_offset 4\n\t") 40 __ASM_CFI(".cfi_rel_offset %ebp,0\n\t") 41 "movl %esp,%ebp\n\t" 42 __ASM_CFI(".cfi_def_cfa_register %ebp\n\t") 43 "pushl %ebx\n\t" 44 __ASM_CFI(".cfi_rel_offset %ebx,-4\n\t") 45 "movl 8(%ebp),%ebx\n\t" 46 /* deliberately mis-align the stack by 8, Doom 3 needs this */ 47 "pushl 4(%ebp)\n\t" /* Driller expects readable address at this offset */ 48 "pushl 4(%ebp)\n\t" 49 "pushl %ebx\n\t" 50 "call *%edx\n\t" 51 "movl %eax,(%esp)\n\t" 52 "call " __ASM_STDCALL( "RtlExitUserThread", 4 )) 53 #endif 54 55 /*********************************************************************** 56 * BaseThreadInitThunk (KERNEL32.@) 57 */ 58 void __fastcall BaseThreadInitThunk( DWORD unknown, LPTHREAD_START_ROUTINE entry, void *arg ) 59 { 60 RtlExitUserThread( entry( arg ) ); 61 } --- snip --- https://source.winehq.org/git/wine.git/blob/bedfb9cae224a369efa4588332a5518… --- snip --- 185 @ stdcall -fastcall BaseThreadInitThunk(long ptr ptr) --- snip --- cross-toolchain used: LLVM MinGW 20201020 with LLVM stable 11.0.0 https://github.com/mstorsjo/llvm-mingw https://github.com/mstorsjo/llvm-mingw/releases https://github.com/mstorsjo/llvm-mingw/releases/download/20201020/llvm-ming… $ wine --version wine-5.22 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 33310] New: Minimizing window erases chess board in Shredder Classic 4 Windows
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

http://bugs.winehq.org/show_bug.cgi?id=33310 Bug #: 33310 Summary: Minimizing window erases chess board in Shredder Classic 4 Windows Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: clavius(a)live.com Classification: Unclassified Minimizing the program window causes the play area to come up blank upon re-maximization in Shredder Classic 4 Windows chess. To duplicate the bug: 1) Obtain Shredder Classic 4 Windows demo from http://download.shredderchess.com/pc/sc4/prg/myscl/SetupShredderClassic4.exe 2) Install the program under Wine. I've tested this with Wine versions 1.4 and several 1.5 releases under both Ubuntu and openSUSE Linux, 64-bit OS. 3) Start the program either by command-line or clicking the icon. You'll see the normal Shredder game screen. Start a new game to get a chess board. 4) Minimize the Shredder window. 5) Now maximize the window again, and the game play area (chess board and all) will have disappeared. This happens with any combination of layouts and chess sets I've tried (most if not all, including the 3d ones). This screen re-draw issue seems to be the only one I haven't been able to resolve by downloading winetricks and various Microsoft runtime libraries. Shredder for Windows offers a few features unavaiable in the native Linux version, including the ability to play Chess960. It also has, in my opinion, a nicer looking GUI. Would be nice to play under Wine. -- 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 12

[Bug 18508] New: Sony Acid Pro 7 Fails to Install
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

http://bugs.winehq.org/show_bug.cgi?id=18508 Summary: Sony Acid Pro 7 Fails to Install Product: Wine Version: unspecified Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: aliendude5300(a)gmail.com Created an attachment (id=21153) --> (http://bugs.winehq.org/attachment.cgi?id=21153) What debug messages appeared during installation of Sony Acid Pro 7 on default Wine installation. The installer for Sony Acid Pro 7 fails to install the necessary files and exits in Wine 1.1.21. -- 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 16

[Bug 50248] New: Cannot install Fantasy Grounds Unity VTT
by WineHQ Bugzilla Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=50248 Bug ID: 50248 Summary: Cannot install Fantasy Grounds Unity VTT Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: bignastydragon(a)gmail.com Distribution: --- Created attachment 68759 --> https://bugs.winehq.org/attachment.cgi?id=68759 Program error details Cannot install Fantasy Grounds Unity VTT but I am still able to run the Classic version of FG https://www.fantasygrounds.com/store/ -- 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 50096] New: Performance Regression in Secondhand Lands
by WineHQ Bugzilla Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=50096 Bug ID: 50096 Summary: Performance Regression in Secondhand Lands Product: Wine Version: 5.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: escomk3(a)hotmail.com Distribution: --- Created attachment 68573 --> https://bugs.winehq.org/attachment.cgi?id=68573 Good and Bad Terminal Output (+xranrd) After 9905a5a8 [1], the maximum FPS reached in Secondhand Lands can be around 5, when it is around 30-120 (120 being the maximum limit) depending on the situation before this commit. Running some quick profiling, there doesn't seem to be obvious (to me) differences between the good and the bad in that regard. Adding some TRACEs into the new code, I couldn't notice yet if anything there was being called a lot, but I did notice something that may or may not be a bit odd: In 'xrandr14_get_gpus2' [2] I'm seeing 'new_gpus: 4' and 'count: 3265744', which seems a "little bit" excessive (though I'm not sure if I'm doing things right at all, nor do I necessarily understand the code at all). This is how I was counting them: *new_gpus = gpus; TRACE("new_gpus: %d.\n"); *count = provider_resources->nproviders; TRACE("count: %d.\n", count); ret = TRUE; Download (no account is needed as the issues is visible in the main title menu already): - https://www.secondhandlands.com/download.php Some Winetricks are required to get the game running at all: - d3dx9_43 - d3dcompiler_43 Latest Wine version tested: - wine-5.20-234-gb793799d3d5 1. https://source.winehq.org/git/wine.git/commitdiff/9905a5a81d6baf59e992c5b2a… 2. https://source.winehq.org/git/wine.git/blob/9905a5a81d6baf59e992c5b2a8ea92e… -- 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 42095] New: winamp needs to be restarted for skins to change
by wine-bugs＠winehq.org Dec. 4, 2020

Dec. 4, 2020

https://bugs.winehq.org/show_bug.cgi?id=42095 Bug ID: 42095 Summary: winamp needs to be restarted for skins to change Product: Wine Version: 2.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winetest(a)luukku.com Distribution: --- This winamp version can be used for testing. https://winamp.en.softonic.com/download -- 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