Description: I have just updated LibreOffice for version version 6.1.0.3 on my pc with windows 10 I don't understand why LibreOffice still so often freezeswhen I go to help> Search for updates. I thought that error had been corrected long time ago but that is obviously not the case. I often experience LibreOffice freezing completely when I try and I need to restart LibreOffice. Reproducible: Always User Profile Reset: No Additional Info:
Cannot reproduce. The command terminates correctly in 2-3 seconds on my PC. Versione: 6.1.0.3 (x64) Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 Thread CPU: 8; SO: Windows 10.0; Resa interfaccia: predefinito; Versione locale: it-IT (it_IT); Calc: group threaded
I can't reproduce it in Versión: 6.1.0.3 Id. de compilación: efb621ed25068d70781dc026f7e9c5187a4decd1 Subprocs. CPU: 1; SO: Windows 6.1; Repres. IU: predet.; Configuración regional: es-ES (es_ES); Calc: group threaded To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile ( https://wiki.documentfoundation.org/UserProfile ) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
It happens occasionally from time to time. Can something be dont to make the script/the function more stable? For my sake, it does not need to update automatically as long as it just shows me if there is a new version or not.
*dont = done.
(In reply to Martin from comment #3) > It happens occasionally from time to time. > Can something be dont to make the script/the function more stable? > For my sake, it does not need to update automatically as long as it just > shows me if there is a new version or not. LibreOffice is not updated automatically, in fact, it shows an icon when a new version is available. Did you try to reset your user profile ?
Yes, so far resetting the LibreOffice Profile seems to solve the problem.
(In reply to Martin from comment #6) > Yes, so far resetting the LibreOffice Profile seems to solve the problem. Thanks for retesting with a clean profile Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.