February 2025 - Wine-Bugs - list.winehq.org

[Bug 57650] New: osu! stable: Insert key to minimize to tray does not hide game window (regression)
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=57650 Bug ID: 57650 Summary: osu! stable: Insert key to minimize to tray does not hide game window (regression) Product: Wine Version: 10.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: wine(a)horvath.blog Distribution: --- Created attachment 77786 --> https://bugs.winehq.org/attachment.cgi?id=77786 broken "x11drv,systray,event" log Regression commit: 0cda91856138e1d49fcfd9b6c2c9328146616baa From: Rémi Bernon <rbernon(a)codeweavers.com> Date: Thu, 14 Nov 2024 11:53:52 +0100 Subject: [PATCH] winex11: Request window state updates asynchronously. --- dlls/user32/tests/win.c | 7 +-- dlls/winex11.drv/event.c | 101 +++----------------------------------- dlls/winex11.drv/window.c | 41 +++++++++++----- dlls/winex11.drv/x11drv.h | 3 +- 4 files changed, 37 insertions(+), 115 deletions(-) Before this commit, pressing the insert key properly unmapped/minimized the window to the system tray. After, it still adds an icon to the tray, but the game window remains open. The tray icon can still be clicked to remove the icon as before. This problem still occurs on current Wine master (5942da6c) with minor differences, but the issue of not minimizing started with this change. I mainly use i3wm, but I get the same behavior on swaywm (with the floating dock instead). -- 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

[Bug 56658] New: When using Kosugi for vertical writing, some punctuation marks are not placed correctly.
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=56658 Bug ID: 56658 Summary: When using Kosugi for vertical writing, some punctuation marks are not placed correctly. Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: sagawa.aki+winebugs(a)gmail.com Distribution: Ubuntu Created attachment 76433 --> https://bugs.winehq.org/attachment.cgi?id=76433 Vertical writing comparison (Orange squares added for emphasis) When using Kosugi, a Japanese font designed by MOTOYA[1], for vertical writing, some punctuation marks are not placed correctly. Ume Gothic[2], another Japanese font, doesn't have this issue. See the attachment for details. Steps to Reproduce: 1. Install Kosugi font, Kosugi-Regular.ttf, to your font directory. SHA1(Kosugi-Regular.ttf) = fb02b5f57e8652a1fd499195d7070bafd58e16e2 2. Download Mery Text Editor Ver 3.7.1[3] and unzip it. SHA1(MeryPortable-3.7.1.zip) = 8355bbf8919bade31bf333731167b48cb47d9e5e 3. Launch Mery editor with Japanese locale, i.e. % LANG=ja_JP.UTF-8 wine Mery.exe 4. Choose Kosugi font in ツール(T) - オプション(O) - 表示 - フォント(F). 5. Enable vertical writing view at 表示(V) - 縦書き(V). 6. Copy and paste the following Japanese text: あのイーハトーヴォのすきとおった風、夏でも底に冷たさをもつ青いそら、うつくしい森で飾られたモリーオ市、郊外のぎらぎらひかる草の波。 Actual results: "。" and "、" are placed in the lower left hand corner of the square. See the left side of the attached image, Kosugi. Expected results: "。" and "、" are placed in the upper right hand corner of the square. See the right side of the attached image, Ume Gothic. [1] https://fonts.google.com/specimen/Kosugi [2] https://ja.osdn.net/projects/ume-font/wiki/FrontPage [3] https://www.haijin-boys.com/download/MeryPortable-3.7.1.zip -- 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 46702] New: GNUTLS_CURVE_TO_BITS not found
by wine-bugs＠winehq.org Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=46702 Bug ID: 46702 Summary: GNUTLS_CURVE_TO_BITS not found Product: Wine Version: 4.2 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Using latest gnutls3.6.6 I got compilation error ~~~ Undefined symbols for architecture i386: "_GNUTLS_CURVE_TO_BITS", referenced from: _key_asymmetric_generate in gnutls.o ld: symbol(s) not found for architecture i386 clang: error: linker command failed with exit code 1 (use -v to see invocation) winegcc: clang failed make[1]: *** [bcrypt.dll.so] Error 2 make: *** [dlls/bcrypt] Error 2 -- 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 35981] New: Battlefield: Bad Company 2 Updater has missing glyphs
by wine-bugs＠winehq.org Feb. 7, 2025

Feb. 7, 2025

http://bugs.winehq.org/show_bug.cgi?id=35981 Bug ID: 35981 Summary: Battlefield: Bad Company 2 Updater has missing glyphs Product: Wine Version: 1.7.16 Hardware: x86 OS: Linux Status: NEW Severity: trivial Priority: P2 Component: fonts Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Created attachment 48100 --> http://bugs.winehq.org/attachment.cgi?id=48100 screenshot In English game locale BFBC2Updater has a normal text, but in Russian isn't. -- 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 41342] New: Build with winegcc is not reproducible
by wine-bugs＠winehq.org Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=41342 Bug ID: 41342 Summary: Build with winegcc is not reproducible Product: Wine Version: 1.9.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: javier--fqu3sqxsVIm7PkQvPySPMwTV4r0Nxk(a)jasp.net Distribution: --- Building with winegcc is not reproducible because the name of a temporary file is included.[1] The function that creates this file should try char* tmp = strmake("%s%s", prefix, suffix); fd = open(tmp, O_CREAT | O_EXCL, 0600); before mkstemps().[2] About reproducible builds: https://reproducible-builds.org/ [1] https://tests.reproducible-builds.org/debian/dbd/unstable/i386/lmms_1.1.3-5… , look for "spec.". [2] http://source.winehq.org/git/wine.git/blob/HEAD:/tools/winegcc/winegcc.c#l2… -- 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 11

[Bug 39733] New: OpenGL Extensions Viewer 4.1 is not started
by wine-bugs＠winehq.org Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=39733 Bug ID: 39733 Summary: OpenGL Extensions Viewer 4.1 is not started Product: Wine Version: 1.8-rc2 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Infinite loop. If stop last messages are ~~~ fixme:mscoree:ConfigFileHandler_startElement Unknown element L"configSections" in state 2 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"sectionGroup" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"section" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"userSettings" in state 2 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"openglex.Properties.Settings" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"appSettings" in state 2 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"add" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"add" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"add" in state 6 fixme:gdiplus:GdipGetLineSpacing ignoring style fixme:gdiplus:GdipGetLineSpacing ignoring style fixme:gdiplus:GdipGetLineSpacing ignoring style fixme:gdiplus:GdipGetLineSpacing ignoring style -- 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 57711] New: The 32-bit wpcap program has a stack leakage issue
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=57711 Bug ID: 57711 Summary: The 32-bit wpcap program has a stack leakage issue Product: Wine Version: 10.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wpcap Assignee: wine-bugs(a)winehq.org Reporter: csumushu(a)126.com Distribution: --- Created attachment 77913 --> https://bugs.winehq.org/attachment.cgi?id=77913 test code I compiled a 32-bit wpcap application using VS2010, and when running this program with Wine, it caused a stack overflow. Therefore, I wrote a test program to print the stack address in the callback function, and I noticed that the address was gradually decreasing. This issue does not occur with the 64-bit program. The test program is included in the attachment. -- 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 57690] New: .NET Framework 4.8 installer hangs with sync:RtlpWaitForCriticalSection
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=57690 Bug ID: 57690 Summary: .NET Framework 4.8 installer hangs with sync:RtlpWaitForCriticalSection Product: Wine Version: 9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: its.kutepov(a)gmail.com Distribution: --- Hangs with the following error messages starting from 9.17 up to 10.0-rc6: ``` 033c:err:sync:RtlpWaitForCriticalSection section 7BD7A2E0 "../dlls/ntdll/loader.c: loader_section" wait timed out in thread 033c, blocked by 02a0, retrying (60 sec) ``` I tried to install using winetricks and by steps described on appdb.winehq.org. The issue is highly reproducible, I was unable to complete the installation even once. -- 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 18

[Bug 56876] New: Paint Tool SAIv2 VirtualAlloc invalid address on commit
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=56876 Bug ID: 56876 Summary: Paint Tool SAIv2 VirtualAlloc invalid address on commit Product: Wine Version: 9.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: cromachina(a)gmail.com Distribution: --- When using Paint Tool SAIv2 (any recent version, Preview.2024.05.22 for example), the program will often start emitting errors when a few files are opened and random scatter brushes are selected (brushes that open bitmap files to draw themselves). After this point, the program can quickly become unstable and inoperable, further opening of files may fail, and attempting to save files in this state may cause file corruption. I've never experienced this issue when using SAI in Windows 10, so I think it is more likely an issue within Wine than SAI itself. What I think is causing the errors: Although the errors seems to be related to files being opened, it seems to be caused by subsequent memory allocations. Checking SAI's error log, it says "!WinError(487): Invalid address." When running with WINDDEBUG=+all, I found that an invalid address error (0x000001E7, 487) is reported after the program attempts to commit a page of memory with VirtualAlloc: For this particular example, the program likely attempted to write to a reserved address 177FFF8, so then a SEH for EXCEPTION_ACCESS_VIOLATION occured. The SEH then attempted to commit 177FFF8 with VirtualAlloc, but it failed, and then GetLastError returned 000001e7 ERROR_INVALID_ADDRESS: 38822.915:0020:01b8:Call KERNEL32.VirtualAlloc(0177fff8,00001000,00001000,00000004) ret=14019f0d2 38822.915:0020:01b8:Ret KERNEL32.VirtualAlloc() retval=00000000 ret=14019f0d2 This should have been a valid address to commit, which should have returned the next lowest page, for example 177f000. The internal call to ntdll.NtAllocateVirtualMemory returned c0000019, which is STATUS_NOT_MAPPED_VIEW. Looking earlier into the log, I can confirm that the region should have indeed been reserved: 38744.422:0020:0024:Call KERNEL32.VirtualAlloc(00000000,00400000,00002000,00000004) ret=1401a0a0e 38744.422:0020:0024:Ret KERNEL32.VirtualAlloc() retval=01380000 ret=1401a0a0e This region 01380000 - 1780000 contains address 177FFF8 (8 bytes from the end of the last page). I could not find any indication that this reserved region is ever freed by VirtualFree. Therefore, I think that this may indicate that the views_tree used by find_view had become damaged somehow: https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/unix/virtual.c#L… I've compressed the massive log file, but it's still too large to attach, so I've uploaded it here: https://mega.nz/file/ET5S1LzY#WyVvta3n4QxeLjmzkyJqWmU5ZdgODWh4jILvNg32_rE -- 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 55155] New: Telegram can not be run in latest version wine, but ok in wine6.0.4
by WineHQ Bugzilla Feb. 7, 2025

Feb. 7, 2025

https://bugs.winehq.org/show_bug.cgi?id=55155 Bug ID: 55155 Summary: Telegram can not be run in latest version wine, but ok in wine6.0.4 Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 398063392(a)qq.com Distribution: --- the Telegram which I used is unpacked from https://updates.tdesktop.com/tx64/tportable-x64.4.8.3.zip -- 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 16