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

[Bug 54407] user32:msg - test_SendMessage_other_thread() sometimes gets a bad WM_USER message sequence in Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54407 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase -- 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.

Jan. 30, 2023

[Bug 54407] New: user32:msg - test_SendMessage_other_thread() sometimes gets a bad WM_USER message sequence in Wine

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54407 Bug ID: 54407 Summary: user32:msg - test_SendMessage_other_thread() sometimes gets a bad WM_USER message sequence in Wine 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:msg - test_SendMessage_other_thread() sometimes gets a bad WM_USER message sequence in Wine: msg.c:19187: Test failed: SendMessage from other thread 1: 1: the msg 0x0400 was expected, but got msg 0x0403 instead msg.c:19187: Test failed: SendMessage from other thread 1: 2: the msg sequence is not complete: expected 0000 - actual 0400 msg.c:19201: Test failed: wrong status 00080000 msg.c:19207: Test failed: SendMessage from other thread 3: 0: the msg 0x0403 was expected, but got msg 0x0401 instead msg.c:19207: Test failed: SendMessage from other thread 3: 1: the msg sequence is not complete: expected 0401 - actual 0000 See https://test.winehq.org/data/patterns.html#user32:msg A somewhat similar issue has been happening for some time on Windows 7 (see bug 53434). This one started happening about twice per month in Wine on 2022-10-14 (debian11-win32). -- 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.

Jan. 30, 2023

[Bug 53435] user32:msg - test_SendMessage_other_thread() sometimes gets a wrong status on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53435 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|user32:msg - |user32:msg - |test_SendMessage_other_thre |test_SendMessage_other_thre |ad() sometimes fails on |ad() sometimes gets a wrong |Windows |status on Windows -- 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.

Jan. 30, 2023

[Bug 53229] dxgi:dxgi - test_swapchain_window_messages() sometimes gets an unexpected WM_DWMNCRENDERINGCHANGED message on Windows

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53229 --- Comment #1 from François Gouget <fgouget(a)codeweavers.com> --- user32:msg has also started receiving this message but in more recent versions of Windows. See bug 54406. -- 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.

Jan. 30, 2023

[Bug 54406] user32:msg - test_unicode_wm_char() sometimes gets an unexpected WM_DWMNCRENDERINGCHANGED message on Windows 10+

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54406 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source, testcase -- 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.

Jan. 30, 2023

[Bug 54406] New: user32:msg - test_unicode_wm_char() sometimes gets an unexpected WM_DWMNCRENDERINGCHANGED message on Windows 10+

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54406 Bug ID: 54406 Summary: user32:msg - test_unicode_wm_char() sometimes gets an unexpected WM_DWMNCRENDERINGCHANGED message on Windows 10+ 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_unicode_wm_char() sometimes gets an unexpected WM_DWMNCRENDERINGCHANGED message on Windows 10+: msg.c:16001: Test failed: unexpected message 31f msg.c:16002: Test failed: bad wparam 1 msg.c:16008: Test failed: unicode WM_CHAR: 0: the msg sequence is not complete: expected 0102 - actual 0000 msg.c:16008: Failed sequence unicode WM_CHAR: msg.c:16008: 0: expected: msg 0102 - actual: nothing See https://test.winehq.org/data/patterns.html#user32:msg Where: 031f == WM_DWMNCRENDERINGCHANGED The first instance happened on 2022-11-08 and there has only been about one instance per month since. This looks like some previous test did something that caused the non-client rendering policy to change but did not wait for this message to be sent and processed by all windows before continuing. So then which test gets impacted is up to timing. dxgi:dxgi has also been getting this message for a long time (see bug 53229). -- 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.

Jan. 30, 2023

[Bug 54405] FAVORITE games crash on New Game (Hoshizora no Memoria, Irotoridori no Sekai, AstralAir no Shiroki Towa, Sakura Moyu...)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54405 --- Comment #1 from Rafał Mużyło <galtgendo(a)o2.pl> --- Clarify: - are you running those games in the Japanese locale ? (going by your description, you likely should be) - sometimes besides Japanese locale Font/Replacement keys are necessary; sometimes it's bad enough that you need the actual font files (though this doesn't seem to be the later case) - which font is the game looking up ? - is there anything interesting in the standard debug output and/or 'font' debug channel ? -- 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.

Jan. 30, 2023

[Bug 54405] New: FAVORITE games crash on New Game (Hoshizora no Memoria, Irotoridori no Sekai, AstralAir no Shiroki Towa, Sakura Moyu...)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=54405 Bug ID: 54405 Summary: FAVORITE games crash on New Game (Hoshizora no Memoria, Irotoridori no Sekai, AstralAir no Shiroki Towa, Sakura Moyu...) Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: nekotekina(a)gmail.com Distribution: --- Hello, Multiple visual novels from FAVORITE crash at selecting New Game after startup. List of affected games (non-exhaustive, using the same engine): 星空のメモリア (Hoshizora no Memoria) -Wish upon a Shooting Star- 星空のメモリア (Hoshizora no Memoria) -Eternal Heart- いろとりどりのセカイ (Irotoridori no Sekai) いろとりどりのヒカリ (Irotoridori no Hikari) アストラエアの白き永遠 (AstralAir no Shiroki Towa) 紅い瞳に映るセカイ (Akai Hitomi ni Utsuru Sekai) アストラエアの白き永遠Finale-白き星の夢- (AstralAir no Shiroki Towa Finale -Shiroki Hoshi no Yume-) さくら、もゆ。(Sakura, Moyu.) -as the Night's, Reincarnation-) Workaround: Go to settings, switch to font settings tab, then go back to main menu. This is far from obvious, as it looks like the game doesn't work at all. Technical details: The game engine crashes calling __invalid_parameter_noinfo after failing to check results of certain call to GetGlyphOutlineA in its text rendering routine. More precisely, the engine seems bugged. First thing it does after starting New Game is trying to "render" Japanese space character U+3000. GetGlyphOutlineA returns zero for it, this triggers the code path calling GetLastError. Last error is sticky and there is no SetLastError anywhere before it. Since GetGlyphOutlineA doesn't set the last error in Wine (at least it's not the case here), GetLastError checks some "ancient" stuck value. The value is also strange: 0xffffffff, which isn't usually seen as an error code. I tried to figure out where 0xffffffff comes from. It's set in win32u:wait_message. X11DRV_MsgWaitForMultipleObjectsEx returns -1 because the count arg is 0, after process_events succeeds: ret is set to count-1. I don't understand where the bug actually is, it's pretty confusing. -- 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.

Jan. 29, 2023

[Bug 10570] Thief 2: The Metal Age - fog not working

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=10570 --- Comment #31 from Matheus <matheus.venturini(a)acad.ufsm.br> --- To see what the versions with broken fog look like with fogging enabled (and also some pretty amusing antics), see this video, which obviously was recorded on Windows: https://www.youtube.com/watch?v=IU8gMHDkH48 It takes place in early evening, but there's no fog. This is probably what the original poster must have been referring to when he filled this bug report, mistakenly thinking it was a Wine-only bug. -- 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.

Jan. 29, 2023

[Bug 10570] Thief 2: The Metal Age - fog not working

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=10570 --- Comment #30 from Matheus <matheus.venturini(a)acad.ufsm.br> --- In short, no, the bug that happens in Wine also happens in Windows. The full picture is what I said in my previous comment, but the bottom line is, from earliest to oldest release: Thief 2 demo: bug does NOT happen, fogging ON by default Thief 2 retail: bug DOES happen, fogging OFF by default Thief 2 Steam: bug DOES happen, fogging OFF by default Thief 2 NewDark engine: bug does NOT happen, fogging OFF by default Thief 2 GOG: bug does NOT happen, fogging OFF by default In all versions, if fogging is ON, it looks like the level takes place in early evening like comment 2 shows. If fogging is OFF, it looks like it takes place at night, like in comment 3. Comment 22 mentioned a demo that uses NewDark but I'm certain that was a misunderstanding, there isn't a demo version that uses it (NewDark is a fan-made modified version of DarkEngine, the original game's engine, which was only developed and released in 2013). -- 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.

Jan. 29, 2023