Description: I'm really interested what the targeted audience for the wizard was In my opinion, way to many confusing choices. The wizard should make - more or less - the decision for people. Instead opening a whole world of possible actions.. I mostly keep it simple; trashing the whole profile. But i'm relying on lots of customization/extensions/replacement lists etc. 1. Make a backup of the user profile automatically (preventing something get lost). And make it a little smarter. Do 'overwrite' a backup automatically. X has a crash, opens safe mode, clicks on 'backup user profile', resets the extensions (he uses many). Concludes still not working, goes back to the wizard, clicks backup again (his extension collection gone.. overwritten) 2. I would opt for go back to factory settings (full profile) as a default. Starting point should be fresh LibreOffice profile. 3. Followed by a list 'except for' the keep the 'advanced' people happy. The other way around would be of course.. go back to factory settings and having an option to restore removed elements: extensions, interface modifications from the backup profile. 4. The 'disable OpenCL/OpenGL' is a fallback. I think? If someone enters the wizard a second time quickly after the first instance, it should give a hint to disable OpenCL/OpenGL or something like that. Or also for cases after replacing VGA? Another approach is ask a lot of questions (but probably rather hard to get right) - Did you recently update LibreOffice? -> - Did you upgrade your video-card -> - Did you recently install a extension -> - Did you recently modify the dialogs -> There is some room for improvement, IMHO. Except I'm unaware of the history of the recovery settings wizard Steps to Reproduce: Help -> Open save mode Actual Results: To many options Expected Results: Simple gui Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.alpha0+ (x64) Build ID: 4475bcd83aac7e033fc5250f268eb922bd471e7b CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: en-US (nl_NL); UI-Language: en-US Calc: CL
*** This bug has been marked as a duplicate of bug 120269 ***