November 2022 - Wine-Bugs - list.winehq.org

[Bug 52790] New: winedbg 'bt all' filled with dbghelp_dwarf fixmes
by WineHQ Bugzilla Nov. 2, 2022

Nov. 2, 2022

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 48197] New: Autonauts in steam under wine has a memory leak.
by WineHQ Bugzilla Nov. 2, 2022

Nov. 2, 2022

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 47595] New: Tequila City of Heroes Launcher - expect_no_runtimes Process exited with a Mono runtime loaded.
by wine-bugs＠winehq.org Nov. 2, 2022

Nov. 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=47595 Bug ID: 47595 Summary: Tequila City of Heroes Launcher - expect_no_runtimes Process exited with a Mono runtime loaded. Product: Wine Version: 4.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 65009 --> https://bugs.winehq.org/attachment.cgi?id=65009 Console output - wine 4.11 (staging) Hello everyone, "Tequila" is a launcher for the abandoned game "City of Heroes". It starts up okay, downloads some stuff but terminates. Console output is 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.

2 5

[Bug 38594] New: dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols (Visual C++ 2013 .pdb's)
by wine-bugs＠winehq.org Nov. 2, 2022

Nov. 2, 2022

https://bugs.winehq.org/show_bug.cgi?id=38594 Bug ID: 38594 Summary: dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols (Visual C++ 2013 .pdb's) Product: Wine Version: 1.7.43 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: --- Created attachment 51493 --> https://bugs.winehq.org/attachment.cgi?id=51493 terminal output in wine-1.7.43 Now that we have pdb's for wine_gecko (see bug 36941), I tried running valgrind with gecko 2.36. The atl100/tests/atl.c test shows a lot of issues with unknown symbols, eventually getting a page fault, e.g.,: fixme:dbghelp_msc:codeview_fetch_type Cannot locate type 103 fixme:dbghelp_msc:codeview_get_type Returning NULL symt for type-id 103 fixme:dbghelp_msc:codeview_snarf S-Udt nullptr_t: couldn't find type 0x103 fixme:dbghelp_msc:codeview_snarf S-Udt NullptrT: couldn't find type 0x103 fixme:dbghelp_msc:codeview_snarf Unsupported symbol id 114c fixme:dbghelp_msc:codeview_add_type_enum_field_list Unsupported type 1404 in ENUM field list fixme:dbghelp_msc:numeric_leaf Unsupported numeric leaf type 8009 fixme:dbghelp_msc:numeric_leaf Unsupported numeric leaf type 800a ... err:dbghelp_msc:pe_load_debug_directory Got a page fault while loading symbols full output 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.

2 2

[Bug 29998] New: Crysis 2 (>1.0) huge graphical issues after loading a savegame
by wine-bugs＠winehq.org Nov. 2, 2022

Nov. 2, 2022

http://bugs.winehq.org/show_bug.cgi?id=29998 Bug #: 29998 Summary: Crysis 2 (>1.0) huge graphical issues after loading a savegame Product: Wine Version: 1.4-rc5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: christian.frank(a)gmx.de Classification: Unclassified Created attachment 39060 --> http://bugs.winehq.org/attachment.cgi?id=39060 Crysis 2 log Hi, if you try to use a saved game in Crysis 2 which is patched to a higher level than 1.0, you will have huge graphical issues. Either you get a black scree with only the hud displayed, or completely broken graphics, or a whiet screen etc.. This does only happen if you use a savegame or if you want to replay a mission. If you start the campaign from the beginning, the game will look fine. This behaviour happens with tons of wine version i have testet, so doesnt seem to be a regression right now. CryEngine 3 is planned to be used in other upcoming games and is somehow a engine which really pushes d3d9 to its limits.I think it would make a lot of sense to get this issue fixed . Many thanks, Christian -- 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 55

[Bug 53829] New: Font links for MingLiU broken 32-bit wineprefixes
by WineHQ Bugzilla Nov. 2, 2022

Nov. 2, 2022

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 50573] New: division by zero in wineconsole when hovering mouse over
by WineHQ Bugzilla Nov. 2, 2022

Nov. 2, 2022

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 Nov. 2, 2022

Nov. 2, 2022

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 Nov. 2, 2022

Nov. 2, 2022

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 Nov. 2, 2022

Nov. 2, 2022

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