August 2023 - wine-bugs

[Bug 55373] New: Running native application inside a windows one, shows a terminal
by WineHQ Bugzilla 21 Aug '23

21 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55373 Bug ID: 55373 Summary: Running native application inside a windows one, shows a terminal Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: cagnulein(a)gmail.com Distribution: --- Since Wine4 i'm using this https://wiki.winehq.org/FAQ#How_do_I_launch_native_applications_from_a_Wind… to run my native application inside a Windows applications. Starting from Wine 8, every time I run a native application from a Windows one, a terminal window popups. How can I prevent this returning to the default behaviour? Thanks -- 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 54784] New: mIRC 7.72 crashes after restoring from application tray
by WineHQ Bugzilla 21 Aug '23

21 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54784 Bug ID: 54784 Summary: mIRC 7.72 crashes after restoring from application tray Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dragone2(a)risposteinformatiche.it Distribution: --- Created attachment 74279 --> https://bugs.winehq.org/attachment.cgi?id=74279 Unhandled exception: page fault on read access - mIRC - Wine-staging 8.5 mIRC was running for about 4-5 hours before the crash. It was reduced on the tray and its icon was blinking to notify that there were new messages / activities in channels or private messages. I clicked on it to restore the window and see the messages and wine gave me this backtrace (see the attachment). I was forced to quit mIRC and restart it again. This rarely happens, so it's not a real problem for me, but I don't know if it could help you fix this. Other infos: - Executable path: D:\mIRC\mirc.exe - mIRC Version: 7.72 (the latest one). - mIRC running in portable mode from a specific drive (on Wine, D:\) formatted in NTFS. - mIRC was running using some custom scripts. But this crash never happen on Windows. - Distro: Linux Mint 21.1 with latest updates. - Kernel: 5.15.0-69-generic - Wine infos: Wine build: wine-8.5 (Staging) Platform: i386 (WOW64) Version: Windows 10 - Drive Z: is a drive formatted in BTRFS. - CPU: Intel Core i7-6700 - RAM: 32 GB, when the crash occurred I was using less than 8 GB. -- 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

[Bug 52676] New: enigma protected software fails to work properly
by WineHQ Bugzilla 21 Aug '23

21 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=52676 Bug ID: 52676 Summary: enigma protected software fails to work properly Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl CC: dark.shadow4(a)web.de Distribution: --- Created attachment 72003 --> https://bugs.winehq.org/attachment.cgi?id=72003 backtrace of the crash (note the garbage) As I've said in bug 49052, the trial that's supposed to work just crashes without displaying anything. Attaching console output. I've got one other trial that's also enigma protected - that one starts, but enters an infinite loop without displaying anything. That one is using an engine that's known to work here, so I suspect enigma being the reason of the failure. -- 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 25

[Bug 4045] Wine is not reading the DPI setting from X - and is defaulting it to a dumb value
by WineHQ Bugzilla 21 Aug '23

21 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=4045 Bloody Iron <bloodyiron(a)lanified.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bloodyiron(a)lanified.com --- Comment #22 from Bloody Iron <bloodyiron(a)lanified.com> --- DPI issues are persisting, and this also is present in Wayland. Latest example for me is Ubuntu 22.04 on a Microsoft Surface Pro 9, which runs a display of 2880x1920 (3:2) and I believe it was a regular DPI of 271, up from the normal 96. But in testing 192 seems to be a good number-ish. In my case installing Mono the install dialogue is so small it's next to impossible to read. -- 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 54450] New: SINE Player fails to load "My Licenses" tab
by WineHQ Bugzilla 20 Aug '23

20 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54450 Bug ID: 54450 Summary: SINE Player fails to load "My Licenses" tab Product: Wine Version: 8.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jonathan(a)luxaritas.com Distribution: --- Created attachment 74001 --> https://bugs.winehq.org/attachment.cgi?id=74001 Wine output from application start through license tab load Download link: https://orchtools-sine.s3.us-west-1.amazonaws.com/SINE_Player_1.1.2.519.exe (via https://www.orchestraltools.com/store/get-sine), sha1 9f698ada2162aa13d8e5f52d1a072464c87fd17d After installing and signing in with an Orchestral Tools account (free), the "My Licenses" tab is loaded. However, the tab contents remains blank. This prevents downloading application content necessary to use the application. It appears this page is implemented via an MS Edge based embedded browser/webview, which seems to be relevant here - all pages that appear to be web views fail similarly, but other pages work fine. -- 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 55445] New: Crash when launching Undertale, DF Connected, or other Gamemaker Games
by WineHQ Bugzilla 20 Aug '23

20 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55445 Bug ID: 55445 Summary: Crash when launching Undertale, DF Connected, or other Gamemaker Games Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ultimateperson66(a)gmail.com Distribution: --- Created attachment 75006 --> https://bugs.winehq.org/attachment.cgi?id=75006 Error i got when opening Don't Forget:Connected Recently, i decided to Switch to Linux (Ubuntu MATE specifically) for reasons i will not get into. Many Windows applications i regularly used were compatible with the latest Stable build of Wine, except for two PC games i play, Undertale, and a fan-game based off of it called Don't Forget: Connected. Since both games are made in Game-maker, i figured that it may be because of something i'm missing to make the engine work Correctly. I read a forum saying that this issue was not Present in an older version of Wine, but i don't know how to Downgrade my Wine version. My hope for this situation is that anyone can offer me guidance to Downgrade wine to a version that can run these games, or if someone can work on fixing this. Attached is my log that i got from my last attempt running Don't Forget Connected. This is my first post, so if there's any more information i need to give out, please let me know, as long as it helps the situation. -- 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 55468] New: XB36Hazard's save editors stay frozen when opening with wine and proton.
by WineHQ Bugzilla 20 Aug '23

20 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55468 Bug ID: 55468 Summary: XB36Hazard's save editors stay frozen when opening with wine and proton. Product: Wine Version: 8.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mg23811(a)gmail.com Distribution: --- Just like the summary says when opening the save editors they will freeze after a few seconds, his launcher however works fine but even if you get one of his save editors exe without the launcher same problem so the launcher its self isn't the problem. I've tried the latest version of wine and tried various protons. Here's a link to his site for his save editors: https://x3t-infinity.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 55466] New: Menu items with MF_POPUP & MF_OWNERDRAW forget to re-draw item text after popup
by WineHQ Bugzilla 20 Aug '23

20 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55466 Bug ID: 55466 Summary: Menu items with MF_POPUP & MF_OWNERDRAW forget to re-draw item text after popup Product: Wine Version: 8.14 Hardware: x86-64 URL: https://web.archive.org/web/20230819235112/https://lts pice.analog.com/software/LTspice64.msi OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: telans(a)posteo.de Distribution: --- Created attachment 75022 --> https://bugs.winehq.org/attachment.cgi?id=75022 Wine Log In LTspice 17.1.10, a popup menu item once moused over fails to draw the initial menu item text. Instead, it is missing. As far as I can tell this isn't a regression, I've tested all the way down to wine-5.0. I believe this happens only with MF_OWNERDRAW & MF_POPUP. After some debugging, this is probably due to TextColor not being restored after drawing, or the window fails to invalidate the menu item rect(?). See screenshots of Windows vs Wine behavior. I've also attached the log for when this happens. Look for "Efficiency Calculation". I've attached the stack trace where the text disappears. This is not the same bug as #52839 which corresponds to the top menu bar entries, which I believe has been fixed. -- 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 55460] New: itss:protocol - test_its_protocol_info() sometimes fails on w7u
by WineHQ Bugzilla 19 Aug '23

19 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55460 Bug ID: 55460 Summary: itss:protocol - test_its_protocol_info() sometimes fails on w7u Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com itss:protocol - test_its_protocol_info() sometimes fails on w7u: protocol.c:484: Test failed: [11] unexpected size=31 protocol.c:487: Test failed: [11] unexpected result: L":test.chm::blank.htmltest.html" See https://test.winehq.org/data/patterns.html#itss:protocol The failures first happened on 2023-07-13 and have happened about once a week since. They also seem to be specific to the w7u VM, in particular they did not happen on w7pro64 yet. -- 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 55451] New: Application gets WM_IME_COMPOSITION without getting WM_IME_STARTCOMPOSITION before
by WineHQ Bugzilla 19 Aug '23

19 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55451 Bug ID: 55451 Summary: Application gets WM_IME_COMPOSITION without getting WM_IME_STARTCOMPOSITION before Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hagb(a)hagb.name Distribution: --- Created attachment 75009 --> https://bugs.winehq.org/attachment.cgi?id=75009 This program can reproduce the problem On wine 8.8 there isn't such a problem. On wine >=8.9 <=8.13, when the user uses input method to input something, the program gets some WM_IME_SETCONTEXT (0x281) messages first, and then gets WM_IME_NOTIFY (0x282, with IMN_WINE_SET_COMP_STRING 0x10), and then gets WM_IME_COMPOSITION (0x10f). There isn't a WM_IME_STARTCOMPOSITION (0x10d) sent before WM_IME_COMPOSITION. And after WM_IME_COMPOSITION, there isn't WM_IME_ENDCOMPOSITION (0x10e) either. -- 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 55465] New: user32:msg - The 64-bit test_swp_paint_region_on_show() sometimes gets a COMPLEXREGION on Windows 7
by WineHQ Bugzilla 19 Aug '23

19 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55465 Bug ID: 55465 Summary: user32:msg - The 64-bit test_swp_paint_region_on_show() sometimes gets a COMPLEXREGION on Windows 7 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 - The 64-bit test_swp_paint_region_on_show() sometimes gets a COMPLEXREGION on Windows 7: msg.c:9471: Test failed: GetRgnBox (on parent) returned 3 5 rects: (10,10)-(100,33) (10,33)-(59,34) (10,34)-(57,35) (10,35)-(56,37) (10,37)-(55,100) msg.c:9508: Test failed: GetRgnBox (on parent) returned 3 5 rects: (20,20)-(120,33) (20,33)-(59,34) (20,34)-(57,35) (20,35)-(56,37) (20,37)-(55,120) msg.c:9565: Test failed: GetRgnBox (on parent) returned 3 5 rects: (10,10)-(100,33) (10,33)-(59,34) (10,34)-(57,35) (10,35)-(56,37) (10,37)-(55,100) See https://test.winehq.org/data/patterns.html#user32:msg Where 3 == COMPLEXREGION This is similar to bug 55374 except: * This only happens in 64-bit tests instead of happening exclusively in 32-bit tests. * So this also only happens on w7pro64 instead of w7u. * test_swp_paint_region_on_show() gets a COMPLEXREGION instead of a NULLREGION. So it's not immediately clear to me if both failure types have the same root cause. The oldest known instance happened on 2023-06-12 and this has happened about once a month since: * 2023-06-12 win7_newtb-w7pro64-64 * 2023-07-14 win7_newtb-w7pro64-64 * 2023-08-17 win7_newtb-w7pro64-64 -- 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 1

[Bug 55464] New: user32:msg - test_EndDialog() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows 8
by WineHQ Bugzilla 19 Aug '23

19 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55464 Bug ID: 55464 Summary: user32:msg - test_EndDialog() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows 8 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_EndDialog() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows 8: msg.c:15510: Test failed: EndDialog2: 9: the msg 0x0009 was expected, but got msg 0x0047 instead msg.c:15510: Test failed: EndDialog2: 10: the msg 0x0008 was expected, but got msg 0x0009 instead msg.c:15510: Test failed: EndDialog2: 11: the msg 0x8005 was expected, but got msg 0x0008 instead msg.c:15510: Test failed: EndDialog2: 12: the msg 0x0007 was expected, but got msg 0x8005 instead msg.c:15510: Test failed: EndDialog2: 13: the msg sequence is not complete: expected 0000 - actual 0007 msg.c:15510: Failed sequence EndDialog2: msg.c:15510: 0: expected: winevent 800a - actual: WEH: winevent 00E001DA 0000800a 00000000 00000000 msg.c:15510: 1: expected: msg 000a - actual: parent: 00E001DA 000a wp 00000001 lp 00000000 (flags 1d) msg.c:15510: 2: expected: msg 0046 - actual: dialog: 002C01EA WM_WINDOWPOSCHANGING wp 00000000 lp 00ccf870 after 00000000 x 0 y 0 cx 0 cy 0 flags SWP_HIDEWINDOW|SWP_NOACTIVATE|SWP_NOZORDER|SWP_NOSIZE|SWP_NOMOVE (flags 19) msg.c:15510: 3: expected: hook 0005 - actual: CBT: hook 5 (HCBT_ACTIVATE) wp 00e001da lp 00ccf89c msg.c:15510: 4: expected: msg 0086 - actual: dialog: 002C01EA 0086 wp 00000000 lp 00e001da (flags 19) msg.c:15510: 5: expected: msg 0006 - actual: dialog: 002C01EA 0006 wp 00000000 lp 00e001da (flags 19) msg.c:15510: 6: expected: winevent 0003 - actual: WEH: winevent 00E001DA 00000003 00000000 00000000 msg.c:15510: 7: expected: msg 0046 - actual: dialog: 002C01EA WM_WINDOWPOSCHANGING wp 00000000 lp 00ccf888 after 0001008A x 0 y 0 cx 0 cy 0 flags SWP_NOACTIVATE|SWP_NOSIZE|SWP_NOMOVE (flags 19) msg.c:15510: 8: expected: msg 0046 - actual: dialog: 002C01EA WM_WINDOWPOSCHANGED wp 00000000 lp 00ccf888 after 0001008A x 108 y 131 cx 156 cy 192 flags SWP_NOACTIVATE|SWP_NOREDRAW|SWP_NOSIZE|SWP_NOMOVE|SWP_NOCLIENTSIZE|SWP_NOCLIENTMOVE (flags 19) msg.c:15510: 9: expected: hook 0009 - actual: dialog: 002C01EA WM_WINDOWPOSCHANGED wp 00000000 lp 00ccf888 after 0001008A x 108 y 131 cx 156 cy 192 flags SWP_NOACTIVATE|SWP_NOREDRAW|SWP_NOSIZE|SWP_NOMOVE|SWP_NOCLIENTSIZE|SWP_NOCLIENTMOVE (flags 19) msg.c:15510: 10: expected: msg 0008 - actual: CBT: hook 9 (HCBT_SETFOCUS) wp 00e001da lp 002c01ea msg.c:15510: 11: expected: winevent 8005 - actual: dialog: 002C01EA 0008 wp 00e001da lp 00000000 (flags 19) msg.c:15510: 12: expected: msg 0007 - actual: WEH: winevent 00E001DA 00008005 fffffffc 00000000 msg.c:15510: 13: expected: nothing - actual: parent: 00E001DA 0007 wp 002c01ea lp 00000000 (flags 3d) See https://test.winehq.org/data/patterns.html#user32:msg This only happened twice so far and both times on Windows 8: * 2023-08-08 win81_newtb-w8 * 2023-08-18 win81_newtb-w8adm -- 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 1

[Bug 55463] New: user32:msg - test_SetFocus() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows
by WineHQ Bugzilla 19 Aug '23

19 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55463 Bug ID: 55463 Summary: user32:msg - test_SetFocus() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows 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_SetFocus() sometimes gets an unexpected WM_WINDOWPOSCHANGED on Windows: msg.c:18822: Test failed: SetFocus on a child window: 5: the msg 0x001c was expected, but got msg 0x0047 instead msg.c:18822: Failed sequence SetFocus on a child window: msg.c:18822: 0: expected: hook 0009 - actual: CBT: hook 9 (HCBT_SETFOCUS) wp 008f00e0 lp 00000000 msg.c:18822: 1: expected: hook 0005 - actual: CBT: hook 5 (HCBT_ACTIVATE) wp 008d00c4 lp 0034f5f8 msg.c:18822: 2: expected: winevent 0003 - actual: WEH: winevent 00000000008D00C4 00000003 00000000 00000000 msg.c:18822: 3: expected: msg 030f - actual: parent: 00000000008D00C4 WM_WINDOWPOSCHANGING wp 00000000 lp 0034f5e0 after 0000000000C600FA x 0 y 0 cx 0 cy 0 flags SWP_NOSIZE|SWP_NOMOVE (flags 1d) msg.c:18822: 4: expected: msg 0046 - actual: parent: 00000000008D00C4 WM_WINDOWPOSCHANGING wp 00000000 lp 0034f5e0 after 0000000000C600FA x 0 y 0 cx 0 cy 0 flags SWP_NOSIZE|SWP_NOMOVE (flags 1d) msg.c:18822: 5: expected: msg 001c - actual: parent: 00000000008D00C4 WM_WINDOWPOSCHANGED wp 00000000 lp 0034f5e0 after 0000000000C600FA x 0 y 0 cx 132 cy 38 flags SWP_NOREDRAW|SWP_NOSIZE|SWP_NOMOVE|SWP_NOCLIENTSIZE|SWP_NOCLIENTMOVE (flags 1d) msg.c:18822: 6: expected: msg 0086 - actual: parent: 00000000008D00C4 000d wp 00000208 lp 0034e6f0 (flags 1d) msg.c:18822: 7: expected: msg 000d - actual: parent: 00000000008D00C4 WM_NCCALCSIZE: winpos->cx 132, winpos->cy 38 (flags 1d) msg.c:18822: 8: expected: msg 000d - actual: parent: 00000000008D00C4 WM_NCCALCSIZE: winpos->cx 132, winpos->cy 38 (flags 1d) msg.c:18822: 9: expected: msg 0006 - actual: parent: 00000000008D00C4 WM_NCCALCSIZE: winpos->cx 132, winpos->cy 38 (flags 1d) msg.c:18822: 10: expected: hook 0009 - actual: WEH: winevent 00000000008D00C4 0000800b 00000000 00000000 msg.c:18822: 11: expected: winevent 8005 - actual: parent: 00000000008D00C4 001c wp 00000001 lp 00000220 (flags 1d) msg.c:18822: 12: expected: msg 0007 - actual: parent: 00000000008D00C4 0086 wp 00000001 lp 00000000 (flags 1d) msg.c:18822: 13: expected: msg 0008 - actual: parent: 00000000008D00C4 000d wp 00000208 lp 0034e330 (flags 3d) msg.c:18822: 14: expected: winevent 8005 - actual: parent: 00000000008D00C4 000d wp 00000208 lp 0034e380 (flags 3d) msg.c:18822: 15: expected: msg 0007 - actual: parent: 00000000008D00C4 0006 wp 00000001 lp 00000000 (flags 1d) msg.c:18822: 16: expected: nothing - actual: CBT: hook 9 (HCBT_SETFOCUS) wp 008d00c4 lp 00000000 msg.c:18822: 17: expected: nothing - actual: WEH: winevent 00000000008D00C4 00008005 fffffffffffffffc 00000000 msg.c:18822: 18: expected: nothing - actual: parent: 00000000008D00C4 0007 wp 00000000 lp 00000000 (flags 3d) msg.c:18822: 19: expected: nothing - actual: parent: 00000000008D00C4 0008 wp 008f00e0 lp 00000000 (flags 1d) msg.c:18822: 20: expected: nothing - actual: WEH: winevent 00000000008F00E0 00008005 fffffffffffffffc 00000000 msg.c:18822: 21: expected: nothing - actual: MsgCheckProc: 00000000008F00E0 0007 wp 008d00c4 lp 00000000 (flags 19) See https://test.winehq.org/data/patterns.html#user32:msg Where 0x001c == WM_ACTIVATEAPP 0x0047 == WM_WINDOWPOSCHANGED The first known instance happened on 2023-06-12 and this has happened about once every other week since: * 2023-06-12 win7_newtb-w7u-pt-PT * 2023-06-14 win21H1_newtb-w10pro64-zh-CN-64 * 2023-07-06 win7_newtb-w7pro64-64 * 2023-07-13 win7_newtb-w7pro64-64_1 * 2023-08-10 win7_newtb-w7pro64-64 -- 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 1

[Bug 55462] New: mfplay:mfplay sometimes times out on Windows 7
by WineHQ Bugzilla 19 Aug '23

19 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55462 Bug ID: 55462 Summary: mfplay:mfplay sometimes times out on Windows 7 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com mfplay:mfplay sometimes times out on Windows 7: mfplay:mfplay:0a24 done (258) in 120s 0B See https://test.winehq.org/data/patterns.html#mfplay:mfplay The test normally runs in under 1 second which means the time out is caused by a deadlock. However this is pretty rare and has only happened in 1.6% of the WineTest runs and only on Windows 7: * 2023-02-22 win7_newtb-w7pro64-64 * 2023-03-02 win7_newtb-w7pro64-64 * 2023-05-10 win7_newtb-w7u-adm * 2023-07-13 win7_newtb-w7pro64-64_1 * 2023-08-17 win7_newtb-w7pro64-64 -- 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 1

[Bug 52569] New: Zothero Error Launch XUL
by WineHQ Bugzilla 19 Aug '23

19 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=52569 Bug ID: 52569 Summary: Zothero Error Launch XUL Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blbenyamin9(a)gmail.com Distribution: --- Created attachment 71889 --> https://bugs.winehq.org/attachment.cgi?id=71889 Zothero Error Launch Zothero, and imidietly got this error Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x0258904c). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:0258904c ESP:0051cb84 EBP:0051dcec EFLAGS:00010206( R- -- I - -P- ) EAX:00000000 EBX:00000000 ECX:0051cb44 EDX:00990094 ESI:009d13e8 EDI:0bc9d478 -- 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 55344] New: Yuzu fails to start (needs MSVCP140_CODECVT_IDS.dll)
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55344 Bug ID: 55344 Summary: Yuzu fails to start (needs MSVCP140_CODECVT_IDS.dll) Product: Wine Version: 8.12 Hardware: x86-64 URL: https://web.archive.org/web/20230727051938/https://git hub.com/yuzu-emu/yuzu-mainline/releases/download/mainl ine-0-1503/yuzu-windows-msvc-20230722-3dfaf1ff2.tar.xz OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: lingm+winebz(a)posteo.org Distribution: --- 1. Download and extract the Windows version of Yuzu 1503. https://github.com/yuzu-emu/yuzu-mainline/releases/tag/mainline-0-1503 (see the URL field for a direct archived link) 2. Run `wine yuzu.exe` 3. No window even shows up. The full output is: ``` $ wine yuzu.exe 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 007c:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 00d8:err:module:import_dll Library MSVCP140_CODECVT_IDS.dll (which is needed by L"$snip_path$\\yuzu.exe") not found 00d8:err:module:LdrInitializeThunk Importing dlls for L"$snip_path$\\yuzu.exe" failed, status c0000135 ``` `winetricks vcrun2019` works around this problem and allows Yuzu to start properly. -- 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 55331] New: ntdll:file - The 64-bit test_file_disposition_information() gets unsupported error on Windows 10 1607 and 1709
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55331 Bug ID: 55331 Summary: ntdll:file - The 64-bit test_file_disposition_information() gets unsupported error on Windows 10 1607 and 1709 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:file - The 64-bit test_file_disposition_information() gets unsupported error on Windows 10 1607 and 1709: file.c:3141: Test failed: unexpected FileDispositionInformationEx result (expected STATUS_SUCCESS or SSTATUS_INVALID_INFO_CLASS, got c00000bb) See https://test.winehq.org/data/patterns.html#ntdll:file Where c00000bb == STATUS_NOT_SUPPORTED c0000003 == STATUS_INVALID_INFO_CLASS This is a case where early Windows 10 versions don't fully support FileDispositionInformationEx(). Further tests show that: * On Windows 10 1507 we get STATUS_INVALID_INFO_CLASS as expected by the test. * On Windows 10 1607 the 32-bit case gets STATUS_INVALID_INFO_CLASS too but the 64-bit one gets STATUS_NOT_SUPPORTED. * On Windows 10 1709 gets STATUS_NOT_SUPPORTED in both 32 and 64-bit. * And Windows 10 1809 gets STATUS_SUCCESS in both cases. The failures started on 2023-06-27 and a quick test confirms they are caused by the commit that added the test: commit cbc1e4423e6d40221734544d081c718cb2a2a778 Author: Joel Holdsworth <joel(a)airwebreathe.org.uk> AuthorDate: Mon May 1 15:27:57 2023 +0100 ntdll/tests: Add tests for FILE_DISPOSITION_IGNORE_READONLY_ATTRIBUTE. Signed-off-by: Joel Holdsworth <joel(a)airwebreathe.org.uk> -- 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 54676] New: winetricks --verify dotnet20 (AutoHotKey) fails in a wow64 build
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54676 Bug ID: 54676 Summary: winetricks --verify dotnet20 (AutoHotKey) fails in a wow64 build Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: NEW Keywords: dotnet, download, wow64 Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian Created attachment 74190 --> https://bugs.winehq.org/attachment.cgi?id=74190 terminal output The install itself seems to go okay (at least, it exits successfully in quiet mode). Running --verify (which should run the .Net verifier tool) instead just hangs on: /opt/oldwownew/wine-8.3/bin/wine y:\ahk\AutoHotkeyU32.exe C:\windows\Temp\dotnet20.ahk -- 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 55127] New: httpapi:httpapi - test_v2_bound_port() sometimes succeeds in connecting on Windows 10
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55127 Bug ID: 55127 Summary: httpapi:httpapi - test_v2_bound_port() sometimes succeeds in connecting on Windows 10 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: httpapi Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com httpapi:httpapi - test_v2_bound_port() sometimes succeeds in connecting on Windows 10: httpapi.c:1426: Test failed: Connecting to socket succeeded, 0. httpapi.c:1427: Test failed: Unexpected error connecting to socket, 0. See https://test.winehq.org/data/patterns.html#httpapi:httpapi This failure first happened on 2023-02-09 and has happened 4 times since then: * 2023-02-09 win22H2_fgtb-w10pro64-32 * 2023-03-30 win22H2_fgtb-w10pro64-32 * 2023-05-30 win2009_newtb-w1064v2009-64 * 2023-06-15 win2009_newtb-w1064v2009-64 -- 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 54866] New: ieframe:webbrowser - test_SetQueryNetSessionCount() sometimes gets an unexpected session count on Windows
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54866 Bug ID: 54866 Summary: ieframe:webbrowser - test_SetQueryNetSessionCount() sometimes gets an unexpected session count on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ieframe Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ieframe:webbrowser - test_SetQueryNetSessionCount() sometimes gets an unexpected session count on Windows: webbrowser.c:4440: init_count 1 webbrowser.c:4443: Test failed: count = 3 webbrowser.c:4446: Test failed: count = 3 webbrowser.c:4449: Test failed: count = 2 webbrowser.c:4452: Test failed: count = 2 See https://test.winehq.org/data/patterns.html#ieframe:webbrowser These failures only happen on Windows 10 21H1 to 22H2. On Windows 10 init_count is either 1 or 2 (on w8adm is can be 0 too), but all the failures so far happened with an init_count of 1. That said there are also a lot of successful runs with init_count == 1. This looks a lot like the browser creates a net session for its own purposes: * Either init_count is 1 and the extra net session is never created or gets created after test_SetQueryNetSessionCount() is done so all is fine. * Or the extra net session is created it before test_SetQueryNetSessionCount() starts and outlives it so our tests pass. * Or the extra net session gets created after we get init_count but before the next test so that all our tests are off by one. * But it seems the extra net session never gets created after the first SESSION_INCREMENT test. Note that on my Windows 10 VM when I start iexplorer.exe by hand and then run the test I always get init_count == 2. But if IE is not already running I get init_count == 0. In any case if it's a race condition I could send a patch to retry a couple of times. -- 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 54073] New: ws2_32:sock - test_close_events() sometimes fails in Wine
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54073 Bug ID: 54073 Summary: ws2_32:sock - test_close_events() sometimes fails in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ws2_32:sock - test_close_events() sometimes fails in Wine: sock.c:6775: Test succeeded inside todo block: event series matches sock.c:6785: Test failed: got unexpected event 0x20 sock.c:6785: Test failed: event series matches See https://test.winehq.org/data/patterns.html#ws2_32:sock This happens in the nightly WineTest runs about twice per month but also impacts merge requests (for instance MR!1524 and MR!1525 where it happened on the GitLab CI). -- 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 48621] New: Civilization 6 crashes on startup.
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=48621 Bug ID: 48621 Summary: Civilization 6 crashes on startup. Product: Wine Version: 5.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: charles2000wang(a)gmail.com Distribution: --- Created attachment 66468 --> https://bugs.winehq.org/attachment.cgi?id=66468 Game Log file Launching the game opens a black window before promptly crashes with the Firaxis Crash Reporter asking to submit a report. Digging around the game files, I found a log file (GameOverlayRenderer.log) with messages about "Aborting HookFunc because pRealFunctionAddr is null" and other errors. -- 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 8

[Bug 36564] New: 'Candytron' demo: certain objects are black with GLSL enabled
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=36564 Bug ID: 36564 Summary: 'Candytron' demo: certain objects are black with GLSL enabled Product: Wine Version: 1.6-rc1 Hardware: x86 URL: http://www.pouet.net/prod.php?which=9424 OS: Linux Status: NEW Keywords: download, regression Severity: trivial Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: hverbeet(a)gmail.com Regression SHA1: 2014141a253a791fc9c79aae3c8ef3c35b73e658 Created attachment 48657 --> http://bugs.winehq.org/attachment.cgi?id=48657 screenshot (comparison) Some of the rectangles that appear in the demo nearly at 00:30 and at 01:10 are black. They should appear as glowing green rectangles as can be seen in the attached screenshot. Terminal output doesn't reveal anything interesting. Disabling GLSL is a workaround. This is a regression from Wine 1.6-rc1: 2014141a253a791fc9c79aae3c8ef3c35b73e658 is the first bad commit commit 2014141a253a791fc9c79aae3c8ef3c35b73e658 Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Wed May 29 09:45:35 2013 +0200 wined3d: Add support for GLSL based fixed function vertex shaders. :040000 040000 d1b4b75f643d4851d4f51454aa47740261f7857f c46794f61b1952b1e78746272d838574c0948010 M dlls Fedora 20 Nvidia 250 gfx card / Nvidia binary drivers 337.19 wine-1.7.19-70-gd6a59f7 -- 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 20

[Bug 55367] New: Trying to run WatchFaceStudio with wine 8.0 and Ubuntu 23 (lunar)
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55367 Bug ID: 55367 Summary: Trying to run WatchFaceStudio with wine 8.0 and Ubuntu 23 (lunar) Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tda.bkp(a)gmail.com Distribution: --- Created attachment 74949 --> https://bugs.winehq.org/attachment.cgi?id=74949 WatchFaceStudio.exe crash trace Installed WatchFaceStudio successfully, but won't run. Trace attached. -- 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 54831] New: GStreamer gst_init_check() crashes when called from winegstreamer on recent macOS
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54831 Bug ID: 54831 Summary: GStreamer gst_init_check() crashes when called from winegstreamer on recent macOS Product: Wine Version: 8.5 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: bshanks(a)codeweavers.com On macOS Ventura (and I suspect Monterey), gst_init_check() crashes (trying to jump to 0x0) when called by winegstreamer. This is caused by the macOS preloader, here's how: * gst_init_check() calls init_static_plugins() <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/blob/1.22/subprojects/…>, which through some GModule abstractions does a dlopen(NULL) and dlsym() for a symbol that doesn't exist. dlsym() returns NULL, but GModule also calls dlerror() which returns NULL (signaling no error). * init_static_plugins() therefore thinks that the dlsym() was successful, doesn't do a NULL pointer check, and jumps to the NULL pointer. The issue here is dlerror() returning NULL despite there being an error to report. Looking at the macOS dyld source code (<https://github.com/apple-oss-distributions/dyld/blob/dyld-1042.1/dyld/DyldA…>), dlerror() always returns NULL if libSystem was not initialized in the process. And sure enough, when running vmmap on a Wine process, the message "Process exists but has not fully started -- dyld has initialized but libSystem has not" is printed. After more searching in dyld, it turns out that dyld initializes libSystem for binaries targeting 10.5 and newer. The Wine preloader targets 10.7 (since that's the newest target that will generate an LC_UNIXTHREAD binary, critical to how the preloader works). But dyld determines the target OS based on where the program vars (argc, argv, environ, etc) are stored, and a 10.6/10.7 binary should contain a __program_vars section for those. The preloader is missing that, and so (I believe) it falls down to being considered a 10.4 binary. A 10.4 binary should init libSystem in its own _start, but the preloader also doesn't do this, and libSystem stays uninitialized. (See <https://github.com/apple-oss-distributions/dyld/blob/dyld-1042.1/common/Mac…> for where this is determined) I see several possible solutions: * The most obvious one: add a __program_vars section to the preloader, to make it a correct 10.7 binary. In fact, the code can basically be copied out of Apple's C startup code (<https://github.com/apple-opensource/Csu/blob/88/crt.c#L47>). This does work, and libSystem gets initialized. However, libSystem is initialized before any preloader code runs, and malloc zones are already in the middle of areas we want to reserve. That's bad; by itself this approach won't work, but it might if we also: - add linker zerofill sections to block off the entire low 4GB. This is desirable to reserve as much address space as possible for 32-bit EXEs in wow64 mode. - and if zerofill sections are also added to reserve the area where 64-bit EXEs generally load (0x14000000), it might even be possible to stop using the preloader altogether on 64-bit. * Alternately, go the other way, and lean in to being a 10.4 binary. In that case, _start in the preloader needs to call back into dyld to initialize things (like this: <https://github.com/apple-opensource/Csu/blob/88/crt.c#L219>). We could do this after reserving our areas. I'm leery of this approach, mainly because x86_64/10.4 was not a popular target (GUI apps were not supported, they could only link against libSystem). If possible, I'd rather not target such an obscure combination. The preloader has been a source of problems with new OS versions, and I'd like to decrease the amount of black magic it's doing, not increase it. (Running 10.4 x86_64 binaries on modern macOS is still supported though, and Xcode can even still build them.) I'd like to make the __program_vars+zerofill approach work if possible. -- 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

[Bug 54748] New: Greenshot GDI+ status: PropertyNotFound
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54748 Bug ID: 54748 Summary: Greenshot GDI+ status: PropertyNotFound Product: Wine Version: 8.3 Hardware: x86-64 URL: https://objects.githubusercontent.com/github-productio n-release-asset-2e65be/36756917/23e6800e-7d29-11e7-8ac 5-aa92e5646973?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz- Credential=AKIAIWNJYAX4CSVEH53A%2F20230328%2Fus-east-1 %2Fs3%2Faws4_request&X-Amz-Date=20230328T165105Z&X-Amz -Expires=300&X-Amz-Signature=311e88c8da4b8ba0ff5ac6008 cf054338cd6e18afcf64471443530ddae088db0&X-Amz-SignedHe aders=host&actor_id=0&key_id=0&repo_id=36756917&respon se-content-disposition=attachment%3B%20filename%3DGree nshot-NO-INSTALLER-1.2.10.6-RELEASE.zip&response-conte nt-type=application%2Foctet-stream OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: lukasz.wojnilowicz(a)gmail.com Distribution: --- Steps to reproduce: 1) unpack Greenshot-NO-INSTALLER-1.2.10.6-RELEASE.zip 2) wine Greenshot.exe 3) RMB on Greenshot icon in the system tray 4) LMB on "Capture region" 5) Draw a rectangel on your screen Behavior: Error window with contents as below. Expected behavior: No error window. Error window contents: Software version: 1.2.10.6-RELEASE-c2414cf0149a1475ea00520effc01b40087c225c (32 bit) .NET runtime version: 4.0.30319.42000+ Time: 2023-03-28 18:59:01 +02:00 OS: unknown (x32) 10.0 build 2600 revision 30000 GDI object count: 0 User object count: 0 Exception: System.Exception Message: Unknown Error [GDI+ status: PropertyNotFound] Stack: at System.Drawing.GDIPlus.CheckStatus (System.Drawing.Status status) [0x0022b] in <fc2ea6474c6d4315858618f13de6e72a>:0 at System.Drawing.Image.get_PropertyItems () [0x00017] in <fc2ea6474c6d4315858618f13de6e72a>:0 at (wrapper remoting-invoke-with-check) System.Drawing.Image.get_PropertyItems() at GreenshotPlugin.Core.ImageHelper.CloneArea (System.Drawing.Image sourceImage, System.Drawing.Rectangle sourceRect, System.Drawing.Imaging.PixelFormat targetFormat) [0x00172] in <68959698d73243a09b84293d02c00b84>:0 at GreenshotPlugin.Core.ImageHelper.Crop (System.Drawing.Image& image, System.Drawing.Rectangle& cropRectangle) [0x00046] in <68959698d73243a09b84293d02c00b84>:0 at GreenshotPlugin.Core.Capture.Crop (System.Drawing.Rectangle cropRectangle) [0x0001a] in <68959698d73243a09b84293d02c00b84>:0 at Greenshot.Helpers.CaptureHelper.CaptureWithFeedback () [0x00085] in <64ca337812514938b5bb8fc98fce780b>:0 at Greenshot.Helpers.CaptureHelper.MakeCapture () [0x008a0] in <64ca337812514938b5bb8fc98fce780b>:0 at Greenshot.Helpers.CaptureHelper.CaptureRegion (System.Boolean captureMouse) [0x00008] in <64ca337812514938b5bb8fc98fce780b>:0 at Greenshot.MainForm+<>c.<CaptureAreaToolStripMenuItemClick>b__52_0 () [0x00000] in <64ca337812514938b5bb8fc98fce780b>:0 at System.Windows.Forms.Control.InvokeMarshaledCallbackDo (System.Windows.Forms.Control+ThreadMethodEntry tme) [0x000c0] in <d22f8be2dd674c49bd49b314423240b8>:0 at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper (System.Object obj) [0x00029] in <d22f8be2dd674c49bd49b314423240b8>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <e70d6e9587d64cb3abb4b3f99bbf5a0d>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <e70d6e9587d64cb3abb4b3f99bbf5a0d>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <e70d6e9587d64cb3abb4b3f99bbf5a0d>:0 at System.Windows.Forms.Control.InvokeMarshaledCallback (System.Windows.Forms.Control+ThreadMethodEntry tme) [0x0004d] in <d22f8be2dd674c49bd49b314423240b8>:0 at System.Windows.Forms.Control.InvokeMarshaledCallbacks () [0x0008a] in <d22f8be2dd674c49bd49b314423240b8>:0 Terminal output: 0024:fixme:dwmapi:DwmGetWindowAttribute (0003008E 9 0021DA80 16) stub 0024:fixme:uiautomation:UiaClientsAreListening () 0024:fixme:dwmapi:DwmGetWindowAttribute (00050086 9 0021D620 16) stub 0024:fixme:dwmapi:DwmGetWindowAttribute (00050070 9 0021C850 16) stub Additional info: seems to happen on NET 4.5 and Mono as well -- 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 10

[Bug 54546] New: ws2_32:sock - test_write_watch() gets unexpected write counts on Windows 11
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54546 Bug ID: 54546 Summary: ws2_32:sock - test_write_watch() gets unexpected write counts on Windows 11 Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:sock - test_write_watch() gets unexpected write counts on Windows 11: sock.c:7670: Test failed: wrong count 0 sock.c:7701: Test failed: wrong count 0 sock.c:7735: Test failed: wrong count 0 sock.c:7735: Test failed: wrong count 0 sock.c:7735: Test failed: wrong count 0 sock.c:7735: Test failed: wrong count 0 See https://test.winehq.org/data/patterns.html#ws2_32:sock -- 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 52889] New: Freelancer with Crossfire mod crashes on startup
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=52889 Bug ID: 52889 Summary: Freelancer with Crossfire mod crashes on startup Product: Wine Version: 6.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: poweroverwhelming982(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 6857cb56957d691bee76cfe28ef88714cca00f29 Distribution: Ubuntu Created attachment 72282 --> https://bugs.winehq.org/attachment.cgi?id=72282 Wine log at commit 6857cb56957d691bee76cfe28ef88714cca00f29 Since wine-6.19, Freelancer with Crossfire 2.0 mod crashes immediately on startup (as soon as the mod window is shown). Bisecting points to this commit: > commit 6857cb56957d691bee76cfe28ef88714cca00f29 > Author: Jacek Caban <jacek(a)codeweavers.com> > Date: Wed Sep 29 14:09:21 2021 +0200 > > gdi32: Move ntgdi functions to Unix library. I've attached the relevant logs, let me know if there's anything else I can do. Additional info: OS: Ubuntu Focal 20.04.3 LTS Kernel: 5.13.0-30-generic x86_64 Wine Prefix: 32 bit, clean GPU: NVIDIA Corporation GF108 [GeForce GT 730] (rev a1) Graphics Driver: Proprietary NVIDIA ver. 390.144 -- 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 8

[Bug 52474] New: ws2_32:sock fails intermittently - 'Test failed: expected timeout'
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=52474 Bug ID: 52474 Summary: ws2_32:sock fails intermittently - 'Test failed: expected timeout' Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com Distribution: --- The test_connect_events() function contains the following checks, where the check (2) fails intermittently: 1. check_events(ctx, FD_CONNECT, FD_WRITE, 200); 2. check_events(ctx, 0, 0, 0); A hypothesis for the cause of the test failure is that the WSAEnumNetworkEvents() call inside the check (1) races with the server setting the event. Note that WSAEnumNetworkEvents performs the following steps: a. It calls ResetEvent on the given event. b. It issues IOCTL_AFD_GET_EVENTS command on the socket to retrieve the events so far. It's possible that the event may be set by the server between (a) and (b), which lingers until the next call to WSAEnumNetworkEvents(). This explains why the event wait in check (2) is satisfied immediately but subsequent tests report no events. -- 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 34678] New: Not all serial port work in wine
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=34678 Bug #: 34678 Summary: Not all serial port work in wine Product: Wine Version: 1.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: rewineland(a)gmail.com Classification: Unclassified I have wine 1.6 install on Ubuntu 12.04 with kernel 3.8.0-31-generial. I have 2 serial ports on board and an add-on card with 8 more.I can get the the on board and 7 of the add-on to work as 1 though 9 comports but com10 I can not get any data though. the port is listed as ttyCTI7, when I connect to that I have data going back and forth. It just wont go into the windows program. Any ideas on what to do. I need to have all 10 ports. -- 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 10

[Bug 55283] New: amstream:amstream systematically crashes and times out on gitlab-debian-32
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55283 Bug ID: 55283 Summary: amstream:amstream systematically crashes and times out on gitlab-debian-32 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: major Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- amstream:amstream systematically crashes and times out on gitlab-debian-32: Unhandled exception: assertion failed in wow64 32-bit code (0xf7f19559). Backtrace: =>0 0xf7f9a559 __kernel_vsyscall+0x9() in [vdso].so (0xf7f34ff4) 1 0xf7da21d7 in libc.so.6 (+0x8a1d7) (0xf7f34ff4) 2 0xf7d510d1 in libc.so.6 (+0x390d1) (0xf7f34ff4) 3 0xf7d3a26a in libc.so.6 (+0x2226a) (0xf7f34ff4) 4 0x71a4de79 in libllvm-15.so.1 (+0x875e79) (0x0022e910) 5 0x00000040 (0x00000040) 0xf7f9a559 __kernel_vsyscall+0x9 in [vdso].so: pop %ebp See https://test.winehq.org/data/patterns.html#amstream:amstream The failures started on 2023-07-10 which corresponds to the GitLab CI switch to Debian 12. What makes this very bad is that the failure is systematic so every single merge request has been getting a GitLab CI error since then. So it is pretty urgent to either: 1. Fix the test if something is wrong with it. 2. Fix the gitlab-debian-32 test environment if it is wrong. 3. Skip amstream:amstream if neither of the above is doable in a reasonable timeframe. -- 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 15

[Bug 53171] New: advapi32:registry - test_performance_keys() sometimes fails due to time going backwards!
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=53171 Bug ID: 53171 Summary: advapi32:registry - test_performance_keys() sometimes fails due to time going backwards! Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com advapi32:registry - test_performance_keys() sometimes fails due to time going backwards: registry.c:3757: Test failed: key FFFFFFFF80000004: value (null): got times 132999520626290092, 132999520626290092, 132967560392269933 registry.c:3763: Test failed: key FFFFFFFF80000004: value (null): got times 132999520626290092, 132999520626290000, 132967560392269933 https://test.winehq.org/data/patterns.html#advapi32:registry This failure is pretty rate: I only found 4 cases (~0.9%): win2009_newtb-w1064-tsign, win21H1_newtb-w10pro64-mx-MX, 2x win21H2_fgtb-w10pro64. The failure lines above happened on w10pro64-mx-MX on 2022-06-17. Here are the corresponding timestamps: systime1 = 132999520626290092 = 2022-06-17 15:07:42.629009 file_time = 132999520626290000 = 2022-06-17 15:07:42.629000 systime2 = 132967560392269933 = 2022-05-11 15:20:39.226993 file_time is a little lower than systime1 which is normal due to its granularity. What is totally wrong however is that systime2 is way lower than systime1. The interesting part is that the live snapshot was created on 2022-05-11 which matches systime2. This scenario is confirmed it two of the other instances; the snapshot creation time for the last case is unknown but a match with systime2 is plausible. After restoring the VM from the live snapshot LibvirtTool sets the VM time through TestAgent::SetTime(): https://gitlab.winehq.org/winehq/tools/-/blob/master/testbot/bin/LibvirtToo… https://gitlab.winehq.org/winehq/tools/-/blob/master/testbot/src/testagentd… So it looks like in rare cases the system time gets reset backwards precisely between this test's two NtQuerySystemTime() calls, which is really unlucky... or lucky: maybe it happens in other cases causing less obvious failures. I don't know if TestAgentd sets the time wrong, if there's something wrong with Windows, or if this is an artifact of the QEmu clocks: <clock offset='localtime'> <timer name='rtc' tickpolicy='delay'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='yes'/> <timer name='hypervclock' present='yes'/> </clock> -- 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 52492] New: stack overflow from GdipFlattenPath
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=52492 Bug ID: 52492 Summary: stack overflow from GdipFlattenPath Product: Wine Version: 7.1 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: rjfeuerbach(a)gmail.com Created attachment 71787 --> https://bugs.winehq.org/attachment.cgi?id=71787 test patch to replicate the curves and stack overflow I have a third party application, unfortunately not available for download, that is generating a virtual stack overflow error. Using +replay and eventually +gdiplus messages, the cause was narrowed down to be due to calls to GdipFlattenPath. Attached is a patch to gdiplus/test/graphicspath.c to include the precise curves that cause the stack overflow. I believe the problem is due to the comparison of REALs with == in the flatten_bezier helper function. -- 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 22

[Bug 55422] New: mfmediaengine:mfmediaengine - test_GetDuration() fails in Wine
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55422 Bug ID: 55422 Summary: mfmediaengine:mfmediaengine - test_GetDuration() fails in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- mfmediaengine:mfmediaengine - test_GetDuration() fails in Wine: mfmediaengine.c:1961: Test failed: Unexpected res 0x102. See https://test.winehq.org/data/patterns.html#mfmediaengine:mfmediaengine This failure started with the commit that introduced the tests: commit 613d7b099986828212299a8e98179f22c86b80ab Author: Zhiyi Zhang <zzhang(a)codeweavers.com> Date: Fri Aug 4 17:35:04 2023 +0800 mfmediaengine/tests: Test IMFMediaEngine::GetDuration(). -- 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 54720] New: Spider-Man: Shattered Dimensions - dialogue audio doesn't play
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54720 Bug ID: 54720 Summary: Spider-Man: Shattered Dimensions - dialogue audio doesn't play Product: Wine Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: tinozzo123(a)tutanota.com Distribution: --- Created attachment 74226 --> https://bugs.winehq.org/attachment.cgi?id=74226 Logs taken with a clean 32 bit prefix with 32 bit Wine devel 8.4, WINEDEBUG=+xactengine,+xaudio2,+x3daudio. In Spider-Man: Shattered Dimensions, the audio that is supposed to be played by the characters during in-game dialogues doesn't play. All the other kinds of audio work. A workaround to this is by installing xact with winetricks. -- 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 44816] New: Cygwin/ MSYS2 `script -e` exit status forwarding randomly returns zero for non zero child process
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=44816 Bug ID: 44816 Summary: Cygwin/MSYS2 `script -e` exit status forwarding randomly returns zero for non zero child process Product: Wine Version: 3.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, to track https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-Deal… Mentioned here: https://wine-staging.com/news/2015-08-23-release-1.7.50.html --- quote --- Do not allow to deallocate thread stack for current thread (MSYS2, Wine Staging Bug #241) --- quote --- After some archaeology I found the Cygwin mailing list discussion here: https://cygwin.com/ml/cygwin/2015-09/msg00114.html --- quote --- > Ah, ok. What OS does Wine emulate here? Have a look at > https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/cygt… > > The terminate_thread_frees_stack flag is set to false for XP/2003 and to > true for any newer OS. I guess this is a double-free because Wine's > TerminateThread already freed the stack and Cygwin got the info it's > supposedly running under XP/2003, so it tries to workaround the fact > that TerminateThread on these systems didn't free the stack by themselves. > Wine emulates Windows XP here, I double checked Wine source code and I can confirm Wine doesn't free the stack: NtTerminateThread() -> abort_thread() -> terminate_thread() https://github.com/wine-compholio/wine-patched/blob/8b3a785e97a7e28ff58731b… Cygwin reports wincap as wincap_xpsp2 which is also correct here. > we need to know what address ret=61005767 is refering to. addr2line would help. As you point out, ret=61005767 is the call to VirtualFree() inside cygthread::terminate_thread () https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/cygt… After combine the information we have so far, I think the problem is clear now. It's not Cygwin's fault, it's Wine's fault. Wine's WaitForSingleObject() needs to wait long enough after the TerminateThread() call, so the target thread has enough time to finish the system cleanup and return correct exit_code before Cygwin call VirtualFree to free the stack. But in our current implementation Wine's WaitForSingleObject returns too early, it shouldn't return before the system thread cleanup done, as a result there is a race here. We are thinking of a solution in Wine. Thanks again for the great help! --- quote --- $ wine --version wine-3.4 Regards -- 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 30655] New: GRID2: Low (1 - 3) FPS during race, but not in in-game menus.
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=30655 Bug #: 30655 Summary: GRID2: Low (1 - 3) FPS during race, but not in in-game menus. Product: Wine Version: 1.5.2 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: linards.liepins(a)gmail.com Classification: Unclassified Created attachment 40128 --> http://bugs.winehq.org/attachment.cgi?id=40128 in-game benchmark test #! Game itself installed with latest winetricks. -- 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 25

[Bug 28603] New: Winedbg sometimes receives invalid parameters
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=28603 Bug #: 28603 Summary: Winedbg sometimes receives invalid parameters Product: Wine Version: 1.3.29 Platform: x86 URL: http://www.winehq.org/pipermail/wine-patches/2011-Sept ember/106508.html OS/Version: Linux Status: NEW Keywords: download, source, testcase Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com CC: julliard(a)winehq.org Classification: Unclassified Created attachment 36753 --> http://bugs.winehq.org/attachment.cgi?id=36753 relay,seh,tid,dbghelp,winedbg I sent a patch to eliminate this dialog: http://www.winehq.org/pipermail/wine-patches/2011-September/106508.html but Alexandre said this should never happen. I see it occasionally on various systems, but since I wrote the patch, haven't found a very reliable testcase. I've found a reliable testcase with make test on Alpine Linux (which uses uclibc). It may not be the best testcase, since it's not using glibc (and also use PaX), but AJ asked for a log, so here we go :). relay,seh,tid,dbghelp,winedbg attached the testcase used was oleaut32/tmarshal wine-1.3.29-217-g5432611 -- 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 6

[Bug 55258] New: steam: small window floating on top of all windows even in fullscreen mode
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55258 Bug ID: 55258 Summary: steam: small window floating on top of all windows even in fullscreen mode Product: Wine Version: 8.12 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 74873 --> https://bugs.winehq.org/attachment.cgi?id=74873 steam_window_bug.png When running steam with new versions of wine, I'm getting a small square window which is always on top of all windows, even when I'm playing fullscreen game. It's usually located around center of screen for me, but during bisecting I also got a few builds when it appeared at top left corner. I've tested it with following wine versions: wine 7.0.2: win7 prefix: good wine 7.0.2: win10 prefix: does not start wine 8.0.1: win7 prefix: good wine 8.0.1: win10 prefix: good wine 8.9: win10 prefix: bad wine 8.12: win10 prefix: bad After that I ran git bisect with following build: mkdir build32 build64 cd build64 ../configure --with-mingw --enable-win64 --prefix=/tmp/wineinstall cd ../build32 ../configure --with-mingw --with-wine64=../build64 --prefix=/tmp/wineinstall cd ../build64 make $JOBS cd ../build32 make $JOBS make $JOBS install cd ../build64 make $JOBS install My results are: 2504a2d7bca47fc77bb523114d7b0b6e60213116 is the first bad commit commit 2504a2d7bca47fc77bb523114d7b0b6e60213116 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Mon Mar 27 11:58:50 2023 +0200 imm32: Keep the IME UI window on the default input context. dlls/imm32/imm.c | 61 ++++++++++++++++++++++++++++++++------------------------ 1 file changed, 35 insertions(+), 26 deletions(-) $ git bisect log # bad: [9ffeb2622d087a6189ca916553529824791010c3] Release 8.9. # good: [d8b2687760f7c07eaf481aba2835b820d3092b3e] Release 8.0.1. git bisect start 'wine-8.9' 'wine-8.0.1' # skip: [6677c044abb711f423fadfb61f2c9a37da6ff686] Release 8.0. git bisect skip 6677c044abb711f423fadfb61f2c9a37da6ff686 # good: [7771a9ae79930d112051cfe18b27dec1e5edd245] widl: Simplify attribute creation with either int or ptr value. git bisect good 7771a9ae79930d112051cfe18b27dec1e5edd245 # bad: [d1c317720ab6a92811c013408844ffd9e581b2a2] mfreadwrite: Fix an address of operator typo. git bisect bad d1c317720ab6a92811c013408844ffd9e581b2a2 # bad: [66bef6db20f72e88a38c4b264e13639015d7817d] msvcrt: Use the sinhf() implementation from the bundled musl library. git bisect bad 66bef6db20f72e88a38c4b264e13639015d7817d # bad: [17fbef91929af9c6ab98e53fb2a54942f0f1a0a5] wmvcore/tests: Don't cast NULL to another pointer type. git bisect bad 17fbef91929af9c6ab98e53fb2a54942f0f1a0a5 # skip: [83f0862b43f7b1b7bd23830b4339894c35febea7] wineps: Handle EMR_SETARCDIRECTION record in spool files. git bisect skip 83f0862b43f7b1b7bd23830b4339894c35febea7 # good: [6a88500af29b82040f0518eb87171ca047fb95aa] hidparse.sys: Include zero-count reports in cap count. git bisect good 6a88500af29b82040f0518eb87171ca047fb95aa # good: [62ef3c5be1d2c5374399984588a9daa75663d030] taskkill: Factor out get_task_pid(). git bisect good 62ef3c5be1d2c5374399984588a9daa75663d030 # bad: [956541c9c823fb6048047893545dcee4c108730e] d3d10/effect: Add support for umin/umax instructions. git bisect bad 956541c9c823fb6048047893545dcee4c108730e # good: [4b04d357739f261457316d55b79ecbcff9c0be84] imm32/tests: Add explicit ImmLoadIME / ImmFreeLayout calls. git bisect good 4b04d357739f261457316d55b79ecbcff9c0be84 # bad: [2504a2d7bca47fc77bb523114d7b0b6e60213116] imm32: Keep the IME UI window on the default input context. git bisect bad 2504a2d7bca47fc77bb523114d7b0b6e60213116 # good: [9117ce4185146a5edd47467d370b3e4dfa588191] imm32/tests: Test ImmProcessKey with the installed IME. git bisect good 9117ce4185146a5edd47467d370b3e4dfa588191 # good: [43e22eaa76a443e3053868df1bd8c5d4130a9fde] imm32/tests: Test IME UI window and IME window presence. git bisect good 43e22eaa76a443e3053868df1bd8c5d4130a9fde # good: [0ddad3564f3260f53e5a50b615f6aa6ba27e032b] imm32: Update existing input contexts on layout change. git bisect good 0ddad3564f3260f53e5a50b615f6aa6ba27e032b # first bad commit: [2504a2d7bca47fc77bb523114d7b0b6e60213116] imm32: Keep the IME UI window on the default input context. OS: Gentoo Linux Amd64 Kernel: 6.1.38-gentoo DE: KDE 5.27.5 glxinfo: OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 7900 XTX (gfx1100, LLVM 16.0.6, DRM 3.49, 6.1.38-gentoo.65) OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.3 OpenGL core profile shading language version string: 4.60 -- 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

[Bug 54413] New: ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=54413 Bug ID: 54413 Summary: ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:sock - DuplicateHandle(socket) sometimes look like a socket in test_WSAGetOverlappedResult() on Windows: sock.c:12512: Test failed: got 1. sock.c:12513: Test failed: got 0. See https://test.winehq.org/data/patterns.html#ws2_32:sock This failure is pretty rare, there are only 4 known instances: * 2022-09-27 on w1064 64 bit (21h2) * 2022-11-15 on w10pro64-hi-u8 64 bit (21h1) * 2023-01-25 on w11pro64 64 bit (21h2) * 2023-01-25 on w1064v2009 64 bit The test creates a socket, treats it as a handle and duplicates it, then checks whether the duplicate handle behaves like a socket which it normally does not, causing WSAGetOverlappedResult() to fail (return 0) and WSAGetLastError() to be set to WSAENOTSOCK. But in these four cases WSAGetOverlappedResult() succeeded which would indicate the duplicate handle looked like a socket? -- 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 8

[Bug 44546] New: The Settlers II: 10th Anniversary runs very slow when CSMT enabled
by wine-bugs＠winehq.org 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=44546 Bug ID: 44546 Summary: The Settlers II: 10th Anniversary runs very slow when CSMT enabled Product: Wine Version: 3.2 Hardware: x86 URL: https://www.fileplanet.com/165168/160000/fileinfo/The- Settlers-II:-10th-Anniversary-Demo-v9801 OS: Linux Status: NEW Keywords: performance Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- The game is running painfully slow in Wine 3.2. Can be observed while it is playing the opening video, in the menus and during gameplay too. Loading times are also incredibly long when csmt is enabled. Disabling csmt makes the game run smoothly. There is nothing suspicious in the terminal. Can be reproduced with the demo version. I have native d3dcompiler_43 and d3dx9_29 installed. settlers2_demo2_multilang.exe (318M) md5sum: c738916e0f5f4c9b780898f66e50941f Wine 3.2 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 390.25 -- 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 14

[Bug 55291] New: gdi32:dc - print_something() gets a bad signature on fg-deb64-*
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55291 Bug ID: 55291 Summary: gdi32:dc - print_something() gets a bad signature on fg-deb64-* Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- gdi32:dc - print_something() gets a bad signature on fg-deb64-*: dc.c:1501: Test failed: wrong signature: See https://test.winehq.org/data/patterns.html#gdi32:dc This does not depend on bitness, happens systematically and a bisect shows that the failure started with the commit below: commit d5373ef6f92d36971859db0746600188ada22a7d Author: Piotr Caban <piotr(a)codeweavers.com> Date: Sun Jul 9 13:05:42 2023 +0200 wineps: Buffer data sent to printer port. -- 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 55231] New: Warframe: camera/mouse stuck in X-axis
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55231 Bug ID: 55231 Summary: Warframe: camera/mouse stuck in X-axis Product: Wine Version: 8.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pmargeti34(a)gmail.com Distribution: --- Wine 8.12 introduces a regression in Warframe: there seems to be a hard limit to how much camera can be turned on the X-axis. After spinning the camera in the same direction a few times, it gets stuck and it's no longer possible to turn in in that direction until it is first turned in the opposite direction. This happens when Warframe is either in full screen mode or borderless fullscreen mode. Windowed mode isn't affected. Warframe is a free to play game and the installer can be obtained here: https://www.warframe.com/download OS: Archlinux Linux 6.4.3 -- 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 17

[Bug 55152] New: Crash in Notepad++ processing a WM_DRAWITEM message
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55152 Bug ID: 55152 Summary: Crash in Notepad++ processing a WM_DRAWITEM message Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: julliard(a)winehq.org Distribution: --- Running the 32-bit Notepad++ 8.5.4 in new wow64 mode crashes on startup when processing a WM_DRAWITEM message. The exception is swallowed by win32u so it still works, but we get a message: 0024:err:seh:KiUserCallbackDispatcher ignoring exception The root cause is that because Notepad++ added a WH_CALLWNDPROC hook, in win32u process_message(), instead of returning to SendMessageW and have it call the winproc, we call it ourselves through KeUserModeCallback. But at that point the message has been converted to 64-bit so we pass a (truncated) 64-bit lparam to the 32-bit winproc. The crash was revealed by a82238fad52761114ab2488d422fad3f70dbb854, which moves the 64-bit stack to high memory. Previously the lparam pointer would fit in 32-bit which avoided the crash, but it would still point to a 64-bit DRAWITEMSTRUCT. -- 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 51443] New: Test fails in remove_dir_all crate when creating file
by WineHQ Bugzilla 18 Aug '23

18 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=51443 Bug ID: 51443 Summary: Test fails in remove_dir_all crate when creating file Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- Hi, Steps to reproduce on clear wine-devel 6.12 ``` wget https://static.rust-lang.org/dist/rust-1.53.0-x86_64-pc-windows-gnu.msi msiexec /i rust-1.53.0-x86_64-pc-windows-gnu.msi git clone https://github.com/XAMPPRocky/remove_dir_all.git cd remove_dir_all git checkout 9b164cecdb4a0590af68be8b22f9c747402237e3 wine cargo test ``` should print this ``` running 4 tests test removes_read_only ... FAILED test removes_empty ... ok test removes_files ... ok test removes_dirs ... ok failures: ---- removes_read_only stdout ---- thread 'removes_read_only' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 5, kind: PermissionDenied, message: "Access denied." }', tests\windows.rs:68:49 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace failures: removes_read_only test result: FAILED. 3 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s error: test failed, to rerun pass '--test windows' ``` I tested it and this works fine in Windows Server 2019 Source code of failed test - https://github.com/XAMPPRocky/remove_dir_all/blob/9b164cecdb4a0590af68be8b2… ``` fn removes_read_only() { env_logger::init(); for i in 0..5 { let path = format!("./readonly/{}/subdir", i); fs::create_dir_all(&path).unwrap(); let file_path = format!("{}/file.txt", path); { let file = File::create(&file_path).unwrap(); ``` -- 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 55449] New: Yaesu Wires-X offline and no internet
by WineHQ Bugzilla 16 Aug '23

16 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=55449 Bug ID: 55449 Summary: Yaesu Wires-X offline and no internet Product: Wine Version: 8.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: oleacc Assignee: wine-bugs(a)winehq.org Reporter: michael.vencio(a)gmail.com Distribution: --- Created attachment 75008 --> https://bugs.winehq.org/attachment.cgi?id=75008 debug output Yaesu Wires-X is an amateur radio application https://www.yaesu.com/jp/en/wires-x/index.php the application is installed and running but cannot connect to the internet. attached is the debug log file. -- 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 34374] New: Mac driver does not respect "Emulate a virtual desktop" option
by wine-bugs＠winehq.org 16 Aug '23

16 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=34374 Bug #: 34374 Summary: Mac driver does not respect "Emulate a virtual desktop" option Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: winemac.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: samael5(a)verizon.net Classification: Unclassified The Mac driver launches all apps in fullscreen mode, regardless of whether "Emulate a virtual desktop" is set. Virtual desktop still functions as expected when using the X11 driver on Mac. -- 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 6

[Bug 39012] New: Game "Yesterday" crashes while being played (OS X Yosemite)
by wine-bugs＠winehq.org 15 Aug '23

15 Aug '23

https://bugs.winehq.org/show_bug.cgi?id=39012 Bug ID: 39012 Summary: Game "Yesterday" crashes while being played (OS X Yosemite) 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: deka95500(a)hotmail.com Hi everyone, I have a version of Yesterday that was built using a wrapper from this website(external link). Everything worked fine until I reached the 3rd stage. The game was stuck on a loading screen and eventually crashed before showing a message saying: "Yesterday.exe has encountered a serious problem and needs to close." The wrapper is using Wineskin 2.5.8 / WS8Wine1.3.16. I'm using Mac OS X Yosemite 10.10.3 on a 2013 MBP. Can you please help me figure out what the issue is? Thank you! -- 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 10

[Bug 14713] New: Xara Xtreme 4: Resizing handles not visible
by wine-bugs＠winehq.org 15 Aug '23

15 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=14713 Summary: Xara Xtreme 4: Resizing handles not visible Product: Wine Version: 1.1.2 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: info(a)linopus.de Xara Xtreme 4: Resizing handles not visible Xara Xtreme 4, the latest edition of the vector drawing application from Xara (30 days trial available at http://www.xara.com/us/downloads/xtreme/ ), shows no resizing handles when selecting an object. The resizing handles should be visible when clicking an object with the select tool. By contrast, the turning/shearing handles are visible. The turning/shearing handels appear when clicking an object twice with the select tool. Additionally, Bezier handles and points on curves do appear, but in wrong colors (cyan instead of red). Bezier handles and points appear when using the edit shape tool. This is on a wine 1.1.2 install on Ubuntu Linux 8.04 in its standard settings. The same bug is present when using Xara Xtreme X1, which is the thirdlast edition. The bug is also present in earlier versions of wine (e.g. 0.9.56) and CrossOver (e.g. 7.0.1). Yours sincerely Tobias Hilbricht -- 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 10

[Bug 10471] New: Radmin viewer 3.1: Ungrayed disabled menu item in the " Connection Properties" window
by wine-bugs＠winehq.org 15 Aug '23

15 Aug '23

http://bugs.winehq.org/show_bug.cgi?id=10471 Summary: Radmin viewer 3.1: Ungrayed disabled menu item in the "Connection Properties" window Product: Wine Version: 0.9.48. Platform: PC URL: http://www.famatech.com/download/rview31.exe OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: wine-gui AssignedTo: wine-bugs(a)winehq.org ReportedBy: bugs.radmin(a)gmail.com We got an error: 1. Installed Radmin server 3.1 (http://www.famatech.com/download/rserv31.exe) on a windows computer. 2. Installed Radmin viewer 3.1 on a linux computer with wine installed. 3. Started Radmin viewer and open "Connection Properties" window (can be reached "Right click on connection icon" --> "Properties" or "Connection" --> "Connect to"). The list of intermediate hosts in "Advanced settings" should be grayed (disabled) until checkbox "Connect through host" is marked. The error was tested on Fedora Core 7 installation with the last wine package from fedora update site (fedora_mirror/fedora/linux/updates/7/i386/). -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 12

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 August 2023