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

[Bug 55833] New: HeidiSQL 12.5.0.6677 crashes on start since Wine 8.17 on ArchLinux
by WineHQ Bugzilla Dec. 18, 2023

Dec. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=55833 Bug ID: 55833 Summary: HeidiSQL 12.5.0.6677 crashes on start since Wine 8.17 on ArchLinux Product: Wine Version: 8.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: clemens.ml(a)gmx.net Distribution: --- Created attachment 75330 --> https://bugs.winehq.org/attachment.cgi?id=75330 HeidiSQL Bug report output. Arch Linux (latest) Starting heidisql 12.5.0.6677 vompiled with Delphi 11 on different wine versions: wine 8.16 works fine. wine 8.17 crashes: exception message : Access violation at address 00000002FB43949D in module 'comctl32.dll'. Write of address FFFFFFFFFE1FF500. wine 8.18 crashes: exception message : Access violation at address 00006FFFFE13956D in module 'comctl32.dll'. Write of address FFFFFFFFFE1FF500. Reproducable: always I might be able to debug using gdb when I receive detailed instructions. -- 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 42

[Bug 55761] New: PLSQL Developer: Access Violation when trying to log in
by WineHQ Bugzilla Dec. 18, 2023

Dec. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=55761 Bug ID: 55761 Summary: PLSQL Developer: Access Violation when trying to log in Product: Wine Version: 8.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: robertdejager(a)tutanota.com Distribution: --- Created attachment 75249 --> https://bugs.winehq.org/attachment.cgi?id=75249 Screenshot of the error Since wine version 8.17, PL/SQL Developer throws an Access Violation exception when trying to log into a database. I have attached a screenshot with the exact error. Steps to reproduce: * Install wine 8.17 * Download Oracle Instant Client (64 bit) and unzip into your prefix in c:\ORACLE\instantclient_21_9 * Import the registry entries from the attached .reg file * Edit c:\ORACLE\instantclient_21_9\tnsnames.ora and add a connect string for a database (apologies, I cannot provide a database or a connect string for it) * Install PL/SQL Developer 14 (64 bit) (15 gives me crippling visual glitches, so I could not test) * Run PL/SQL Developer and try to log into a database Workaround: * Downgrade to wine <= 8.16 -- 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

[Bug 56011] New: regression: explorer/systray.c crash when WM_USER + 1 signal sent (eg on WM lock/unlock cycle)
by WineHQ Bugzilla Dec. 18, 2023

Dec. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=56011 Bug ID: 56011 Summary: regression: explorer/systray.c crash when WM_USER + 1 signal sent (eg on WM lock/unlock cycle) Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: explorerframe Assignee: wine-bugs(a)winehq.org Reporter: elizabeth(a)ctyalcove.org Distribution: --- Created attachment 75632 --> https://bugs.winehq.org/attachment.cgi?id=75632 screenshot showing line 574 nb_displayed error Regression introduced in 48e6bf3cf1aabdd2ac640f572416b9169e324f21, present in Wine 9.0-rc1 Assert at https://github.com/wine-mirror/wine/blob/wine-9.0-rc1/programs/explorer/sys… `assert(nb_displayed)` fails inside of WM_USER + 1 case in which hide_icon() is called by WM, while nb_displayed is not currently true. Repro case: trigger systray_atom(), for instance locking screen (causing the wine systray to hide because wine is sensitive / not allowed to appear in unity systray while locked), then unlocking screen, causing the systray event to fire and a second hide attempted while already hidden. -- 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 55747] New: The 64-bit dbghelp:dbghelp fails in Wine
by WineHQ Bugzilla Dec. 18, 2023

Dec. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=55747 Bug ID: 55747 Summary: The 64-bit dbghelp:dbghelp fails in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The 64-bit dbghelp:dbghelp fails in Wine: New Windows-on-Windows case: dbghelp.c:827: Test failed: Wrong bitness aggregation count 0 5 dbghelp.c:829: Test failed: Wrong kind aggregation count 0 1 dbghelp.c:831: Test failed: Wrong directory aggregation count 5 0 dbghelp.c:889: Test failed: Wrong kind aggregation count 1 2 dbghelp.c:1213: Test failed: [64/32 enum:+32bit wow64]: Unexpected enum.count_exe 1 dbghelp.c:1337: Test failed: [64/32 enum:+32bit wow64]: Different sym/enum count32_bit (23/23) dbghelp.c:1343: Test failed: [64/32 enum:+32bit wow64]: Different sym/enum wowdir (22/22) dbghelp.c:1345: Test failed: [64/32 enum:+32bit wow64]: Different sym/enum exe (1/1) dbghelp.c:1213: Test failed: [64/32 enum:default wow64]: Unexpected enum.count_exe 0 dbghelp.c:1217: Test failed: [64/32 enum:default wow64]: Unexpected enum.count_32bit 0 dbghelp.c:1223: Test failed: [64/32 enum:default wow64]: Unexpected enum.count_wowdir 0 dbghelp.c:1226: Test failed: [64/32 enum:default wow64]: Unexpected sym.count_exe 0 dbghelp.c:1230: Test failed: [64/32 enum:default wow64]: Unexpected sym.count_32bit 0 dbghelp.c:1236: Test failed: [64/32 enum:default wow64]: Unexpected sym.count_wowdir 0 Old Windows-on-Windows case: dbghelp.c:818: Test failed: Wrong bitness aggregation count 0 1 dbghelp.c:820: Test failed: Wrong kind aggregation count 0 1 dbghelp.c:822: Test failed: Wrong directory aggregation count 1 0 dbghelp.c:671: Test failed: C:\windows\syswow64\ntdll.dll shouldn't already be loaded dbghelp.c:878: Test failed: Wrong bitness aggregation count 22 2 dbghelp.c:880: Test failed: Wrong kind aggregation count 1 2 dbghelp.c:882: Test failed: Wrong directory aggregation count 1 22 dbghelp.c:1278: Test failed: [64/32 enum:+32bit wine_old_wow64]: Unexpected enum.count_exe 1 dbghelp.c:1284: Test failed: [64/32 enum:+32bit wine_old_wow64]: Unexpected enum.count_systemdir 1 dbghelp.c:1289: Test failed: [64/32 enum:+32bit wine_old_wow64]: Unexpected enum.count_ntdll 2 dbghelp.c:1296: Test failed: [64/32 enum:+32bit wine_old_wow64]: Unexpected sym.count_64bit 1 dbghelp.c:1297: Test failed: [64/32 enum:+32bit wine_old_wow64]: Unexpected sym.count_systemdir 1 dbghelp.c:1337: Test failed: [64/32 enum:+32bit wine_old_wow64]: Different sym/enum count32_bit (22/24) dbghelp.c:1339: Test failed: [64/32 enum:+32bit wine_old_wow64]: Different sym/enum count64_bit (1/0) dbghelp.c:1345: Test failed: [64/32 enum:+32bit wine_old_wow64]: Different sym/enum exe (1/1) dbghelp.c:1347: Test failed: [64/32 enum:+32bit wine_old_wow64]: Different sym/enum exe (1/2) dbghelp.c:1278: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected enum.count_exe 0 dbghelp.c:1284: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected enum.count_systemdir 1 dbghelp.c:1289: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected enum.count_ntdll 1 dbghelp.c:1291: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected sym.count_exe 0 dbghelp.c:1296: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected sym.count_64bit 1 dbghelp.c:1297: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected sym.count_systemdir 1 dbghelp.c:1302: Test failed: [64/32 enum:default wine_old_wow64]: Unexpected sym.count_ntdll 1 dbghelp.c:1337: Test failed: [64/32 enum:default wine_old_wow64]: Different sym/enum count32_bit (0/1) dbghelp.c:1339: Test failed: [64/32 enum:default wine_old_wow64]: Different sym/enum count64_bit (1/0) See https://test.winehq.org/data/patterns.html#dbghelp:dbghelp A bisect shows that this started with the commit below: commit de81e2ea41b27a14f88177639c5b5d35a210b5bd Author: Alexandre Julliard <julliard(a)winehq.org> Date: Fri Oct 6 15:08:02 2023 +0200 ntdll: Only create the main module on the 32-bit side for wow64. This means this most likely has the same fix as bug 55744. -- 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 55976] New: Battle.net stopped working after update pushed from server
by WineHQ Bugzilla Dec. 18, 2023

Dec. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=55976 Bug ID: 55976 Summary: Battle.net stopped working after update pushed from server Product: Wine Version: 8.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joshudson(a)gmail.com Distribution: --- Created attachment 75564 --> https://bugs.winehq.org/attachment.cgi?id=75564 Process state when it crashed Battle.net dies on startup; worked until 11/30/23 -- 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 55960] New: user32: 512 is not enough for LB_ADDSTRING
by WineHQ Bugzilla Dec. 18, 2023

Dec. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=55960 Bug ID: 55960 Summary: user32: 512 is not enough for LB_ADDSTRING Product: Wine Version: 8.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- So, as noted in bug 54034, while dealing with some out-of-memory crashes, I ran into an odd one, one that could be triggered even shortly after reload and acting more like a buffer overflow bug. Namely, if a certain string that was about to be displayed on the screen was above 530 chars (but it had newline embedded), the game crashed, but didn't if the string was manually truncated. It left me grasping at straws, as my (quite lacking) gdb skills didn't lets me see where the crash occurred. So, I was left waiting for some burst of inspiration. It came today. For some reason, this felt like I had been hitting some internal limit. I suspected wine code. After trying a few debug channel combinations, I eventually tested 'msg'. The strings were printed using ID3DXFontImpl_DrawTextA. In the log, I've noted LB_ADDSTRING and - after looking at that code - took a stab in the dark. I've set the buffer size for that message in both WINPROC_CallProcAtoW and WINPROC_CallProcWtoA to 1536 (yes, likely excessively large). Making this change has fixed the crash. I'm marking it wine 8.21, but I expect this has been around as long as wine has been using too small buffer. -- 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 55511] New: Wine repeatedly prints err:system:update_display_cache Failed to read display config.
by WineHQ Bugzilla Dec. 18, 2023

Dec. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=55511 Bug ID: 55511 Summary: Wine repeatedly prints err:system:update_display_cache Failed to read display config. Product: Wine Version: 8.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: m101010a(a)gmail.com Distribution: --- In sysparams.c the read_display_adapter_settings function uses the global variable config_key, but does not actually initialize it. This causes the function to fail, and that failure eventually trickles down to update_display_cache. I haven't seen any functionality break because of it, but the messages are annoying and could be trivially fixed by initializing config_key before it is used. -- 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 55014] New: kernel32:comm crashes in WoW64 mode on Linux
by WineHQ Bugzilla Dec. 18, 2023

Dec. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=55014 Bug ID: 55014 Summary: kernel32:comm crashes in WoW64 mode on Linux Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- kernel32:comm crashes in WoW64 mode on Linux: comm.c:708: Found Com port COM1. Connected devices may disturb results Unhandled exception: page fault on read access to 0x0000000000000000 in 64-bit code (0x007f47b448083c). [...] =>0 0x007f47b448083c wait_for_event+0x1c(arg=<internal error>) [/home/winetest/tools/testbot/var/wine-wow64/../wine/dlls/ntdll/unix/serial.c:945] in ntdll.so (0000000000000000) 0x007f47b448083c wait_for_event+0x1c [/home/winetest/tools/testbot/var/wine-wow64/../wine/dlls/ntdll/unix/serial.c:945] in ntdll.so: mov (%rdi), %rdi 945 if (!server_get_unix_fd( commio->hDevice, FILE_READ_DATA | FILE_WRITE_DATA, &fd, &needs_close, NULL, NULL )) See https://test.winehq.org/data/patterns.html#kernel32:comm The failure seems to only happen on the TestBot VMs, maybe because of QEmu, particularly because it does not set the baud rate correctly. A bisect shows that this failure started with the commit below: commit b337c5b1a1757b2abbc90a7c6955d64242861ab9 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Fri Jun 2 09:35:29 2023 +0200 ntdll: Use the default ABI for all functions on the Unix side. -- 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 45305] New: [AZERTY Keyboard] Certains special keys are not correctly recognized.
by wine-bugs＠winehq.org Dec. 18, 2023

Dec. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=45305 Bug ID: 45305 Summary: [AZERTY Keyboard]Certains special keys are not correctly recognized. Product: Wine Version: 3.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Hello, I have a problem when i want to use special character with my French Keyboard. If i use "é", "è", "ç" and "à" keys in winecfg, regedit or notepad, these symbols are correctly write. But in game/all games, if i use these keys, the game does not recognize it. Example for Vampyr, "é" symbol is used by default for an action. If i want to use "é" for an other action, when i press the key on my keybaord, there is no effect, the key is not recognized. I have this problem even if i export LC_ALL=fr_FR before to launch Steam. If someone had this issue in the past and fix this problem, i'll say him thanks 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 3

[Bug 54616] New: Wine 8.0+, Memory Access Violation in Libaes.dll, Texecom Wintex
by WineHQ Bugzilla Dec. 17, 2023

Dec. 17, 2023

https://bugs.winehq.org/show_bug.cgi?id=54616 Bug ID: 54616 Summary: Wine 8.0+, Memory Access Violation in Libaes.dll, Texecom Wintex 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: zestier-bib.0a(a)icloud.com Distribution: --- Created attachment 74142 --> https://bugs.winehq.org/attachment.cgi?id=74142 Error from console when Program is run. When attempting to run running Texecom Wintex in Wine 8.0 or above, there is a Memory Access Violation/Buffer Overrun error c0000005 in libaes.dll. Downgrading to Wine 7.0.1 with no other changes allows the program to run normally. The environment has C++ Redistributable 2010 installed as required. There is no GUI errors shown when the issue is present. The attached .txt file contains the error that is printed when the program is run via the console. libaes.dll seems to be specific to this program. The program can be downloaded from here: https://texecom-live.s3.eu-west-2.amazonaws.com/wp-content/uploads/2022/08/… (no account required) or https://www.texe.com/help-and-support/product-support/ (free account required) No accounts or hardware is needed to run the software. See also: My forum post: https://forum.winehq.org/viewtopic.php?p=139794#p139794 If I can provide any more information, please let me know. -- 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