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

[Bug 48233] New: In a 64-bit app, GetSyscolor(COLOR_BTNSHADOW) returns a darker value than on windows
by WineHQ Bugzilla 09 Oct '20

09 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=48233 Bug ID: 48233 Summary: In a 64-bit app, GetSyscolor(COLOR_BTNSHADOW) returns a darker value than on windows Product: Wine Version: 3.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: ryampolsky(a)yahoo.com Distribution: --- Created attachment 65879 --> https://bugs.winehq.org/attachment.cgi?id=65879 Screenshot, showing shadow drawn with GetSysColor(COLOR_BTNSHADOW) I recently converted my 32-bit app to 64-bits, and when I run either the 32-bit version or the 64-bit version under a wine64 WINEPREFIX, the only difference I notice is the value returned by GetSyscolor(COLOR_BTNSHADOW). On Windows in both the WIN32 and WIN64 versions of my app, it returns 0xa0a0a0, but on WINE64, it returns 0x4c4c4c. On WINE, I'm using the Ubuntu Light theme. With that theme in effect, on WINE32, GetSysColor(COLOR_BTNSHADOW) returns 0xa5a9ad. But on WINE64, both the WIN32 and WIN64 versions get 0x4c4c4c. So the shadow looks too dark. Again, the WIN32 exe gets the right color under WINE32, but the same wrong color as the WIN64 exe under WINE64 - which is why I think it's a WINE64 bug and not my app. Everything else seems to look the same between WINE32 and WINE64. The attached screenshot shows the About dialog from my app. There's a 3D frame around the logo at the top - BTNSHADOW on top and left, BTNHIGHLIGHT on bottom and right. The text below it shows that this is the X64 version of the app, and prints out the value returned by GetSysColor(COLOR_BTNSHADOW). -- 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 7

[Bug 43947] New: Disk size in Wine is not correct
by wine-bugs＠winehq.org 08 Oct '20

08 Oct '20

https://bugs.winehq.org/show_bug.cgi?id=43947 Bug ID: 43947 Summary: Disk size in Wine is not correct Product: Wine Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: christoph.heilmann(a)gmx.de Distribution: --- Created attachment 59586 --> https://bugs.winehq.org/attachment.cgi?id=59586 disk size windows Dual Xeon E5-2630v4 (!!) Ubuntu 17.04 Server Kernel 4.10.0-37 Wine 2.0.3 WINEARCH=win64 WINEPREFIX=/home/christoph/.wine64 christoph@:/$ df -h Filesystem Size Used Avail Use% Mounted on udev 126G 0 126G 0% /dev tmpfs 26G 11M 26G 1% /run /dev/sda2 450G 166G 262G 39% / tmpfs 126G 0 126G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 126G 0 126G 0% /sys/fs/cgroup /dev/sda1 226M 58M 153M 28% /boot The disk size in Wine is not correct (see attachment). -- 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 17

[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 #28 from Rémi Bernon <rbernon(a)codeweavers.com> --- Created attachment 68359 --> https://bugs.winehq.org/attachment.cgi?id=68359 Rebased user32-rawinput-mouse-experimental 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 --- Comment #27 from Rémi Bernon <rbernon(a)codeweavers.com> --- Created attachment 68358 --> https://bugs.winehq.org/attachment.cgi?id=68358 Rebased user32-rawinput-mouse 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 --- 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