October 2020 - Wine-bugs - list.winehq.org

[Bug 2155] Failure of SetFocus, SetActiveWindow and SetForegroundWindow
by WineHQ Bugzilla 08 Oct '20

08 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=2155 --- Comment #26 from Rémi Bernon <rbernon(a)codeweavers.com> --- Created attachment 68357 --> https://bugs.winehq.org/attachment.cgi?id=68357 Rebased user32-rawinput-hid series -- 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 2155] Failure of SetFocus, SetActiveWindow and SetForegroundWindow
by WineHQ Bugzilla 08 Oct '20

08 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=2155 Rémi Bernon <rbernon(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon(a)codeweavers.com --- Comment #25 from Rémi Bernon <rbernon(a)codeweavers.com> --- Created attachment 68356 --> https://bugs.winehq.org/attachment.cgi?id=68356 Patch series addressing several focus inconsistencies. I spent some time digging into focus issues lately and I believe this issue has several root causes. First of all of course, Wine currently doesn't implement any mechanism to activate other windows on the X11 side. This is implemented by the staged patch, but I believe it can then trigger other focus problems that Wine suffers from. With or without the patch, the root issues are: 1) I believe there's a race condition in the SetForegroundWindow / SetActiveWindow implementation. When multiple threads are involved, SetActiveWindow requests from other threads are only applied when the thread checks its messages, possibly overwriting changes that were done by the thread itself. 2) The asynchronous nature of the focus handling code: Wine applies the Win32 focus state changes immediately, but processes -- and applies -- the results of the X11 activation requests only later, during window message processing. 3) Windows allows hidden windows to be focused and foreground, X11 doesn't allow unmapped windows to be. This is a fundamental difference and it is pretty hard to solve, we currently implement hidden windows as unmapped X11 windows, as it is probably the only way to have truly invisible windows, but it makes it impossible to keep the X11 state consistent in that case. The solutions are either to map hidden windows, using some other mechanism to hide them as much as possible, bottom-most attribute being perhaps the least brittle. Or, as a possible mitigation, force change X11 focus when hidden window is supposed to be focused, so that X11 will send focus change events when it changes back to another window. 4) SetForegroundWindow is not supposed to always succeed, although Wine always pretend it does. The _NET_ACTIVE_WINDOW request also not always succeed, but as we can't wait for its possible result, it is hard to return a reliable success status. This is especially the case with the staged patch, that sends activation requests to be applied later, but it is also the case with user focus changes. Having the X11 events processed and applied only when message processing can trigger a race condition where X11 related focus changes will overwrite the already executed Win32 focus changes, possibly ending up in an inconsistent state. Also, because of 1), when focus events come on several threads, SetActiveWindow messages coming from other threads may be applied at the same as the X11 events are processed and applied, making things even more inconsistent. The attached patch series should help fixing these issues. First of all, it fixes the incorrect message processing order in 1). Then it should try to make 2) work better by tracking X11 focus globally in explorer.exe, so that we don't rely on application processing their messages anymore, and by discarding old SetForegroundWindow requests based on their timestamp. Last, it also implements a similar feature as the staged _NET_ACTIVE_WINDOW patch to send X11 activation requests, but it adds a mitigation for 3) and 4), where SetForegroundWindow returns failure if X11 focus is not on another Wine window, and where SetActiveWindow forcefully unsets X11 focus when hidden window is activated. It is still not completely matching Windows behavior, as SetForegroundWindow should probably return FALSE in more cases, but the details are a little bit more complicated and it may also break some currently working cases. I'm currently trying to upstream the first patches, but the way internal messages gets discarded needed some discussion. The whole series also could benefit from more extensive testing. This is also probably going to conflict with the rawinput patch series, as there are changes in the XInput2 code to get Focus messages with timestamps if possible. I'll attach rebased versions next in the eventuality this goes into staging. -- 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 49959] New: Error 430 class does not support automation
by WineHQ Bugzilla 08 Oct '20

08 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49959 Bug ID: 49959 Summary: Error 430 class does not support automation Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: handzdwn(a)protonmail.com Error 430 when trying open 911.re -- 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 4977] Mindstar Script Editor aborts on startup with "Runtime Error 430: Class does not support Automation..."
by WineHQ Bugzilla 07 Oct '20

07 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=4977 Methodmanx6 <handzdwn(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |handzdwn(a)protonmail.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 0

[Bug 39150] New: Devil May Cry 3 SE Screen is too bright.
by wine-bugs＠winehq.org 07 Oct '20

07 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=39150 Bug ID: 39150 Summary: Devil May Cry 3 SE Screen is too bright. Product: Wine Version: 1.7.49 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: SolisX007(a)yahoo.com Distribution: --- Hello Everyone, Devil May Cry 3 SE Screen is too bright. It almost looks like a white out. -- 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 32

[Bug 49955] New: Qt Creator installer does not show the selected tick when the component is selected
by WineHQ Bugzilla 07 Oct '20

07 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49955 Bug ID: 49955 Summary: Qt Creator installer does not show the selected tick when the component is selected Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- Created attachment 68346 --> https://bugs.winehq.org/attachment.cgi?id=68346 Screenshot showing the selected tick not visible on the selected line Summary Qt Creator installer does not show the selected tick when the component is selected Download location https://www.qt.io/download-thank-you?os=windows&hsLang=en $ sha256sum qt-unified-windows-x86-3.2.3-online.exe f4ac94370647375e557569f15d443ff8032687cca505db623a08422f3df02a5c qt-unified-windows-x86-3.2.3-online.exe Steps to reproduce 1) start the installer $ wine qt-unified-windows-x86-3.2.3-online.exe with the following settings: welcome -> next qt account -> make or input a qt account, next qt open source -> [X] i have read and approve the obligation of using open source qt, next setup -> next contribute -> [X] help us -> next Installation folder -> C:\Qt Select components Qt -> Qt 5.15.1 -> MinGw 8.1.0 32 bit Qt -> Developer and designer tools -> Qt Creator 4.13.2 CDB Debugger Support Support (default) Qt -> Developer and designer tools -> Debugging tools for windows (default) Qt -> Developer and designer tools -> CMake 3.17.1 64-bit (default) Qt -> Developer and designer tools -> Ninja 1.10.0 (default) Qt -> Developer and designer tools -> MinGW 8.1.0 32 bit (must match the Qt version above) After enabling a component, the selected tick is only visible when the line is not selected. See the screenshot. Versions: $ wine --version wine-5.18 (Staging) $ pacman -Q wine wine-staging 5.18-1 uname -a Linux cedric-p4 5.8.13-arch1-1 #1 SMP PREEMPT Thu, 01 Oct 2020 20:40:35 +0000 x86_64 GNU/Linux -- 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 49947] New: Winetricks on Fedora Requires Uninstall of WIne-Staging
by WineHQ Bugzilla 06 Oct '20

06 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49947 Bug ID: 49947 Summary: Winetricks on Fedora Requires Uninstall of WIne-Staging Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: knight00819(a)gmail.com Distribution: --- Created attachment 68337 --> https://bugs.winehq.org/attachment.cgi?id=68337 Terminal-log After installing Wine-staging for Fedora 32, attempting to install Winetricks warns the user that Wine-Staging conflicts with Wine-common and suggests uninstalling Wine-Staging to do so. -- 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 25390] New: wineconsole doesn't returns exit code of subprocess
by wine-bugs＠winehq.org 06 Oct '20

06 Oct '20

http://bugs.winehq.org/show_bug.cgi?id=25390 Summary: wineconsole doesn't returns exit code of subprocess Product: Wine Version: 1.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: cblp(a)cblp.su wineconsole should exit with the code, that was returned by nested command. Example 1. $ wineconsole cmd CMD Version 1.2 > thereisnosuchcommand File not found > echo %ERRORLEVEL% 9009 > exit $ echo $? 0 Example 2. $ wineconsole thereisnosuchcommand wine: cannot find L"C:\\windows\\system32\\thereisnosuchcommand.exe" wineconsole: Starting command "thereisnosuchcommand" failed. The command is invalid. $ echo $? 0 And always 0, regardless of subprocess. -- 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 7

[Bug 43166] New: Skyrim on FreeBSD will only work a few seconds after being in the world ( after the menu)
by wine-bugs＠winehq.org 06 Oct '20

06 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=43166 Bug ID: 43166 Summary: Skyrim on FreeBSD will only work a few seconds after being in the world (after the menu) Product: Wine Version: 2.7 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com Created attachment 58421 --> https://bugs.winehq.org/attachment.cgi?id=58421 Output of the terminal at the exact moment when the problem occurs Everything is working fine until I load a saved game to continue my old character from FreeBSD. It will work the same way as on GNU/Linux for just a few seconds then will freeze while the led of my hard drive disk will stay lit as to say my hard drive disk is working a lot. After a few seconds, the game will close, the hard drive disk led will turn off and I'll be back to my desktop. I added the -- 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

[Bug 49948] New: starfighter-2.3.3 black screen after alt-tabbing to window on second screen.
by WineHQ Bugzilla 06 Oct '20

06 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=49948 Bug ID: 49948 Summary: starfighter-2.3.3 black screen after alt-tabbing to window on second screen. Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- Created attachment 68338 --> https://bugs.winehq.org/attachment.cgi?id=68338 The console messages Summary: starfighter-2.3.3 black screen after alt-tabbing to window on second screen. Download location https://github.com/pr-starfighter/starfighter/releases/tag/v2.3.3 https://github.com/pr-starfighter/starfighter/releases/download/v2.3.3/star… sha256sum starfighter-2.3.3-win32.zip 67debd28241d6ea3c87ba0fc0db90d04dda5f74fc30c85925a50d9889f1533d6 starfighter-2.3.3-win32.zip Steps to reproduce 1) unzip the game $ unzip starfighter-2.3.3-win32.zip $ cd starfighter-2.3.3-win32 2) Run the game: $ wine starfighter.exe 3) Goto options - and set full screen on 4) Press alt-tab to a window on your second screen. Now the game window gets minimized. 5) Alt-tab back into the game. Now the screen is black. (but the music still plays.) 6) Press alt-tab. to a window on your second screen. Now the game window gets minimized. 7) Right click on the game window in the task bar, and choose "close window" Environment: I run LXDE with 2 monitors with this video card: $ lspci 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7) $ lsmod amdgpu 5861376 4 kvm_amd 114688 0 gpu_sched 40960 1 amdgpu i2c_algo_bit 16384 1 amdgpu Versions: $ wine --version wine-5.18 (Staging) $ pacman -Q wine wine-staging 5.18-1 uname -a Linux cedric-p4 5.8.13-arch1-1 #1 SMP PREEMPT Thu, 01 Oct 2020 20:40:35 +0000 x86_64 GNU/Linux -- 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