Summary: | Scheduled Backup fails to start on Plasma 6 | ||
---|---|---|---|
Product: | [Applications] kup | Reporter: | Simon Brown <bugs> |
Component: | general | Assignee: | Simon Persson <simon.persson> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | p.r.worrall |
Priority: | NOR | Keywords: | qt6 |
Version First Reported In: | 0.9.1 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Simon Brown
2024-03-11 09:09:02 UTC
It seems as though the backup status indicator doesn't work too well in Plasma 6, see also bug #480546 If I connect and decrypt the storage volume before starting the backup when prompted, it appears to run successfully. What kup does is that when starting to save a backup it first checks if the storage volume is accessible, if not it will ask for the volume to be mounted and it goes back to passive state. If the volume never becomes accessible then kup will never continue with saving data. It sounds to me that perhaps something in the "solid" framework has stopped working in newer versions? That is the library that should ask for password and mount the storage volume. Simon Brown, can you try to enable automatic mounting for your storage device and see if this helps? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |