June 2023 - Wine-Bugs - list.winehq.org

[Bug 55120] New: kernel32:debugger - test_debug_loop_wow64() gets wrong ntdll count in the new WoW mode
by WineHQ Bugzilla July 7, 2023

July 7, 2023

https://bugs.winehq.org/show_bug.cgi?id=55120 Bug ID: 55120 Summary: kernel32:debugger - test_debug_loop_wow64() gets wrong ntdll count in the new WoW mode Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:debugger - test_debug_loop_wow64() gets wrong ntdll count in the new WoW mode: debugger.c:1231: Test failed: Expecting two ntdll instances See https://test.winehq.org/data/patterns.html#kernel32:debugger These failures started on 2023-06-21 and are specific to the 64-bit tests running in the new WoW mode. A bisect shows that this failure started with the commit below: commit 2ef4cc48fbce406d67be32a90a2208868026a505 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Jun 21 12:08:00 2023 +0200 wow64: Map a copy of ntdll to build the syscall table. The original ntdll may have been hooked. -- 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 55110] New: quartz:vmr7 & quartz:vmr9 sometimes exit prematurely in Wine
by WineHQ Bugzilla July 7, 2023

July 7, 2023

https://bugs.winehq.org/show_bug.cgi?id=55110 Bug ID: 55110 Summary: quartz:vmr7 & quartz:vmr9 sometimes exit prematurely in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- quartz:vmr7 & quartz:vmr9 sometimes exit prematurely in Wine: vmr7.c:2393: Test marked todo: Got hr 0. vmr7.c:2424: Test marked todo: Got hr 0x8004020a. quartz:vmr7:0890 done (0) in 4s 2250B Notice the missing ' xxx tests executed' line. And also in the Wine traces: 01e4:fixme:d3d:wined3d_guess_card No card selector available for card vendor 0000 (using GL_RENDERER "llvmpipe (LLVM 11.0.1, 256 bits)"). X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 7 (X_ReparentWindow) Resource id in failed request: 0x140019d Serial number of failed request: 2252 Current serial number in output stream: 2253 See https://test.winehq.org/data/patterns.html#quartz:vmr7 https://test.winehq.org/data/patterns.html#quartz:vmr9 So it is most likely the X error that causes the test to be prematurely killed. I did not notice an X error for quartz:vmr9 but for now I will consider that it either has the same cause or is a consequence of the vmr7 failure. The first failure happened on 2023-06-13 and, across all test configurations, it has been happening about once a day since. Further, a bisect shows that the vmr7 failure started with the commit below: commit 9f8d9eef216d4ede3b53d3caab222ad8f896f10b Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Jan 25 15:22:08 2021 +0100 winex11: Set the window cursor immediately in SetCursor. Instead of synchronizing the cursor on mouse changes. The SetCursor call should now only be made when cursor or window handle have changed. -- 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 34040] New: QuickBooks SS 2008 R1 crashes multiple times on second run
by wine-bugs＠winehq.org July 6, 2023

July 6, 2023

http://bugs.winehq.org/show_bug.cgi?id=34040 Bug #: 34040 Summary: QuickBooks SS 2008 R1 crashes multiple times on second run Product: Wine Version: 1.6-rc5 Platform: x86-64 URL: http://dlm.download.intuit.com/SBD/QuickBooks/2008/R1/ QuickBooksSimpleStartDirect2008.exe OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Classification: Unclassified Created attachment 45237 --> http://bugs.winehq.org/attachment.cgi?id=45237 wine-1.6-rc5 console output Running QB 2008 a second time after setting up a company file and closing the application will cause multiple crashes that are caught by the application itself. To get this far: 1. winetricks -q dotnet20 msxml4 (Bug 34028 and Bug 34029) 2. Install. 3. Run and set up a company file and save it. 4. Exit application. 5. Run application. Tried msxml3 but this simply causes the application to hang. NOTE: Native msxml3 cannot be installed before the first run as this appears to also cause Bug 34028. Tried vcrun2005 too but it made no difference. -- 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 5

[Bug 34028] New: QuickBooks SS 2008 R1 fails to load due to licence error
by wine-bugs＠winehq.org July 6, 2023

July 6, 2023

http://bugs.winehq.org/show_bug.cgi?id=34028 Bug #: 34028 Summary: QuickBooks SS 2008 R1 fails to load due to licence error Product: Wine Version: 1.6-rc5 Platform: x86-64 URL: http://download.microsoft.com/download/C/C/0/CC0BD555- 33DD-411E-936B-73AC6F95AE11/IE8-WindowsXP-x86-ENU.exe OS/Version: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: msxml4 AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Classification: Unclassified Created attachment 45219 --> http://bugs.winehq.org/attachment.cgi?id=45219 wine-1.6-rc5 console output QuickBooks SS 2008 R1 fails to load due to a "Could not initialize license properties" error. fixme:msxml:domdoc_setProperty Ignoring property L"NewParser", value {VT_I2: -1} fixme:msxml:domdoc_setProperty Ignoring property L"NewParser", value {VT_BOOL: ffffffff} [...] fixme:msxml:domdoc_get_parseError (0x1aa674)->(0x32f2dc): creating a dummy parseError Workaround is "winetricks msxml4". -- 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 9

[Bug 55153] New: comdlg32:filedlg sometimes crashes on Windows 7
by WineHQ Bugzilla July 5, 2023

July 5, 2023

https://bugs.winehq.org/show_bug.cgi?id=55153 Bug ID: 55153 Summary: comdlg32:filedlg sometimes crashes on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comdlg32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comdlg32:filedlg sometimes crashes on Windows 7: comdlg32:filedlg start dlls/comdlg32/tests/filedlg.c 0ef8:filedlg: unhandled exception c0000005 at 766523AD comdlg32:filedlg:0ef8 done (-1073741819) in 5s 56B See https://test.winehq.org/data/patterns.html#comdlg32:filedlg Where c0000005 == STATUS_ACCESS_VIOLATION The first crash happened on 2023-02-28 and there has been a bit over 1.5 per month since. -- 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 54135] New: JGlossator v5.0: Hovering textboxes not displaying
by WineHQ Bugzilla July 5, 2023

July 5, 2023

https://bugs.winehq.org/show_bug.cgi?id=54135 Bug ID: 54135 Summary: JGlossator v5.0: Hovering textboxes not displaying Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mshtml Assignee: wine-bugs(a)winehq.org Reporter: metcalsr(a)gmail.com Distribution: --- Created attachment 73666 --> https://bugs.winehq.org/attachment.cgi?id=73666 +mshtml Application features hover-over translations for text in the search box. This is not only an important QoL feature, but often provides alternative translations which aid significantly in understanding the text. These hovering boxes break under 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 11

[Bug 55024] New: Sims 4 Studio window flickering
by WineHQ Bugzilla July 5, 2023

July 5, 2023

https://bugs.winehq.org/show_bug.cgi?id=55024 Bug ID: 55024 Summary: Sims 4 Studio window flickering Product: Wine Version: 8.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ryu.ketsueki(a)outlook.com Distribution: --- This is something that was happening before for a while now but it was tolerable. Now it's unusable. Sims 4 Studio updated to the (Star) release, as in the 3.2.0.6 and it's actually usable now. The application doesn't freeze when trying to render anything 3D, which was apparently an issue on Sims 4 Studio itself, as even in a virtual machine, it had the exact same error. Could only get around it by a dual boot with Windows. Not anymore. Sims 4 Studio runs relatively well and I can create and modify game packages normally. That was until recently, when the flickering got so much worse. I'll explain what is happening. The window would hang frames for a bit and flicker them instead of completely update to the newest frame. Now it doesn't hang anymore. Instead, the window appears completely black, except when hovering over buttons or menus, when the window flash its content for a split second and goes black again. This is still on top of the flickering of before, so it still hangs frames but still goes black constantly, making the application unusable. Now, to my knowledge, Sims 4 Studio requires .NET 6.0 to launch at all. I had to install it to make it work, even when it was usable. Maybe this is related Mono or .NET itself, I don't know. I did observe a behavior that may be connected to what is going on. When the window is flashing black, the center of the window has a square showing the correct content but it's following the Windows 10/11 spinning wheel, so only this loading wheel shows correctly. The behavior persists even when the wheel is gone -- 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 47067] New: Font is too wide in RPGMaker game Hello Charlotte
by wine-bugs＠winehq.org July 4, 2023

July 4, 2023

https://bugs.winehq.org/show_bug.cgi?id=47067 Bug ID: 47067 Summary: Font is too wide in RPGMaker game Hello Charlotte Product: Wine Version: 4.6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 64246 --> https://bugs.winehq.org/attachment.cgi?id=64246 Screenshot on Wine The font in the game is too wide, meaning long lines are cut off. Already tried winetricks allfonts, which doesn't help. To reproduce, just download the game, run Game.exe and click Start in the mainmenu. -- 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 53230] New: user32:win - test_activateapp() fails randomly with fvwm
by WineHQ Bugzilla July 4, 2023

July 4, 2023

https://bugs.winehq.org/show_bug.cgi?id=53230 Bug ID: 53230 Summary: user32:win - test_activateapp() fails randomly with fvwm Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:win - test_activateapp() fails randomly with fvwm. The failures themselves change quite a bit from one run to the next, depending on where in the function the failures start. It looks a bit like a race condition between the test and the window manager. Here is a relatively complete set: win.c:10976: Test failed: Expected foreground window 0, got 01DE007C win.c:10982: Test failed: Expected foreground window 001A013C, got 01DE007C win.c:10992: Test failed: Expected foreground window 001A013C, got 00000000 win.c:10999: Test failed: Expected foreground window 001A013C, got 01DE007C win.c:11001: Test failed: GetActiveWindow() = 00000000 win.c:11001: Test failed: GetFocus() = 00000000 win.c:11003: Test failed: Received WM_ACTIVATEAPP(0), did not expect it. win.c:11011: Test failed: Expected foreground window 001A013C, got 00000000 win.c:11013: Test failed: GetActiveWindow() = 00000000 win.c:11013: Test failed: GetFocus() = 00000000 win.c:11021: Test failed: Received WM_ACTIVATEAPP(1), did not expect it. https://test.winehq.org/data/patterns.html#user32:win The failures don't seem to depend on the locale or bitness. However they only happen in the TestBot VMs which happen to run fvwm (with a specially curated configuration file) and don't happen on my box which runs KDE for instance. -- 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 49229] New: Regression Requiem: Rise of the Reaver mouse issue since Release v5.0-rc3
by WineHQ Bugzilla July 3, 2023

July 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=49229 Bug ID: 49229 Summary: Regression Requiem: Rise of the Reaver mouse issue since Release v5.0-rc3 Product: Wine-staging Version: 5.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ergoschnuffel(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- radeon/amdgpu (same behaviour) X11 on openbox Game: Requiem: Rise of the Reaver (http://www.playrequiem.com/) Use case: windowed multi client (transfer of items, shop open in the background etc.) issues: - need to click once to activate the game window and then it operates normally, before it was a direct click through (activate game window and action in the game) - mouse cursor gets trapped in game window A while moving the mouse to game window B and activating game window B (game window A/B overlapping a bit since monitor resolution). My issues started between Release v5.0-rc2 and Release v5.0-rc3 (update of the raw input patches?) and are still on going. -- 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