This may be a separate bug, but it's worse... [again, I wonder, am I the only one trying to use this as my remote backup solution?!]:
when I run sbackup from the command line, it SILENTLY fails to finish the backup. That is, an incomplete .tgz file is written. After only a couple of minutes, it stops writing. There is no error and sbackupd does not terminate. And the lock file is still there. (Btw, trying your recent version, despite giving an error it did delete what it needed to so that when I ran sbackupd a second time, it went ahead without error. But with this new, bigger problem). So I end up with a "full" backup that is about 30 MB in stead of 1.1 GB. Okay, this new problem happens with the latest v1.3 too. But it didn't used to. ... -- gnomevfs.NotFoundError even when the "test" works in remote backup site https://bugs.launchpad.net/bugs/67814 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
