SUMMARY In the kup KCM I entered a manual path for my backup /home/kaiuwe/Backups/kup. However, the "kup" folder did not exist, so the plasmoid would just sit there with "Backup destination not available". Once I created the folder, it prompted me whether I would start a backup now. STEPS TO REPRODUCE 1. Go to "Backups" in System Settings 2. Schedule backup or edit one 3. Go to "Destination" tab 4. Choose "Filesystem path" 5. Manually enter a destination that does not exist into the text field, not use the directory picker dialog OBSERVED RESULT It shows a hint that this directory does not exist, prevents me from choosing this location (destination could be automounted, so maybe not a good ideA) or it offers to create it. EXPECTED RESULT It happily accepts the path but then never backs up anything until I manually create the directory SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master as of 2022-08-24
Thanks for reporting! It was indeed created with mounted folders in mind, so a destination folder not existing would be normal at most times. But like you say, the configuration module might be good time to insist that it should exist. It could offer to create the folder, maybe in a warning message.
This looks like a relative to https://bugs.kde.org/show_bug.cgi?id=453919
Git commit 13b10dad891d281e2a0c6aac7c15211bb8dbd692 by Simon Persson. Committed on 24/02/2023 at 00:28. Pushed by persson into branch 'master'. Add warnings to user about problems with filesystem destination Related: bug 445391 M +50 -1 kcm/backupplanwidget.cpp M +3 -0 kcm/backupplanwidget.h https://invent.kde.org/system/kup/commit/13b10dad891d281e2a0c6aac7c15211bb8dbd692