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

[Bug 19667] New: Demo for Total Annihilation: mouse scrolling of screen unworkable.
by wine-bugs＠winehq.org Nov. 15, 2019

Nov. 15, 2019

http://bugs.winehq.org/show_bug.cgi?id=19667 Summary: Demo for Total Annihilation: mouse scrolling of screen unworkable. Product: Wine Version: 1.1.27 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: hughperkins(a)gmail.com Demo for Total Annihilation: mouse scrolling of screen unworkable. On screens that cannot run at 640x480 resolution, the demo of Total Annihilation has to run in a virtual desktop in order to run at all, otherwise it crashes. This is not I feel the bug. The issue targeted by this bug report is that it is unworkably hard to scroll around the game world by moving the mouse pointer to the edges of the window, since the mouse pointer has to be positioned *exactly* on the edge of the window, which is possible, but detracts from the gameplay experience to the point as to be unplayable. A possible solution to this issue (which is not really a bug, so much as a lack of a feature I feel), could be to make it possible to enforce in wincfg that the mouse is locked to a particular region of the window or screen, by default to the window itself. wincfg could provide the possibility to specify a keyboard shortcut to unlock the mouse when necessary, or simply, by alt-tabbing out of the window, the mouse could be unlocked. For an example of another environment that implements this, you could look for example at dosbox. If you run for example populous in dosbox in a window, it works perfectly I feel, by locking the mouse pointer to the window, and one can use ctrl-f10 to free it, which I feel is totally unintuitive, but I feel works fine. -- 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 14

[Bug 47807] New: Wine Mono fails to install fakedlls
by WineHQ Bugzilla Nov. 15, 2019

Nov. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=47807 Bug ID: 47807 Summary: Wine Mono fails to install fakedlls Product: Wine Version: 4.16 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- When creating a new prefix and installing Wine Mono by downloading the msi, fakedlls are not installed in c:\windows\Microsoft.NET. For example, fusion.dll is missing. I do not believe this was caused by a change in Wine Mono. This may be relevant: 001c:err:msi:execute_command unable to execute command 2 001c:err:msi:execute_command unable to execute command 2 -- 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 48019] New: SSE register MXCSR is wrong for new threads
by WineHQ Bugzilla Nov. 15, 2019

Nov. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=48019 Bug ID: 48019 Summary: SSE register MXCSR is wrong for new threads Product: Wine Version: 4.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: mterrisse(a)free.fr Distribution: --- Created attachment 65554 --> https://bugs.winehq.org/attachment.cgi?id=65554 Command line executable with source code to get MXCSR in a new created thread Hello, I am running Wine 4.15 64 bits (PlayOnLinux) on Ubuntu 19.10 (More recent versions of Wine are not available yet). On Windows when a new thread is created (CreateThread), the value of the SSE register MXCSR is initialized to 0x1f80. But for Wine 4.15 on Ubuntu, it is initialized to 0x1920. This is fatal for our programs that use libcef.dll (Chromium Embedded Framework), this library creates new renderer threads, doesn't set the MXCSR register (so exceptions due to denormalization of floats are not masked), then there is an unhandled exception and the whole program crashes. I tested with Wine 4.18 on macOS 10.15.1 Catalina, I get the correct value 0x1f80, and indeed there is no crash on macOS. So this is specific to Wine on Linux (except is something has changed between Wine 4.15 and Wine 4.18). Here attach you can find a command line executable with source code (Delphi) that displays the value of MXCSR for a new thread. Thank you for your help. Regards, Michel Terrisse -- 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 35821] New: wPrime 2.09 (VB6 app) reports 'Run-time error 445: Object doesn't support this action' (needs ITextStream ReadLine method implementation)
by wine-bugs＠winehq.org Nov. 15, 2019

Nov. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=35821 Bug ID: 35821 Summary: wPrime 2.09 (VB6 app) reports 'Run-time error 445: Object doesn't support this action' (needs ITextStream ReadLine method implementation) Product: Wine Version: 1.7.14 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: scrrun Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Hello folks, as the summary says ... Prerequisite: 'winetricks -q vb6run' --- snip --- $ WINEDEBUG=+tid,+seh,+relay,+msi,+scrrun,+vbscript wine ./wPrime.exe >>log.txt 2>&1 ... 0041:trace:scrrun:filesys_OpenTextFile (0x7e274450)->(L"wprime.exe" 1 0 0 0x33f808) 0041:Call ntdll.RtlAllocateHeap(00110000,00000000,00000028) ret=7e256408 0041:Ret ntdll.RtlAllocateHeap() retval=00148be0 ret=7e256408 0041:Call KERNEL32.CreateFileW(004058dc L"wprime.exe",80000000,00000000,00000000,00000003,00000080,00000000) ret=7e257c80 0041:Ret KERNEL32.CreateFileW() retval=000000a4 ret=7e257c80 0041:Call KERNEL32.GetFileSizeEx(000000a4,00148bf8) ret=7e257cd9 0041:Ret KERNEL32.GetFileSizeEx() retval=00000001 ret=7e257cd9 0041:trace:scrrun:textstream_QueryInterface (0x148be0)->({53bad8c1-e718-11cf-893d-00a0c9054228} 0x33f6e8) 0041:trace:scrrun:textstream_AddRef (0x148be0)->(2) 0041:trace:scrrun:textstream_Release (0x148be0)->(1) 0041:trace:scrrun:textstream_get_AtEndOfStream (0x148be0)->(0x33f7b4) 0041:Call KERNEL32.SetFilePointerEx(000000a4,00000000,00000000,0033f6b8,00000001) ret=7e257217 0041:Ret KERNEL32.SetFilePointerEx() retval=00000001 ret=7e257217 0041:fixme:scrrun:textstream_ReadLine (0x148be0)->(0x33f814): stub 0041:trace:scrrun:textstream_AddRef (0x148be0)->(2) 0041:trace:scrrun:textstream_QueryInterface (0x148be0)->({df0b3d60-548f-101b-8e65-08002b2bd119} 0x33f698) 0041:trace:scrrun:textstream_Release (0x148be0)->(1) ... 0041:Call KERNEL32.RaiseException(c000008f,00000001,00000002,0033f678) ret=660d0956 0041:trace:seh:raise_exception code=c000008f flags=1 addr=0x7b83ab23 ip=7b83ab23 tid=0041 0041:trace:seh:raise_exception info[0]=deadcafe 0041:trace:seh:raise_exception info[1]=deadcafe 0041:trace:seh:raise_exception eax=7b826b89 ebx=7b8bb000 ecx=deadcafe edx=0033f5d4 esi=0033f678 edi=0033f640 0041:trace:seh:raise_exception ebp=0033f618 esp=0033f5b4 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000283 0041:trace:seh:call_stack_handlers calling handler at 0x401b66 code=c000008f flags=1 ... 0041:Call KERNEL32.WideCharToMultiByte(00000000,00000000,0014a644 L"Run-time error '445':\n\nObject doesn't support this action",ffffffff,00bbf0f8,00000072,00000000,00000000) ret=660711c4 --- snip --- Source: http://source.winehq.org/git/wine.git/blob/038438ad696fc936a6bae5669bc0f35d… --- snip --- 374 static HRESULT WINAPI textstream_ReadLine(ITextStream *iface, BSTR *text) 375 { 376 struct textstream *This = impl_from_ITextStream(iface); 377 FIXME("(%p)->(%p): stub\n", This, text); 378 379 if (textstream_check_iomode(This, IORead)) 380 return CTL_E_BADFILEMODE; 381 382 return E_NOTIMPL; 383 } --- snip --- $ sha1sum wPrime.exe 68fe810b959eec35e875994f14f6356aca5cc19d wPrime.exe $ du -sh wPrime.exe 2.6M wPrime.exe $ wine --version wine-1.7.14-185-g5cf20ce 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.

2 7

[Bug 47349] New: TesModManager require SetFileInformationByHandle with FileBasicInfo to properly set file timestamps
by wine-bugs＠winehq.org Nov. 15, 2019

Nov. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=47349 Bug ID: 47349 Summary: TesModManager require SetFileInformationByHandle with FileBasicInfo to properly set file timestamps Product: Wine Version: 4.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Distribution: --- Hi. The Application TesModManager 1.6.50(a .NET Mod Manager for Bethesda Games) require SetFileInformationByHandle with FileBasicInfo to be able to sucessfully set file timestamp. Setting the timestamp is required for mods load order on some bethesda games as Tes4 Oblivion. on the log: 0009:fixme:file:SetFileInformationByHandle 0xd0, 0, 0x34f358, 40 -- 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 47885] New: [regression] [bisected] games are now restricted to resolutions not bigger than the virtual desktop
by WineHQ Bugzilla Nov. 15, 2019

Nov. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=47885 Bug ID: 47885 Summary: [regression] [bisected] games are now restricted to resolutions not bigger than the virtual desktop Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: mtmkls(a)gmail.com Distribution: --- If wine is set to emulate a virtual desktop of 1024x768 for example, games cannot set any resolution higher than that. Previously they were able to set any resolution up to the real resolution of the monitor. 25167fb286822c93582457815bcf069fef040976 is the first bad commit commit 25167fb286822c93582457815bcf069fef040976 Author: Zhiyi Zhang <zzhang(a)codeweavers.com> Date: Wed Aug 14 16:23:55 2019 +0800 winex11.drv: Make screen helpers independent of Xinerama. So that other display device handlers such as XRandR can be introduced because they might report a virtual screen size with different top-left corner and the primary screen may be different as well. Signed-off-by: Zhiyi Zhang <zzhang(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/winex11.drv/display.c | 70 +++++++++++++++++++++++++++++++++++++++++++++ dlls/winex11.drv/xinerama.c | 33 --------------------- 2 files changed, 70 insertions(+), 33 deletions(-) Please revert to the old behavior. -- 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 47305] New: Notepad doesn't adjust caret and scroll position properly
by wine-bugs＠winehq.org Nov. 15, 2019

Nov. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=47305 Bug ID: 47305 Summary: Notepad doesn't adjust caret and scroll position properly Product: Wine Version: 4.9 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- This is just to track the issue here, I'll send in a patch soon. Found on https://jira.reactos.org/browse/CORE-15780. Issue description from ReactOS JIRA: How to reproduce: Open Notepad Make sure you disabled word wrapping (it usually disabled by default) Type in very long string to activate horizontal scroll bar Make a new string (hit Enter) Now your caret position would be somewhere at the beginning of line 2, but the whole text box is not scrolled to the first character position, and horizontal scroll bar position is not changed (see attached screenshot). If you move your caret back to line 1 ending, and move with arrow keys to line 2, the bug will appear again (it does not matter whether right or down arrow key will be used). -- 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 47815] New: Virtual desktop is missing window decorations
by WineHQ Bugzilla Nov. 15, 2019

Nov. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=47815 Bug ID: 47815 Summary: Virtual desktop is missing window decorations Product: Wine Version: 4.16 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: huw(a)codeweavers.com, zzhang(a)codeweavers.com Regression SHA1: efbbe66669a060dd01b3ae399f5a9e7328312f03 Distribution: ArchLinux efbbe66669a060dd01b3ae399f5a9e7328312f03 is the first bad commit commit efbbe66669a060dd01b3ae399f5a9e7328312f03 Author: Zhiyi Zhang <zzhang(a)codeweavers.com> Date: Fri Sep 20 16:54:31 2019 +0800 winex11.drv: Initialize display devices before getting primary desktop rectangle. Otherwise, the retrieved primary desktop might be from the last explorer instance if we launch new explorer instances before wine server fully shuts down. Signed-off-by: Zhiyi Zhang <zzhang(a)codeweavers.com> Signed-off-by: Huw Davies <huw(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/winex11.drv/desktop.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) This is on KDE 5.16.4. -- 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 15

[Bug 47958] New: Mi PC Suite: It won't install
by WineHQ Bugzilla Nov. 15, 2019

Nov. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=47958 Bug ID: 47958 Summary: Mi PC Suite: It won't install Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: propsys Assignee: wine-bugs(a)winehq.org Reporter: txus.mipanas(a)gmail.com Distribution: --- Created attachment 65463 --> https://bugs.winehq.org/attachment.cgi?id=65463 Here is the error log It starts installing and then shows an error with the attachment's log. Download link: http://bigota.d.miui.com/MiFlash/MiSetup2.2.0.7032_2717.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.

1 4

[Bug 40442] New: Unexplained new random comctl32:header failure (cross-compiler issue?)
by wine-bugs＠winehq.org Nov. 15, 2019

Nov. 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=40442 Bug ID: 40442 Summary: Unexplained new random comctl32:header failure (cross-compiler issue?) Product: Wine Version: 1.9.6 Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:header started having regular failures on newtb-wxppro right after the WineHQ upgrade (2016/03/17). https://test.winehq.org/data/tests/comctl32:header.html The failure: header.c:1148: Test failed: expected 0, got 1 Things that point to a cross-compiling issue: * Since 2016/03/18 comctl32:header has had an almost systematic failure on newtb-wxppro (68.7%) and more rarely on newtb-w2003std (12.5%). * In the 27 runs from 2016/02/09 to 2016/03/17 it had no failure (neither on these two platforms nor on any other). * There has been no change to comctl32:header before it started failing. * The tests that run before comctl32:header don't seem to have undergone changes that could cause the following tests to fail (see 'git log 62277fb7779f..6bc0ce26a853 dlls/[abc]*/tests'). Unexplained mysteries: * Cross-compiling the test with i686-w64-mingw32-gcc (GCC) 5.3.1 20160205, the standard '-g -O2' options and uploading it to the TestBot does not yield the expected failure (changing that to '-g -O0' does not make a difference either). * None of the other platforms is affected. * And even more strange, newtb-xppro is the only Windows XP to be affected by the new failure. -- 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