wine-bugs September 2023

wine-bugs@winehq.org

1 participants
2602 discussions

[Bug 54031] New: user32:msg - test_SendMessage_other_thread() broken by WM_WINDOWPOSCHANGING on Windows dual-monitor configs
by WineHQ Bugzilla 16 Sep '23

16 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54031 Bug ID: 54031 Summary: user32:msg - test_SendMessage_other_thread() broken by WM_WINDOWPOSCHANGING on Windows dual-monitor configs Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com user32:msg - test_SendMessage_other_thread() sometimes gets an unexpected WM_WINDOWPOSCHANGING message: msg.c:19053: Test failed: wrong status 00480048 msg.c:19091: Test failed: SendMessage from other thread 5: 0: the msg sequence is not complete: expected 0000 - actual 0046 msg.c:19091: Failed sequence SendMessage from other thread 5: msg.c:19091: 0: expected: nothing - actual: MsgCheckProc: 006F025C WM_WINDOWPOSCHANGING wp 00000000 lp 0022fc40 after 00000000 x 100 y 100 cx 200 cy 200 flags SWP_NOACTIVATE|SWP_NOZORDER (flags 19) msg.c:19091: 1: expected: nothing - actual: MsgCheckProc: 006F025C 0024 wp 00000000 lp 0022f700 (flags 39) msg.c:19059: Failed sequence SendMessage from other thread 1: msg.c:19059: 0: expected: msg 0402 - actual: MsgCheckProc: 007102CA 0402 wp 00000000 lp 00000000 (flags 19) msg.c:19059: 1: expected: msg 0400 - actual: MsgCheckProc: 007102CA 0400 wp 00000000 lp 00000000 (flags 19) msg.c:19079: Failed sequence SendMessage from other thread 3: msg.c:19079: 0: expected: msg 0403 - actual: MsgCheckProc: 007102CA 0403 wp 00000000 lp 00000000 (flags 19) msg.c:19079: 1: expected: msg 0401 - actual: MsgCheckProc: 007102CA 0401 wp 00000000 lp 00000000 (flags 19) [53435] msg.c:19087: Test failed: wrong status 00400040 msg.c:19091: Failed sequence SendMessage from other thread 5: msg.c:18487: Failed sequence SetFocus on a desktop window: msg.c:18497: Failed sequence SetFocus on another thread window: msg.c:18517: Failed sequence SetActiveWindow on a desktop window: msg.c:18527: Failed sequence SetActiveWindow on another thread window: msg.c:18592: Failed sequence SetFocus on a child window: msg.c:18592: 0: expected: hook 0009 - actual: CBT: hook 9 (HCBT_SETFOCUS) wp 005e0252 lp 002f0278 msg.c:12896: QS_RAWINPUT not supported on this platform msg.c:12921: Test failed: wrong qstatus 00000000 See https://test.winehq.org/data/patterns.html#user32:msg This seems to only happen on dual-monitor configurations, most frequently on w1064-2qxl but also regularly on w7u-2qxl. -- 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 55600] New: Connecting a GPU after X was started causes wine to break
by WineHQ Bugzilla 16 Sep '23

16 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55600 Bug ID: 55600 Summary: Connecting a GPU after X was started causes wine to break Product: Wine Version: 8.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: activeds Assignee: wine-bugs(a)winehq.org Reporter: mark(a)unserver.de Distribution: --- Hi I have a notebook with Intel GPU and an external Nvidia connected via Thunderbolt. Native software works always fine: vkcube, glmark2, glxgears, vkmark all good, on booth GPUs and their 32 bit versions all run fine as well. More complex stuff runs fine too. And wine also runs fine, as long as i connect the Egpu before i start X. But if i connect the eGPU after X was started, wine breaks. No matter what i run, even winecfg or Explorer.exe. The system starts to stutter (mouse moves fine, background processes seem to run fine too, but X hangs for a few seconds, then works for a brief moment, hangs again, ...) and no window ever appears. Wine reports: 0138:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. I can happily provide full logs, configs and the usual stuff, but as i do not know whats necessary i refrain from dumping a wall of text until i'm asked to do so. One thing i noted is that xrandr reports two providers when the Gpu was connected before X was started, and only when it was connected after. But keep in mind that everything works in both cases except wine. Another thing, as soon as the stutter begins i get kernel messages: [ 1413.308613] i915 0000:00:02.0: [drm] *ERROR* LSPCON init failed on port D [ 1414.701163] i915 0000:00:02.0: [drm] *ERROR* Failed to probe lspcon in time with the stutter and on each stutter. I can reproduce the problem even without an eGpu by just unbinding a Gpu and rebinding it after X is started: Unbind: echo "1" > /sys/bus/pci/devices/0000\:01\:00.0/remove Rebind: echo '\\_SB.PCI0.PEG0.PEGP._ON' > /proc/acpi/call; echo 1 > /sys/bus/pci/rescan I can always force wine onto the Intel GPU VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/intel_icd.i686.json" wine whatever.exe and then it works. But only on the intel Gpu, which kind of defeats the purpose of an eGpu :D -- 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 52571] New: batch token parsing regression
by WineHQ Bugzilla 16 Sep '23

16 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=52571 Bug ID: 52571 Summary: batch token parsing regression Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: dragonwarriorxtreme(a)gmail.com Distribution: --- This is easily demonstrated with vcvars script batch files in Visual Studio 2015, on amd64. >) >) >) >) >) >Can't recognize 'x86' as an internal or external command, or batch script. >Can't recognize '\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\x64\;C:\windows\system32;C:\win dows;C:\windows\system32\wbem;C:\windows\system32\WindowsPowershell\v1.0' as an internal or external command, or batch script. >Can't recognize 'x86' as an internal or external command, or batch script. >Can't recognize '\Windows Kits\NETFXSDK\4.6.1\include\um;' as an internal or external command, or bat ch script. >Can't recognize 'x86' as an internal or external command, or batch script. >Can't recognize '\Windows Kits\NETFXSDK\4.6.1\lib\um\x86;' as an internal or external command, or bat ch script. >Can't recognize 'x86' as an internal or external command, or batch script. >Can't recognize '\Microsoft Visual Studio 14.0\Team Tools\Performance Tools\x64;C:\Program Files ' as an internal or external command, or batch script. >Can't recognize 'x86' as an internal or external command, or batch script. ... etc ... 1. Install Visual Studio 2015 (latest Wine-git works around ncrypt limitations) or the v140/v141 build tools using 2017 (already works). What I did personally (was attempting to compile x86 programs on an x64 install before I hit this bug): 2. cd C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64_x86 3. wine cmd /K vcvarsamd64_x86.bat -- 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 55031] New: experimental wow64 mode: crashes in some 3d graphics code
by WineHQ Bugzilla 16 Sep '23

16 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55031 Bug ID: 55031 Summary: experimental wow64 mode: crashes in some 3d graphics code Product: Wine Version: 8.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: idarktemplar(a)mail.ru Distribution: --- Created attachment 74591 --> https://bugs.winehq.org/attachment.cgi?id=74591 wine.crash.log When I'm trying to run Spellforce 2 with experimental wow64 wine mode, it crashes. When I'm running it using normal multilib setup, everything runs fine, at least until main menu, didn't check again further. Same happens when I'm trying to run Torchlight 2 from Steam. Demo available on: https://store.steampowered.com/app/200710/Torchlight_II/ Crashing wine build options: ./configure --with-mingw --enable-archs='i386,x86_64' --prefix=/tmp/wineinstall Suspicious log lines just before crash: 0114:fixme:opengl:wow64_map_buffer GL_MAP_PERSISTENT_BIT not supported! wine: Unhandled page fault on write access to 5BFFF000 at address 6AB23144 (thread 0114), starting debugger... OS: Gentoo Linux amd64 (64bit) Graphics: X11 Videocard information: OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: Quadro K1000M/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 470.182.03 OpenGL core profile shading language version string: 4.60 NVIDIA OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile -- 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 55597] New: Second desktop slows running Planet of Lana
by WineHQ Bugzilla 16 Sep '23

16 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55597 Bug ID: 55597 Summary: Second desktop slows running Planet of Lana Product: Wine Version: 8.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stephematician(a)gmail.com Distribution: --- Created attachment 75129 --> https://bugs.winehq.org/attachment.cgi?id=75129 Short version of log from running program "Planet of Lana" A second monitor/desktop, plugged in to my laptop via HDMI, slows down considerably when running Planet of Lana. The laptop monitor/desktop and the game itself (windowed) appear to run at a normal speed. This issue is _not_ observed when running the Steam version of the game (using Proton 8.0.2). I am using UbuntuMATE 22.04 (X11/LightDM). I have an on-board and NVIDIA graphics controller, using the NVIDIA 535.86.05 driver. lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] (rev a1) 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev c5) Logs when running one vs two monitors do not appear materially different, e.g. # unplug second monitor wine Planet\ of\ Lana.exe 1&>2 2>one_monitor.log # plug second monitor in wine Planet\ of\ Lana.exe 1&>2 2>two_monitor.log # trim log sed -r '/semi-stub|stub!/d' one_monitor.log | sed 's/[0-9A-F]\{16\}/HEX/g' \ | sed 's/^[0-9a-fA-F]\{4\}:/HEX:/g' > one_monitor_trim.log sed -r '/semi-stub|stub!/d' two_monitor.log | sed 's/[0-9A-F]\{16\}/HEX/g' \ | sed 's/^[0-9a-fA-F]\{4\}:/HEX:/g' > two_monitor_trim.log diff one_monitor_trim.log two_monitor_trim.log # no difference Attached the (trimmed) one-monitor log for reference. -- 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 55546] New: wine 8.15 breaks with upgrading alsa-lib from 1.2.9 to 1.2.10
by WineHQ Bugzilla 16 Sep '23

16 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55546 Bug ID: 55546 Summary: wine 8.15 breaks with upgrading alsa-lib from 1.2.9 to 1.2.10 Product: Wine Version: 8.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: karabaja4(a)gmail.com Distribution: --- Upgrading these packages on Arch: * alsa-lib (1.2.9-1 -> 1.2.10-1) * lib32-alsa-lib (1.2.9-1 -> 1.2.10-1) breaks any Wine game with a sound when using pure ALSA (no pulseaudio, no pipewire). The game does not start, and this is the error message from wine output when trying to run the game: "Assertion failed: !status, file ../wine/dlls/mmdevapi/mmdevapi_private.h, line 69" Tested with games: * Project Diablo 2 * World Of Warcraft Vanilla 1.12. Using Wine 8.15. Regards, Igor -- 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 55539] New: user32:msg test_hvredraw fails in win1709 with unexpected region
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55539 Bug ID: 55539 Summary: user32:msg test_hvredraw fails in win1709 with unexpected region Product: Wine Version: 8.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- win1709_newtb-w1064v1709-64 now consistently fails in test_hvredraw with mismatched regions. This failure appears to have been introduced by https://gitlab.winehq.org/wine/wine/-/commit/fa038c3c3714cd1293e4de6aad44c1…, as it was the only change when this test started failing. There are 34 total failures that look somewhat like this: msg.c:9655: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos redraw #1 (0, 0, 50, 0): Update region shall match expected region msg.c:9655: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos redraw #2 (0, 0, 50, 50): Update region shall match expected region msg.c:9655: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos redraw #3 (0, 0, -50, -50): Update region shall match expected region msg.c:9655: Test failed: SimpleWindowClassWithHRedraw 00cf0000 SetWindowPos redraw #5 (-50, -50, 50, 0): Update region shall match expected region I did a test run with some traces, and it seems the actual update region always matches the window's visible area. It's not clear to me why running the test in a temporary desktop would cause this. -- 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 55533] New: setupapi:devinst - test_class_installer() fails on Windows 7+ and Wine
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55533 Bug ID: 55533 Summary: setupapi:devinst - test_class_installer() fails on Windows 7+ and Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com setupapi:devinst - test_class_installer() fails on Windows 7+ and Wine: devinst.c:2754: Test failed: Failed to call class installer, error 0xe000020e. devinst.c:2756: this is the last test seen before the exception 092c:devinst: unhandled exception c0000005 at 000000013F23C92E See https://test.winehq.org/data/patterns.html#setupapi:devinst This started on 2023-09-05 and happens on Windows 7+ and Wine. -- 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 55246] New: ntdll:om - The 64-bit test_object_types() crashes on Windows 8+
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=55246 Bug ID: 55246 Summary: ntdll:om - The 64-bit test_object_types() crashes on Windows 8+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:om - The 64-bit test_object_types() crashes on Windows 8+: om.c:2325: this is the last test seen before the exception 1c98:om: unhandled exception c0000005 at 00007FFFC32A60AB See https://test.winehq.org/data/patterns.html#ntdll:om Where c0000005 == STATUS_ACCESS_VIOLATION This started on 2023-07-10 which corresponds to the GitLab CI switch to Debian 12 for builds which means it is caused by the commit below: commit 5799e89f15b5584f186dcc2fd24b98e0a7bd6c10 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Jul 10 17:18:49 2023 +0200 gitlab: Upgrade the Debian image to bookworm. Note that, to this day, the 64-bit binaries produced by the TestBot still run successfully on Windows because they are built on Debian 11. But the nightly WineTest runs fail because they use the official WineTest binaries produced by the GitLab CI which uses Debian 12. -- 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 54331] New: Game "Antecrypt": Black screen after launch
by WineHQ Bugzilla 15 Sep '23

15 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54331 Bug ID: 54331 Summary: Game "Antecrypt": Black screen after launch Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stabilergriller(a)gmail.com Distribution: --- Created attachment 73894 --> https://bugs.winehq.org/attachment.cgi?id=73894 Output when running "wine beam.exe" This shooting game from https://punkcake.itch.io/antecrypt just opens up a window which is completely black. I confirm that this game runs on Windows 10. My set up: OS: Arch 64-Bit GPU: Intel HD Graphics 610 Mesa: 22.3.3 Kernel version: 6.1.5 -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs September 2023