wine-bugs September 2021

wine-bugs@winehq.org

1 participants
4513 discussions

[Bug 51757] New: Network application crashes
by WineHQ Bugzilla 24 Sep '21

24 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51757 Bug ID: 51757 Summary: Network application crashes Product: Wine Version: 6.17 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: dmitry(a)baikal.ru CC: z.figura12(a)gmail.com Regression SHA1: 1ee382c706bed683e7263c867fd6599dd6920103 Distribution: --- Created attachment 70653 --> https://bugs.winehq.org/attachment.cgi?id=70653 +winsock,+server,+seh,+tid log of the crashing thread This is a recent regression, wine-6.17 works fine: commit 1ee382c706bed683e7263c867fd6599dd6920103 Author: Zebediah Figura <zfigura(a)codeweavers.com> Date: Tue Sep 14 01:02:43 2021 -0500 server: Pass the async result size as part of apc_call_t. Only really an optimization (plus it makes the code a little conceptually simpler). Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> I'm attaching a +winsock,+server,+seh,+tid log of the crashing thread, please let me know if you need full log. -- 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 51723] New: Timespinner controller triggers aren't properly recognized
by WineHQ Bugzilla 24 Sep '21

24 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51723 Bug ID: 51723 Summary: Timespinner controller triggers aren't properly recognized Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vlund(a)codeweavers.com Distribution: --- Created attachment 70605 --> https://bugs.winehq.org/attachment.cgi?id=70605 Terminal Output Timespinner had an update that updated the FNA Framework from 19.05 to 21.08. Since then the trigger buttons on controllers are not working. In the Player Settings options menu Left trigger and Right trigger are reported as the opposite ones when pressed, and in game neither button actually does anything. All other buttons seem to working fine. This happens with both Xbox and PS4 controllers. -- 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 51696] New: ntoskrnl.exe:ntoskrnl outputs too much traces (and broke the Wine tests entirely)
by WineHQ Bugzilla 24 Sep '21

24 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51696 Bug ID: 51696 Summary: ntoskrnl.exe:ntoskrnl outputs too much traces (and broke the Wine tests entirely) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- ntoskrnl.exe:ntoskrnl outputs more than 200kB of traces: $ ./wine dlls/ntoskrnl.exe/tests/ntoskrnl.exe_test.exe ntoskrnl >ntoskrnl.report $ tail -n3 ntoskrnl.report 0270:ntoskrnl: 96 tests executed (1 marked as todo, 0 failures), 0 skipped. 0020:ntoskrnl: Silenced 5475 todos, 0 skips and 0 traces. 0020:ntoskrnl: 21296 tests executed (1967 marked as todo, 0 failures), 0 skipped. $ ls -l ntoskrnl.report -rw-r--r-- 1 fgouget fgouget 208428 août 28 18:37 ntoskrnl.report $ grep "Test marked todo:" ntoskrnl.report | wc -cl 1994 204531 This is not a problem of a runaway test or even that many trace() statements. It's just that there are too many todos despite the vast majority being silenced already. The big issue is that adding so much data to a full Winetest run pushes it over the 1.5MB limit (before and after debiant2 WineTest reports): -rw-r--r-- 1 fgouget fgouget 1477298 août 28 20:27 /tmp/job96432_1_1_win32.report -rw-r--r-- 1 fgouget fgouget 1689913 août 28 20:24 /tmp/job96543_1_1_win32.report The commit that introduced the extra todos is: commit 8d37962b43e5074bc0421611267dc41593114f85 Author: Zebediah Figura <zfigura(a)codeweavers.com> AuthorDate: Thu Aug 26 20:54:10 2021 -0500 ntoskrnl/tests: Add more tests for IRP status handling. Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Also the TestBot warned about this issue when the patch was submitted, though that did not carry over to sending an email to wine-devel or marking the patch as failed on the patches website (bug 51695). https://testbot.winehq.org/JobDetails.pl?Key=96439#k401 -- 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 51596] New: Unhandled exception code c0000005 when running any 64-bit Winelib application
by WineHQ Bugzilla 24 Sep '21

24 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51596 Bug ID: 51596 Summary: Unhandled exception code c0000005 when running any 64-bit Winelib application Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winelib Assignee: wine-bugs(a)winehq.org Reporter: mail(a)robbertvanderhelm.nl Distribution: ArchLinux Somewhere after Wine 6.14, 64-bit Winelib applications are no longer able to start when Wine is compiled with optimizations. Everything still works just fine when setting {C,CXX,CROSSC}FLAGS to "-g -O0", and 32-bit Winelib applications also still work fine. I haven't tested which exact commit introduced this issue, but it at least happens after f63ecaedc72f3580e7016ba71a480025e4d86e99 To reproduce this issue, create a main.cpp file with the following contents and then compile it with `wineg++ -o main main.cpp -mwindows -m64`: #include <iostream> int main() { std::cout << "Hello, world!" << std::endl; } Running main.exe with these versions of the latest master branch version of Wine Staging (wine-6.14-323-g91494ae6f2e right now) prints the following: 0144:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr 0x7bc2dc17 Doing the same thing with a 32-bit Winelib (i.e. with -m32) works just fine, and the 64-bit version also works fine when compiling Wine the following configuration: CC='ccache gcc' CXX='ccache g++' CROSSCC='ccache x86_64-w64-mingw32-gcc' CFLAGS="-g -O0" CXXFLAGS="-g -O0" CROSSCFLAGS="-g -O0" ../configure --disable-tests --enable-win64 Leaving out those flags brings back the error, so there's likely some kind of UB at play here. -- 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 48442] New: MPGUI crash on start in MSVCRT__wctomb_s_l in msvcr100
by WineHQ Bugzilla 24 Sep '21

24 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=48442 Bug ID: 48442 Summary: MPGUI crash on start in MSVCRT__wctomb_s_l in msvcr100 Product: Wine Version: 5.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Distribution: --- Created attachment 66220 --> https://bugs.winehq.org/attachment.cgi?id=66220 stacktrace Hi, MPGUI (a C++/CLI application, so C++ app that use the .NET runtime )crash on start with a Unhandled exception: page fault on read access to 0x00000020 in 32-bit code (0x7c6e61a0). PArt of the stacktrace: 0 0x7c6e61a0 MSVCRT__wctomb_s_l+0x1180() in msvcr100 (0x0032f378) 1 0x7c6e87f0 MSVCRT_vsnprintf+0x3f() in msvcr100 (0x0032f3c8) 2 0x7c6e8952 MSVCRT_sprintf_s+0x21() in msvcr100 (0x0032f3f8) 0x7c6e61a0 MSVCRT__wctomb_s_l+0x1180 in msvcr100: movzbl 0x0(%edi),%eax This part of the stacktrace suggest that native dotnet may be a workaround: 10 0x6c54c5ee mono_jit_runtime_invoke+0x46d(exc=<is not available>) [Z:\vagrant\mono\mono\mini\mini-runtime.c:3184] in libmono-2.0-x86 (0x005f6b48) 11 0x6c71da32 object_new_handle_common_tail+0x1d1(o=<is not available>, klass=<is not available>, error=<is not available>) [Z:\vagrant\mono\mono\metadata\object.c:3029] in libmono-2.0-x86 (0x00000000) 12 0x6c722105 mono_runtime_object_init+0xd4() [Z:\vagrant\mono\mono\metadata\object.c:5151] in libmono-2.0-x86 (0x00000000) 13 0x6c5a3372 mono_jit_exec+0x191() [Z:\vagrant\mono\mono\mini\driver.c:1325] Full stacktrace attached. Prefix is new. 32bit Wine Log is empty. -- 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 19

[Bug 51729] New: Unable to find an entry point named 'UiaDisconnectProvider' in DLL 'UIAutomationCore.dll'
by WineHQ Bugzilla 24 Sep '21

24 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51729 Bug ID: 51729 Summary: Unable to find an entry point named 'UiaDisconnectProvider' in DLL 'UIAutomationCore.dll' Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uiautomationcore Assignee: wine-bugs(a)winehq.org Reporter: pashtet92(a)bk.ru Distribution: --- Created attachment 70615 --> https://bugs.winehq.org/attachment.cgi?id=70615 wine logs Hello. I tried to use a .NET 5 application written using WinForms: https://github.com/Greavesy1899/MafiaToolkit After I close the intro window, this exception happens: System.EntryPointNotFoundException: Unable to find an entry point named 'UiaDisconnectProvider' in DLL 'UIAutomationCore.dll'. at Interop.UiaCore.UiaDisconnectProvider(IRawElementProviderSimple provider) at System.Windows.Forms.Control.ReleaseUiaProvider(IntPtr handle) at System.Windows.Forms.Control.WmDestroy(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, WM msg, IntPtr wparam, IntPtr lparam) Apparently, it tries to unregister a UI Automation provider on window destruction. MSDN docs: https://docs.microsoft.com/ru-ru/windows/win32/api/uiautomationcoreapi/nf-u… Since current uia_core implementation is largely stub, I think it might benefit from one more stub ;) -- 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 50623] New: Windows ISO Downloader 8.45 - Error messages and freeze with wine-mono
by WineHQ Bugzilla 24 Sep '21

24 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=50623 Bug ID: 50623 Summary: Windows ISO Downloader 8.45 - Error messages and freeze with wine-mono Product: Wine Version: 6.1 Hardware: x86-64 URL: https://web.archive.org/web/20210128040613/https://www .heidoc.net/php/Windows-ISO-Downloader.exe OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: winetaste(a)gmx.net Distribution: --- Created attachment 69317 --> https://bugs.winehq.org/attachment.cgi?id=69317 Unhandled exceptions Starting Windows ISO Downloader 8.45* I get an error message about an unhandled exception. I can continue, but selecting a Windows version (except "Windows 7 (August 2018)" and "DELL") results in another exception and the app freezes if I select the continue button. winetricks dotnet40 fixes start up exception. App needs ie8 then. Winetricks ie8 fixes this and I can select "Windows 7". Other versions like "Windows 10" just freeze without exception window. *https://www.heidoc.net/joomla/technology-science/microsoft/67-microsoft-windows-and-office-iso-download-tool -- 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 17

[Bug 50089] New: Far Manager 2.0 crashes on start-up
by WineHQ Bugzilla 24 Sep '21

24 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=50089 Bug ID: 50089 Summary: Far Manager 2.0 crashes on start-up Product: Wine Version: 5.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 68554 --> https://bugs.winehq.org/attachment.cgi?id=68554 backtrace Steps to reproduce: Install https://www.farmanager.com/history/far2.x86.msi SHA256: a96df17ca77c2bb817ca4e0f9cef9408d6cbd6b74c5d336c83961be5a92067f4 Run it: wine wineconsole Far.exe -- 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 51741] New: Nt*PowerRequest syscalls do not exist on real Windows
by WineHQ Bugzilla 24 Sep '21

24 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51741 Bug ID: 51741 Summary: Nt*PowerRequest syscalls do not exist on real Windows Product: Wine Version: 4.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: cdavis5x(a)gmail.com Distribution: --- In ca2b7012496c4a97d7c03bc34b388592fd1157f5, I added stub system calls corresponding to the kernel32 power request API. These syscalls do not exist on real Windows. Based on my reading of the headers, what we need to use instead is NtPowerInformation() with the selectors 'PowerRequestCreate' and 'PowerRequestAction'. However, I have no idea what the I/O structs for those functions look like. Before this can be fixed, we'll need to get the definitions of these structures somehow. -- 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 50498] New: Intel Assistive Context-Aware Toolkit (ACAT) v1.00.0 (.NET 4.5 app) setup exits with System.MissingMethodException
by WineHQ Bugzilla 24 Sep '21

24 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=50498 Bug ID: 50498 Summary: Intel Assistive Context-Aware Toolkit (ACAT) v1.00.0 (.NET 4.5 app) setup exits with System.MissingMethodException Product: Wine Version: 6.0-rc6 Hardware: x86-64 URL: https://github.com/01org/acat/releases/download/v1.00. 0/ACATSetup.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Distribution: ArchLinux The setup will finish and after clicking 'Finish' it says it will install Word Predictor and after clicking 'Finish' again this error shows up: Unhandled Exception: System.MissingMethodException: Method not found: void System.ServiceModel.Description.MetadataExporter.set_PolicyVersion(System.ServiceModel.Description.PolicyVersion) at (wrapper remoting-invoke-with-check) presage_wcf_service_system_tray.PresageWCFHostForm..ctor() at presage_wcf_service_system_tray.Program.Main () [0x0000b] in <abe18da6446d4917b2d9283654dbd0f2>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.MissingMethodException: Method not found: void System.ServiceModel.Description.MetadataExporter.set_PolicyVersion(System.ServiceModel.Description.PolicyVersion) at (wrapper remoting-invoke-with-check) presage_wcf_service_system_tray.PresageWCFHostForm..ctor() -- 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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs September 2021