October 2022 - Wine-bugs - list.winehq.org

[Bug 52790] New: winedbg 'bt all' filled with dbghelp_dwarf fixmes
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=52790 Bug ID: 52790 Summary: winedbg 'bt all' filled with dbghelp_dwarf fixmes Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: NEW Keywords: download, regression, source Severity: normal Priority: P2 Component: winedbg Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian First, run any wine app $ wine notepad Then, try to run `bt all`: austin(a)hyrule:~$ echo "bt all" | winedbg Wine-dbg>02d4:fixme:dbghelp_dwarf:dwarf2_read_range no entry found RtlDefaultNpAcl () at Z:\home\austin\wine-git\dlls\ntdll\sec.c:1731 0x7bc53821 ntdll+0x53821 [Z:\home\austin\wine-git\dlls\ntdll\sec.c:1731]: ret 1731 } Backtracing for thread 0024 in process 0020 (C:\windows\system32\start.exe): Backtrace: =>0 0x7bc0be6c CsrAllocateCaptureBuffer+0xae6c() in ntdll (0x0031fd58) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 1 0x7b073b7e WaitForSingleObject+0x39(handle=<internal error>, timeout=<internal error>) [Z:\home\austin\wine-git\dlls\kernelbase\sync.c:334] in kernelbase (0x0031fd98) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 02d4:fixme:dbghelp_dwarf:compute_call_frame_cfa Too complex expression for frame_CFA resolution (RULE_VAL_EXPRESSION) 2 0x00402804 wmain+0xa14(argc=<internal error>, argv=<internal error>) [Z:\home\austin\wine-git\programs\start\start.c:701] in start (0x0031fef8) 3 0x004038d8 wmainCRTStartup+0x68() [Z:\home\austin\wine-git\dlls\msvcrt\crt_wmain.c:60] in start (0x0031ff30) 4 0x7b62d310 WriteTapemark+0x100(device=7FFD1000, type=<is not available>, count=<is not available>, immediate=<is not available>) [Z:\home\austin\wine-git\dlls\kernel32\tape.c:317] in ker nel32 (0x0031ff48) 5 0x7bc58ca7 RtlWakeConditionVariable+0x57(variable=7B62D300) [Z:\home\austin\wine-git\dlls\ntdll\sync.c:757] in ntdll (0x0031ff5c) 6 0x7bc59360 RtlCreateUserThread(entry=00403870, arg=7FFD1000) [Z:\home\austin\wine-git\dlls\ntdll\thread.c:261] in ntdll (0x0031ffec) 02d4:fixme:dbghelp_dwarf:dwarf2_read_range no entry found 0x7bc53821 ntdll+0x53821 [Z:\home\austin\wine-git\dlls\ntdll\sec.c:1731]: ret 1731 } with WINEDEBUG=-all, it's much more readable: Backtracing for thread 0024 in process 0020 (C:\windows\system32\start.exe): Backtrace: =>0 0x7bc0be6c CsrAllocateCaptureBuffer+0xae6c() in ntdll (0x0031fd58) 1 0x7b073b7e WaitForSingleObject+0x39(handle=<internal error>, timeout=<internal error>) [Z:\home\austin\wine-git\dlls\kernelbase\sync.c:334] in kernelbase (0x0031fd98) 2 0x00402804 wmain+0xa14(argc=<internal error>, argv=<internal error>) [Z:\home\austin\wine-git\programs\start\start.c:701] in start (0x0031fef8) 3 0x004038d8 wmainCRTStartup+0x68() [Z:\home\austin\wine-git\dlls\msvcrt\crt_wmain.c:60] in start (0x0031ff30) 4 0x7b62d310 WriteTapemark+0x100(device=7FFD1000, type=<is not available>, count=<is not available>, immediate=<is not available>) [Z:\home\austin\wine-git\dlls\kernel32\tape.c:317] in ker nel32 (0x0031ff48) 5 0x7bc58ca7 RtlWakeConditionVariable+0x57(variable=7B62D300) [Z:\home\austin\wine-git\dlls\ntdll\sync.c:757] in ntdll (0x0031ff5c) 6 0x7bc59360 RtlCreateUserThread(entry=00403870, arg=7FFD1000) [Z:\home\austin\wine-git\dlls\ntdll\thread.c:261] in ntdll (0x0031ffec) 0x7bc53821 ntdll+0x53821 [Z:\home\austin\wine-git\dlls\ntdll\sec.c:1731]: ret 1731 } -- 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 13

[Bug 53838] New: Non-PE builds fail after "makedep: Make the installation directories architecture-generic."
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=53838 Bug ID: 53838 Summary: Non-PE builds fail after "makedep: Make the installation directories architecture-generic." Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: martin(a)martin.st CC: julliard(a)winehq.org Regression SHA1: 9795a01918185435f7d9a34806327ef9bf109e6a Distribution: --- After 9795a01918185435f7d9a34806327ef9bf109e6a, "makedep: Make the installation directories architecture-generic.", non-PE (--without-mingw) fail. Previously for such builds, the <prefix>/lib/wine/<arch>-windows directory contained the small stub .dll/.exe files - now they are all installed along with the .so files in the <arch>-unix directory. -- 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 53829] New: Font links for MingLiU broken 32-bit wineprefixes
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=53829 Bug ID: 53829 Summary: Font links for MingLiU broken 32-bit wineprefixes Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: blocker Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Wine fails to create (non-WoW) 32-bit wineprefixes: 0024:err:environ:run_wineboot boot event wait timed out wine: could not load kernel32.dll, status c0000135 A bisect shows the issue started with this commit: commit edecac8afdd04701314381b6386e0f7ac862e066 Author: Ziqing Hui <zhui(a)codeweavers.com> Date: Tue Oct 18 13:38:56 2022 +0800 win32u: Add font links for MingLiU. As was reported by the TestBot: https://gitlab.winehq.org/wine/wine/-/merge_requests/1089 Reverting this commit fixes the 32-bit wineprefix creation. -- 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 53521] New: imm32:imm32 - test_default_ime_window_creation() fails on Windows 10 21H1+
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=53521 Bug ID: 53521 Summary: imm32:imm32 - test_default_ime_window_creation() fails on Windows 10 21H1+ Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: imm32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com imm32:imm32 - test_default_ime_window_creation() fails on Windows 10 21H1+: imm32.c:1427: Test failed: Expected IME window existence https://test.winehq.org/data/patterns.html#imm32:imm32 This failure is systematic and this check was introduced in: commit 716e9c93e4a2a0574e0028d428eb087574d8d843 Author: Akihiro Sagawa <sagawa.aki(a)gmail.com> AuthorDate: Fri Sep 2 21:55:37 2016 +0900 imm32/tests: Add more default IME window tests with message-only window. Signed-off-by: Akihiro Sagawa <sagawa.aki(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 6

[Bug 48197] New: Autonauts in steam under wine has a memory leak.
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=48197 Bug ID: 48197 Summary: Autonauts in steam under wine has a memory leak. Product: Wine Version: 4.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: eeknaak(a)gmail.com Distribution: --- Created attachment 65834 --> https://bugs.winehq.org/attachment.cgi?id=65834 Hard_info report Running Autonauts.exe under wine 4.20 has a constant memory leak. Running it native on windows doesn't have a leak. https://github.com/EricKnaak/computerfacts/blob/master/pc%20specs OS: Ubuntu 18.04 wine: 4.20 steam for linux: Built: Nov 20 2019, at 01:49:33 Autonauts.exe won't run in valgrind due to lack of support of IRET/IRETD — Interrupt Return. I learned about Valgrind and how to compile again. I don't see anything I can do to gather any more info on this problem. -- 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 50573] New: division by zero in wineconsole when hovering mouse over
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=50573 Bug ID: 50573 Summary: division by zero in wineconsole when hovering mouse over Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: magiblot(a)hotmail.com Distribution: --- Created attachment 69247 --> https://bugs.winehq.org/attachment.cgi?id=69247 Demo application to reproduce the issue This bug can be reproduced with the same application provided in bug 49780, which I am attaching again to this issue. When launching the application, you will not see anything because wineconsole does not support VT sequences (see bug 49780). However, when hovering the mouse over wineconsole, it will crash because of a division by zero. 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.

1 5

[Bug 53855] New: V Rising everything is blue graphical glitch (texture issue)
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=53855 Bug ID: 53855 Summary: V Rising everything is blue graphical glitch (texture issue) Product: Wine Version: 7.19 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 73382 --> https://bugs.winehq.org/attachment.cgi?id=73382 V Rising - Wine-staging 7.19 - Default terminal output Hello, I tested V Rising while it was free on Steam (https://store.steampowered.com/app/1604030/V_Rising/) The main issue (this bug) is that everything is plain blue. It looks like a texture related issue. There is also a memory consumption issue. The minimum memory requirements is 12GB but the game consumes more than that. I have 16GB of memory but it's filled quickly and multiple GB of swap space are used. This doesn't prevent the game from working though. It just makes it slow to load. Debian 8 jessie Intel® Core™ i7-4930K CPU @ 3.40GHz × 12 NVIDIA GeForce RTX 2070/PCIe/SSE2 (8GB VRAM - proprietary driver 515.57) 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.

1 5

[Bug 53853] New: loader/wine.inf.in Unable to enter Chinese as Nombre when create regedit
by WineHQ Bugzilla 31 Oct '22

31 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=53853 Bug ID: 53853 Summary: loader/wine.inf.in Unable to enter Chinese as Nombre when create regedit Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Distribution: --- I know that we can modify wine.inf.in according to the format of the .inf file, so that wine will write the corresponding content into the registry when it starts. such as: > HKLM,%FontSubStr%,"MS Shell Dlg 2",,"Tahoma" But when I type Chinese in this file, the Chinese cannot be imported into the registry very well, instead it becomes garbled characters such as: > HKLM,%FontSubStr%,"宋体",,"Tahoma" After starting wine, the corresponding position will become garbled. instead of Chinese "宋体" -- 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 53852] New: Launching wine resets DualShock 4 LED to default blue
by WineHQ Bugzilla 30 Oct '22

30 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=53852 Bug ID: 53852 Summary: Launching wine resets DualShock 4 LED to default blue Product: Wine Version: 7.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: andysem(a)mail.ru Distribution: --- Launching any application under wine (e.g. winecfg) resets DualShock 4 LED to the default light blue light. Happens every time. The gamepad is connected over Bluetooth and its LED is disabled upon connecting by my udev rules, so wine is constantly breaking my configuration. Steps to reproduce: 1. Connect DualShock 4 over Bluetooth. 2. Turn off the LED by "for f in /sys/bus/hid/devices/0005:054C:05C4.000D/leds/*; do echo 0 > $f/brightness; done". Here, 0005:054C:05C4.000D is the gamepad device id. 3. Run "wine winecfg". This is on Kubuntu 22.04, Linux kernel 5.15.0-52-lowlatency. Interestingly, even after running wine, all the "brightness" files still report 0. It looks like wine is somehow resetting the controller LED to the default state without writing to these control files. In order to turn the LED off again after that one has to write a non-zero value to the brightness files first, and then zero again. -- 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 53851] New: wrong symbols for close, Minimize and Maximize in titlebar buttons and system menus
by WineHQ Bugzilla 30 Oct '22

30 Oct '22

https://bugs.winehq.org/show_bug.cgi?id=53851 Bug ID: 53851 Summary: wrong symbols for close, Minimize and Maximize in titlebar buttons and system menus Product: Wine Version: 6.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bastien.blanchon(a)gmail.com Distribution: --- On Linux mint 22 "vanessa" (mate desktop+wm) wine 6.03 the buttons in use for the windows size handling options are incorrect on - windows menu - modal sub windows titlebars - application titlebars when using "virtual desktop" mode square instead of cross for "close" 1 instead of the maximize symbol for maximize, idem with 2 for "restore" and 0 for minimize please note that the following packages are installed - ms core fonts (in text mode so as not to miss the license validation) - wine fonts - tahoma font was installed with wintricks, without result this issue seems similar to what happens when when wine font is not installed, so should just be an font issue No Bug relate dto this issue con be found on linux mint or ubuntu forum -- 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