SUMMARY This is a feature request for adding an option to ignore ALL configuration files so KDENLIVE starts in a trully clean state. There's too many files involved in configuration and is really difficult to remember them. There's even a wiki page just for that: https://community.kde.org/Kdenlive/Configuration Looking at the forum/maillist it's obvius that there's a lot of issues resolved removing old configuration files. This problem is even more prominent when testing new versions mixing appimage packages, nightly builds and local repositories. So adding an option to launch KDENLIVE in a clean instance without reading any configuration file or directory should help a lot. Some programs already do that when they detect some problems (firefox with extensions, ardour with plugins). As a workaround I set HOME variable to something like "/tmp/klivetest" but that trick gives other unexpected results. STEPS TO REPRODUCE 1. Execute a version of KDENLIVE 2. Execute another version 3. OBSERVED RESULT Lot of features act weird or don't work at all. EXPECTED RESULT All features work ok. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
This kind of reminds me of the "safe mode" startup option that lots of other applications usually have (e.g. LibreOffice: https://help.libreoffice.org/Common/Safe_Mode)