Sometimes, the Autorepair on startup fails. The autorepair will trig on each start forever, though. On /failed/ autorepair, it would be great with an option to make it never autorepair again, just so that you don't need to google for undocumented features and look up hidden system files to manually force it not to attempt to autorepair that particular file again.
Aha, so, the Cancel button actually has this effect already - this is not so clear, Cancel sounds more like that you want to Autorepair it on the next app start again. Perhaps this can be clarified somehow.
Hi Mikael, Thanks for the issue and your extra comment. I agree: it is not clear in the text that is on top of that dialog. Set to New. ciao, Cor
Created attachment 102174 [details] add-disable-autorecovery.patch add possibility to --disable-autorecovery before building This controls whether to build document auto-recovery feature or not.
My ideas are more radical. ``I dunno why do you love this useless annoying "feature" so much. Actually, it would be much better to completely remove this functionality from the source.'' I made a patch which turns this "feature" off. But upstream rejected it. So I attached it to this report (maybe somebody will want it too). https://gerrit.libreoffice.org/#/c/10032/
Umm.. in my frame of reference, autorecovery is a very good default functionality. I vote for Cor's suggestion i.e. clarify the description of what the Cancel button actually does.
Caolán McNamara committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=6ac621f1e07c2717d69880866522056996fe9546 Resolves: fdo#80815 rename Cancel and explain what it will do It will be available in 4.4.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
hopefully that helps clarify what the (now renamed) button does