Description: I am writing and LibreOffice crash for no reason Steps to Reproduce: 1. Open or create document 2. Write some paragraphs 3. Not recover files Actual Results: Depósito con errores 1477583030401000005, tipo 5 Nombre de evento: BEX64 Respuesta: No disponible Identificador de archivo CAB: 0 Firma del problema: P1: soffice.bin P2: 7.5.0.3 P3: 63d28149 P4: ucrtbase.dll P5: 10.0.19041.789 P6: 2bd748bf P7: 000000000007286e P8: c0000409 P9: 0000000000000007 P10: Archivos adjuntos: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCD1.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF5.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF15.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF13.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF33.tmp.txt Es posible que estos archivos estén disponibles aquí: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_soffice.bin_e1f3539628bd196a4544c67e641fb5e1c62ef4d_3e93c176_ffb8e5c6-bdd0-4fd3-8f15-7d590924cbc7 Símbolo de análisis: Nueva búsqueda de una solución: 0 Identificador de informe: 46169fc4-d1f1-4147-858e-4784d78d74ab Estado del informe: 268435456 Depósito con algoritmo hash: f400363318463025b4816df005326245 GUID de CAB: 0 Nombre de la aplicación con errores: soffice.bin, versión: 7.5.0.3, marca de tiempo: 0x63d28149 Nombre del módulo con errores: ucrtbase.dll, versión: 10.0.19041.789, marca de tiempo: 0x2bd748bf Código de excepción: 0xc0000409 Desplazamiento de errores: 0x000000000007286e Identificador del proceso con errores: 0x1ed8 Hora de inicio de la aplicación con errores: 0x01d96cab4447fc7f Ruta de acceso de la aplicación con errores: C:\Program Files\LibreOffice\program\soffice.bin Ruta de acceso del módulo con errores: C:\Windows\System32\ucrtbase.dll Identificador del informe: 46169fc4-d1f1-4147-858e-4784d78d74ab Nombre completo del paquete con errores: Identificador de aplicación relativa del paquete con errores: Intel(R) HD Graphics 530 Expected Results: No errors when i write documents Reproducible: Always User Profile Reset: Yes Additional Info: Ucrtbase.dll: version 10.0.19041.789 Version: 7.5.2.2 (X86_64) / LibreOffice Community Build ID: 53bb9681a964705cf672590721dbc85eb4d0c3a2 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: es-CO (es_CO); UI: es-ES Calc: CL threaded
You report using LO 7.5.2.2 but the error report shows 7.5.0.3. Can you please actually test with the latest version, 7.5.2.2, and if you can still reproduce the crash, test with Skia turned off (in Tools > Options > LibreOffice > View). Thank you.
Dear juagon007, 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
Dear juagon007, 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