Comment 4 for bug 726054

I've tried to launch the tar command from console using the configuration files produced by sbackup.
It returned this error:

$ tar --gzip -cS --directory=/ --ignore-failed-read --blocking-factor 20 --totals --files-from=./includes.list --exclude-from=./excludes.list --checkpoint=858 --listed-incremental=./files.snar
gzip: compressed data not written to a terminal. Use -f to force compression.
For help, type: gzip -h
tar: Removing leading `/' from member names
Segmentation fault
$ echo $?
139

Then I've tried to do a full backup, and it worked.
So given that I changed some configuration settings of the backup profile since the last (incremental and successful) backup (e.g. I added and removed some directories), I guess tar didn't like the probable mismatch between the snar file and the present configuration...
Recap: try to change some profile settings and then do a incremental backup. That ___might___ be the matter.