https://bugs.winehq.org/show_bug.cgi?id=57792
Bug ID: 57792 Summary: Unhandled page fault on write access to 05010111 at address 7BC2732E (thread 0118) Product: Wine Version: 10.0-rc6 Hardware: aarch64 OS: MacOS Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: christophe.bronner@videotron.ca
Was trying this command wine /Users/lancelot/Downloads/vs_Community.exe --LayOut "C:\Temp\VS2022Offline" --Lang en-US
but it crashed with the following, I suspect this is the same error encountered when trying to use the GUI.
0118:err:eventlog:ReportEventW L"Application: vs_setup_bootstrapper.exe\nFramework Version: v4.0.30319\nDescription: The process was terminated due to an unhandled exception.\nException Info: System.AccessViolationException\n at Microsoft.Win32.SafeHandles.SafeNCryptProviderHandle.NCryptFreeObject(IntPtr)\n at Micros"... wine: Unhandled page fault on write access to 05010111 at address 7BC2732E (thread 0118), starting debugger... 0118:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 268 1244" (2) Read the Wine Developers Guide on how to set up winedbg or another debugger
https://bugs.winehq.org/show_bug.cgi?id=57792
--- Comment #1 from Rafał Mużyło galtgendo@o2.pl --- Attach whole console output, not just the crashing line - the run-up might be relevant and quite interesting.
https://bugs.winehq.org/show_bug.cgi?id=57792
--- Comment #2 from Rafał Mużyło galtgendo@o2.pl --- ...also, not a blocker.
https://bugs.winehq.org/show_bug.cgi?id=57792
--- Comment #3 from Christophe Bronner christophe.bronner@videotron.ca --- Created attachment 77993 --> https://bugs.winehq.org/attachment.cgi?id=77993 Console log
https://bugs.winehq.org/show_bug.cgi?id=57792
--- Comment #4 from Christophe Bronner christophe.bronner@videotron.ca --- Apologies, I created this pretty late last night and though blocker since it blocked usage of the app, I've reduced it to normal, let me know if there would be a better value for any of those fields.
https://bugs.winehq.org/show_bug.cgi?id=57792
--- Comment #5 from Rafał Mużyło galtgendo@o2.pl --- As always, bug status is more about the impact on the system, not the partcular app...
Anyway:
err:combase:RoGetActivationFactory Failed to find library for L"Windows.Foundation.Diagnostics.AsyncCausalityTracer"
So, it looks like a case of an unimplemented library (or at least relevant reg entry, if the lib already exists in wine).
https://bugs.winehq.org/show_bug.cgi?id=57792
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal
--- Comment #6 from Austin English austinenglish@gmail.com ---
msync: bootstrapped mach port on wine-968fd37-msync. msync: up and running.
This appears to be from https://github.com/marzent/wine-msync/tree/main? Out of tree patches aren't supported on wine-bugzilla.
0148:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems 0148:err:winediag:ntlm_check_version ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution. 0148:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems
These missing dependencies may also be a factor.
https://bugs.winehq.org/show_bug.cgi?id=57792
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Unhandled page fault on |vs_Community.exe crashes on |write access to 05010111 at |MacOS |address 7BC2732E (thread | |0118) |
https://bugs.winehq.org/show_bug.cgi?id=57792
--- Comment #7 from Christophe Bronner christophe.bronner@videotron.ca --- Created attachment 77999 --> https://bugs.winehq.org/attachment.cgi?id=77999 Console log (without patches)
Just running `wine vs_Community.exe`, no patches, on a Windows 10 bottle, with `winetricks corefonts dotnet48` executed before.
https://bugs.winehq.org/show_bug.cgi?id=57792
--- Comment #8 from Christophe Bronner christophe.bronner@videotron.ca --- It's a completely different log, I guess because I'm using the GUI this time? Other possibility is I mixed my terminal windows, I had some with wine 10 and some with Whisky (wine 7.7 + patches).
This time I'm certain I got the Wine 10 log.