Lo 7.1 Writer unstable (bug?) on Ubuntu 20.10

LO 7.1 Writer continuously and unexpectedly crashes on Ubuntu 20.10. The problem is that after successfully recovering the files, I see a notice that "Due to an error, Libre Office crashed. All the files you were working on will now be saved. The next time LO is launched, your files will be recovered automatically. The following files will be recovered: … (list of files) … "
When I open a file the next time, the recovery process starts again in an indefinite loop.

Hello,

you state “When I open a file the next time, the recovery process starts again in an indefinite loop.”. This is a clear indication, that your LibreOffice user profile is defect and you need to reset to factory settings.

To reset the user profile perform:

  • Start LibreOffice
  • Start in Safe Mode using Help -> Restart in Safe Mode and confirm the restart using button: Restart
  • Archive your profile expanding Advanced (click on the word Advanced right above Help button) and click Archive User Profile button
  • Select option Reset to factory settings
  • Activate [x] Reset entire user profile
  • Click button Apply Changes and Restart

Hope that helps.

Thanks for the suggestion. However I already uninstalled and reinstalled LO 7.1.3. I hope there will be no more crashes, but in that case I will follow your advice, although I doubt that when I open LO, before accessing the Safe Mode, the recovery process starts looping again. I’ll keep you posted

Just a note:

If a problem is caused by a corrupt user profile, reinstalling LibreOffice won’t help at all, since this action won’t touch the user profile. I understood you remark about looping recovery process that the recovery appears every time you start LibreOffice and if that is a correct understanding of your remark, reinstalling could not have fixed the recovery issue. May be you deleted/renamed $HOME/.config/libreoffie/4 manually but reinstalling wasn’t the solution.

In that sense: My answer wasn’t a “suggestion” but the only solution to fix a corrupt user profile induced issue.

OK, I rest profile and factory settings. So far, so good.