This happens because sbackup runs as 'root'. It has a global configuration file, which is shared for all users that run sbackup.
This file is stored in /etc (/etc/sbackup.conf). If sbackup has config files for each user, stored for example, in ~/.sbackup.conf, this kind of bug report wouldn't appear. To make sbackup config file for each user is in our TODO list , and allow it runs with no root privileges too. -- Dapper -> Edgy failure: sbackup configuration file has conflicts https://launchpad.net/bugs/63354 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
