https://bugs.kde.org/show_bug.cgi?id=482494
Bug ID: 482494
Summary: Running out of space in the middle of a synchronized
rsync backup is not user-friendly
Classification: Applications
Product: kup
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Keywords: usability
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Kup built from source, against Qt6, on Plasma 6.
I did a backup using Kup today that ran out of space in the middle because I
used an external disk that was too small, oops. As a result the backup failed
and communicated this to me via a System notification. But the text of that
notification failed to tell me what was wrong; it simply directed me to the log
file, where I found the following text:
rsync: [sender] write error: Broken pipe (32)
rsync error: error in socket IO (code 10) at io.c(848) [sender=3.2.7]
rsync error: received SIGUSR1 (code 19) at main.c(1609) [generator=3.2.7]
This is also not very helpful. Eventually I figured out on my own that the
issue was the target disk filling up during the backup. This could have been
presented in a more user-friendly manner.
--
You are receiving this mail because:
You are watching all bug changes.
