Created attachment 141483 [details] this shows the moment the crash happens Please read everything including the steps to reproduce on the screenshot I attached
The crash recover should result in a crashreport (a dump posted to crashreport.libreoffice.org that is parsed with symbols) we'll need that. If not generated, check the task manager for any soffice.bin instances left running, kill them and retest. Post the linked crash report. Otherwise if you are up to it, you could install the Windows SDK, just the debug tools, and catch the crash dump with linked symbols [1]; and, might need to use the Microsoft sysinternals "procdump" utility [2] to catch the dump with -ma settings to create the dump. Devs won't be able to do a lot with this crash at the 6.0.3.2 x64 build without seeing a dump/stack trace linked to Libreoffice symbols. =-ref-= [1] https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg [2] https://docs.microsoft.com/en-us/sysinternals/downloads/procdump
Also, are you connecting to the HP P1102w network printer via WiFi or Ethernet, or both? And, could you check if with the HP 1102w set as the Windows default printer for the user profile--can you open LibreOffice? And, can you create a Writer document and then use the Format -> Character dialog? Looking at relationship to bug 116679
Does it happen with 6.0.6.2 or 6.1.0.3? Please respond to pinpoint the issue.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20190321
Dear VistaMail1, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp