April 2023 - Wine-bugs - list.winehq.org

[Bug 53898] New: Programmer's File Editor MDI window contents incorrectly refreshed after closing an MDI document
by WineHQ Bugzilla 18 Apr '23

18 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=53898 Bug ID: 53898 Summary: Programmer's File Editor MDI window contents incorrectly refreshed after closing an MDI document Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine_bugzilla(a)sctb.ch Distribution: --- Created attachment 73439 --> https://bugs.winehq.org/attachment.cgi?id=73439 Corrupted window. I've been using Programmer's File Editor (PFE), a text editor from 1999, with WINE, since the beginning of time. There has always been a problem that when the editor has multiple MDI windows open, and a single window has been maximized (so it fills the entire editor), and that window is closed, the window which replaces it does not correctly refresh the editor display - the content is visually garbled. Minimizing and restoring the editor induces a correct refresh. Screenshot attached of a garbled window, and then the same window after a min-restore induced refresh (so you can more easily see the corruption). -- 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 54855] New: When Tahoma uses fontlink to Noto Sans CJK SC, the final Chinese output will be distorted
by WineHQ Bugzilla 18 Apr '23

18 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54855 Bug ID: 54855 Summary: When Tahoma uses fontlink to Noto Sans CJK SC, the final Chinese output will be distorted Product: Wine Version: 8.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- in > HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink make > Tahoma -> NotoSansCJK-Regular.ttc,Noto Sans CJK SC Chinese display is distorted I have provided a demo that can be used on:https://bugs.winehq.org/attachment.cgi?id=74311 and the problem photo on : https://bugs.winehq.org/attachment.cgi?id=74315 -- 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 54065] New: Windower 4 with FFXI Online has no keyboard input
by WineHQ Bugzilla 18 Apr '23

18 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54065 Bug ID: 54065 Summary: Windower 4 with FFXI Online has no keyboard input Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: dinput Assignee: wine-bugs(a)winehq.org Reporter: reaper2021(a)protonmail.com Distribution: --- Created attachment 73616 --> https://bugs.winehq.org/attachment.cgi?id=73616 error log Keyboard input in FFXI with Windower 4 has been broken for a long time. It fails in 7.20, and all the way down to 5.0rc2 or earlier (I stopped testing there). Keyboard input works in wine-staging-5-0rc5, and no longer works in wine-staging-5-0-rc6. My installation for which I posted the log uses dxvk and dgVoodoo, but the problem also occurs without that. Steps to reproduce: 1. make a 32 bit prefix, windows version seems noncritical (7 or 10). 2. install official FFXI distribution from http://www.playonline.com/ff11us/download/media/install_win.html (install hangs for a seemingly long time at some step, disk space check if I recall, just wait) 3. winetricks dotnet462 gdiplus (without dotnet, windower will not work. Gdiplus just makes the fonts in the windower console look nicer, it's not absolutely required for reproduction.) 4. install windower 4.3 from https://www.windower.net/ , to $WINEPREFIX/drive_c/windower4.3/ 5. wine $WINEPREFIX/drive_c/windower4.3/Windower.exe At this step, you'll need an FFXI subscription and character to log in and get to the point where you see that the keyboard doesn't work. -- 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 8532] JawsEditor 2.5/3.0 reports "Invalid imagesize" on startup ('IPicture::SaveAsFile' method too stubby/incorrect)
by WineHQ Bugzilla 17 Apr '23

17 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=8532 temp82(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |temp82(a)luukku.com --- Comment #14 from temp82(a)luukku.com --- still valid as wine 8.6. -- 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 54851] New: comctl32:tooltips - test_TTN_SHOW() sometimes gets extra or missing WM_NOTIFY messages in Wine
by WineHQ Bugzilla 17 Apr '23

17 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54851 Bug ID: 54851 Summary: comctl32:tooltips - test_TTN_SHOW() sometimes gets extra or missing WM_NOTIFY messages in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- comctl32:tooltips - test_TTN_SHOW() sometimes gets extra or missing WM_NOTIFY messages in Wine. For instance: tooltips.c:1218: Test failed: TTN_SHOW parent seq: the msg sequence is not complete: expected 004e - actual 0000 tooltips.c:1218: Failed sequence TTN_SHOW parent seq: tooltips.c:1218: 0: expected: msg 004e - actual: nothing or tooltips.c:1218: Test failed: TTN_SHOW parent seq: the msg sequence is not complete: expected 0000 - actual 004e tooltips.c:1218: Failed sequence TTN_SHOW parent seq: tooltips.c:1218: 0: expected: 004e - actual: 004e wp 1234abcd lp 0072eec0 tooltips.c:1218: 1: expected: nothing - actual: 004e wp 1234abcd lp 0072ef20 See https://test.winehq.org/data/patterns.html#comctl32:tooltips In are cases both issues happen or the same issue happens twice; once before the load_v6_module() call, and once after. -- 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 54850] New: comctl32:tooltips - test_customdraw() sometimes fails to get the current tool on Windows
by WineHQ Bugzilla 17 Apr '23

17 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54850 Bug ID: 54850 Summary: comctl32:tooltips - test_customdraw() sometimes fails to get the current tool on Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:tooltips - test_customdraw() sometimes fails to get the current tool on Windows tooltips.c:252: Test failed: 3: Failed to get current tool 0. tooltips.c:259: Test failed: 3: Unexpected hwnd CCCCCCCCCCCCCCCC. tooltips.c:260: Test failed: 3: Unexpected hinst CCCCCCCCCCCCCCCC. tooltips.c:261: Test failed: 3: Unexpected uId cccccccccccccccc. tooltips.c:262: Test failed: 3: Unexpected lParam cccccccccccccccc. See https://test.winehq.org/data/patterns.html#comctl32:tooltips This can happen either before or after the load_v6_module() call, and in any of the for loop iterations, though normally only one of them per run. -- 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 52987] New: comctl32:tooltips - test_customdraw() fails systematically on some Windows 10 machines
by WineHQ Bugzilla 17 Apr '23

17 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=52987 Bug ID: 52987 Summary: comctl32:tooltips - test_customdraw() fails systematically on some Windows 10 machines Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com comctl32:tooltips - test_customdraw() fails systematically on some Windows machines: tooltips.c:251: Test failed: 0: Failed to get current tool 0. tooltips.c:258: Test failed: 0: Unexpected hwnd CCCCCCCCCCCCCCCC. tooltips.c:259: Test failed: 0: Unexpected hinst CCCCCCCCCCCCCCCC. tooltips.c:260: Test failed: 0: Unexpected uId cccccccccccccccc. tooltips.c:261: Test failed: 0: Unexpected lParam cccccccccccccccc. tooltips.c:251: Test failed: 1: Failed to get current tool 0. tooltips.c:258: Test failed: 1: Unexpected hwnd CCCCCCCCCCCCCCCC. tooltips.c:259: Test failed: 1: Unexpected hinst CCCCCCCCCCCCCCCC. tooltips.c:260: Test failed: 1: Unexpected uId cccccccccccccccc. tooltips.c:261: Test failed: 1: Unexpected lParam cccccccccccccccc. [... all 6 iterations fail ...] https://test.winehq.org/data/patterns.html#comctl32:tooltips Also this impacts both test_customdraw() calls: the one after test_create_tooltip(FALSE) and the one after test_create_tooltip(TRUE) though the latter is more random. When the latter fails there is an extra couple of failures in test_TTN_SHOW(): tooltips.c:261: Test failed: 5: Unexpected lParam cccccccccccccccc. tooltips.c:1216: Test failed: TTN_SHOW parent seq: the msg sequence is not complete: expected 004e - actual 0000 tooltips.c:1216: Failed sequence TTN_SHOW parent seq: tooltips.c:1216: 0: expected: msg 004e - actual: nothing v6util.h:92: created cc6.manifest tooltips.c:251: Test failed: 0: Failed to get current tool 0. [...] tooltips.c:1216: Test failed: TTN_SHOW parent seq: the msg sequence is not complete: expected 004e - actual 0000 However the failure pattern is strange: * The failures mostly happen on the cw-gtx560 and cw-rx460 machines. But w1064v1709-64 has the same failures so it's not a real hardware vs. VM issue. * The failures happen on Windows 10 1709, 21h1 and 21h2, but not on 1507, 1607, 1809 or 2004. 1909 had failures on March 21 and 22 but not in the month since then. So it does not really seem related to the Windows version. * cw-gtx560-21H1 and cw-rx460-21H1 never had failures in the 32-bit tests but the failures happen in 32-bit on cw-gtx560-1709 and cw-rx460-1709. So it's not a bitness issue and it should not be a machine configuration issue either. The failure on line 251 indicates that there is no tooltip at all. Maybe there is a window that has the focus and prevented the tooltip from opening? (that window if any is not visible in the final screenshot) If it is a focus issue, skipping when the windows does not have the focus could avoid the failures. -- 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 6893] ChessBase Light 6 does not install
by WineHQ Bugzilla 17 Apr '23

17 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=6893 --- Comment #25 from temp82(a)luukku.com --- still an issue. wine 8.6. -- 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 30826] New: Gigasoft's ProEssentials demo crashes on startup
by wine-bugs＠winehq.org 16 Apr '23

16 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=30826 Bug #: 30826 Summary: Gigasoft's ProEssentials demo crashes on startup Product: Wine Version: 1.5.5 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified To reproduce, wget http://www.gigasoft.com/PE7-Pro-Setup.exe wine PE7-Pro-Setup.exe cd .wine/drive_c/ProEssentials7/DEMO wine PEDemo.exe Click the popup window to make it go away. Unhandled exception: page fault on read access to 0x5050ff98 in 32-bit code (0x7ed36a26). Or, sometimes: Unhandled exception: page fault on read access to 0x00000048 in 32-bit code (0x7ed2ea26). The backtrace seems the same either way: Backtrace: =>0 get_log_fontW+0x16(font=0x720041, graphics=0x154780, lf=0x32e92c) [dlls/gdiplus/font.c:486] 1 get_font_hfont+0x10e(graphics=0x154780, font=0x720041, hfont=0x32eb58) [dlls/gdiplus/graphics.c:2139] 2 GdipDrawString+0x2c1(graphics=0x154780, string="Bollinger Upper", length=0xf, font=0x720041, rect=0x32eba8, format=0x149e28, brush=0x154b68) [dlls/gdiplus/graphics.c:5210] 486 lf->lfHeight = -em_size_to_pixel(font->emSize, font->unit, font->family->dpi); Installing corefonts doesn't help. -- 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 23

[Bug 54813] New: Installation League of Legends crash
by WineHQ Bugzilla 16 Apr '23

16 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=54813 Bug ID: 54813 Summary: Installation League of Legends crash Product: Wine Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: totinous.31(a)hotmail.fr Distribution: --- Created attachment 74304 --> https://bugs.winehq.org/attachment.cgi?id=74304 Program Error Details Hello, I'm not fluent english, i'll try my best to explain. I tried to install and launch with the "snap method" (snap install leagueoflegends --edge --devmode) the game League of Legends. The first part is good : preparation of the environement works well, the installation as well but when the "Riot Client Main" opens, it stays black and a "Program Error" appears. i'm using wine8.5 staging. You can find the Program error details in the attachment. let me know if any further information is required to resolve that issue -- 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 12