Hi, this is a bug I noticed when trying to backup a file my user didn't have read permissions on. Normally a desktop notification (notify-send) would be displayed containing the path of the problematic file.
However in some cases, parts of the log message are treated as shell commands. For example
# under 1st user account (user1, www-data...)
user1@machine $ touch /mnt/backup_source/afile\ \(1\).txt
user1@machine $ chmod 0600 /mnt/backup_source/afile\ \(1\).txt # not needed if default umask/filemode is 0600# under second user account# set backintime to backup the /mnt/backup_source/ directory, and
maintenance@machine $ backintime backup
Version: 1.1.12
[...]
INFO: Call rsync to take the snapshot
notify-send "Back In Time (dbu) : Profil principal""Error: rsync: send_files failed to open "/mnt/backup_source/afile (1).txt": Permission denied (13)"
sh: 1: Syntax error: "(" unexpected
[...]
INFO: Unlock
INFO: Release inhibit Suspend
Other errors also trigger this bug (example with a filesystem error:)
notify-send "Back In Time (dbu) : Profil principal" "Error: rsync: readlink_stat("/mnt/audio/Volterock & undocument - Vocal Hazard Pack Vol 2/Von Volterock/Dieing 10.wav") failed: Structure needs cleaning (117)"
sh: 1: undocument: command not found
The text was updated successfully, but these errors were encountered:
@buhtz actually it's a backport from master. I ported current master completely from os.system to subprocess.Popen a year ago when I rewrote the majority of snapshots.py
Backintime 1.1.12-2 (Debian stable)
Hi, this is a bug I noticed when trying to backup a file my user didn't have read permissions on. Normally a desktop notification (
notify-send) would be displayed containing the path of the problematic file.However in some cases, parts of the log message are treated as shell commands. For example
Other errors also trigger this bug (example with a filesystem error:)
The text was updated successfully, but these errors were encountered: