“Simple Backup” package fails after Ubuntu upgrade
up vote
0
down vote
favorite
I was happily using Simple Backup (sbackup package) for several years without problems under 32-bit Ubuntu 12.04 LTS in ext3 format (backing up to an ext3 partition in an external drive). Then about a year ago I updated to Ubuntu 14.04 LTS, and sbackup stopped working. Each time I try to back up (ad hoc full back-up) I get the error 'NoneType' object has no attribute 'st_size'. Nothing is written in the designated log folder. There is a normally named back-up file, but it is unreadable and shows no properties.
Shortly after upgrading the OS, I added a second user with administrative rights (not used to call sbackup), so I cannot exclude that this is the reason for the failures. I subsequently deleted the second user, but the back-up folder is still mounted in /media/[back-up partition]/[user]/[back-up folder] instead of /media/[back-up partition]/[back-up folder], but I don't see how this could be a problem.
Perhaps some sort of permissions problem, hope that one of you can help. Thanks and best wishes, John
14.04 upgrade backup
asked Nov 20 at 15:25
user717045
113
add a comment |
up vote
0
down vote
favorite
I was happily using Simple Backup (sbackup package) for several years without problems under 32-bit Ubuntu 12.04 LTS in ext3 format (backing up to an ext3 partition in an external drive). Then about a year ago I updated to Ubuntu 14.04 LTS, and sbackup stopped working. Each time I try to back up (ad hoc full back-up) I get the error 'NoneType' object has no attribute 'st_size'. Nothing is written in the designated log folder. There is a normally named back-up file, but it is unreadable and shows no properties.
Shortly after upgrading the OS, I added a second user with administrative rights (not used to call sbackup), so I cannot exclude that this is the reason for the failures. I subsequently deleted the second user, but the back-up folder is still mounted in /media/[back-up partition]/[user]/[back-up folder] instead of /media/[back-up partition]/[back-up folder], but I don't see how this could be a problem.
Perhaps some sort of permissions problem, hope that one of you can help. Thanks and best wishes, John
14.04 upgrade backup
asked Nov 20 at 15:25
user717045
113
'NoneType' python errors might be due to permissions, but are more likely to be reportable bugs. Use a LiveUSB to test for the bug in Ubuntu 18.10. If the bug still exists in 18.10, then please file a bug report with sufficient detail so others can reproduce the problem on their test systems. (Bugs that cannot be reproduced cannot be fixed.)
– user535733
Nov 20 at 16:27
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I was happily using Simple Backup (sbackup package) for several years without problems under 32-bit Ubuntu 12.04 LTS in ext3 format (backing up to an ext3 partition in an external drive). Then about a year ago I updated to Ubuntu 14.04 LTS, and sbackup stopped working. Each time I try to back up (ad hoc full back-up) I get the error 'NoneType' object has no attribute 'st_size'. Nothing is written in the designated log folder. There is a normally named back-up file, but it is unreadable and shows no properties.
Shortly after upgrading the OS, I added a second user with administrative rights (not used to call sbackup), so I cannot exclude that this is the reason for the failures. I subsequently deleted the second user, but the back-up folder is still mounted in /media/[back-up partition]/[user]/[back-up folder] instead of /media/[back-up partition]/[back-up folder], but I don't see how this could be a problem.
Perhaps some sort of permissions problem, hope that one of you can help. Thanks and best wishes, John
14.04 upgrade backup
asked Nov 20 at 15:25
user717045
113
I was happily using Simple Backup (sbackup package) for several years without problems under 32-bit Ubuntu 12.04 LTS in ext3 format (backing up to an ext3 partition in an external drive). Then about a year ago I updated to Ubuntu 14.04 LTS, and sbackup stopped working. Each time I try to back up (ad hoc full back-up) I get the error 'NoneType' object has no attribute 'st_size'. Nothing is written in the designated log folder. There is a normally named back-up file, but it is unreadable and shows no properties.
Shortly after upgrading the OS, I added a second user with administrative rights (not used to call sbackup), so I cannot exclude that this is the reason for the failures. I subsequently deleted the second user, but the back-up folder is still mounted in /media/[back-up partition]/[user]/[back-up folder] instead of /media/[back-up partition]/[back-up folder], but I don't see how this could be a problem.
Perhaps some sort of permissions problem, hope that one of you can help. Thanks and best wishes, John
14.04 upgrade backup
14.04 upgrade backup
asked Nov 20 at 15:25
user717045
113
asked Nov 20 at 15:25
user717045
113
asked Nov 20 at 15:25
user717045
113
asked Nov 20 at 15:25
user717045
113
asked Nov 20 at 15:25
user717045
113
113
'NoneType' python errors might be due to permissions, but are more likely to be reportable bugs. Use a LiveUSB to test for the bug in Ubuntu 18.10. If the bug still exists in 18.10, then please file a bug report with sufficient detail so others can reproduce the problem on their test systems. (Bugs that cannot be reproduced cannot be fixed.)
– user535733
Nov 20 at 16:27
add a comment |
'NoneType' python errors might be due to permissions, but are more likely to be reportable bugs. Use a LiveUSB to test for the bug in Ubuntu 18.10. If the bug still exists in 18.10, then please file a bug report with sufficient detail so others can reproduce the problem on their test systems. (Bugs that cannot be reproduced cannot be fixed.)
– user535733
Nov 20 at 16:27
'NoneType' python errors might be due to permissions, but are more likely to be reportable bugs. Use a LiveUSB to test for the bug in Ubuntu 18.10. If the bug still exists in 18.10, then please file a bug report with sufficient detail so others can reproduce the problem on their test systems. (Bugs that cannot be reproduced cannot be fixed.)
– user535733
Nov 20 at 16:27
'NoneType' python errors might be due to permissions, but are more likely to be reportable bugs. Use a LiveUSB to test for the bug in Ubuntu 18.10. If the bug still exists in 18.10, then please file a bug report with sufficient detail so others can reproduce the problem on their test systems. (Bugs that cannot be reproduced cannot be fixed.)
– user535733
Nov 20 at 16:27
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094550%2fsimple-backup-package-fails-after-ubuntu-upgrade%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
'NoneType' python errors might be due to permissions, but are more likely to be reportable bugs. Use a LiveUSB to test for the bug in Ubuntu 18.10. If the bug still exists in 18.10, then please file a bug report with sufficient detail so others can reproduce the problem on their test systems. (Bugs that cannot be reproduced cannot be fixed.)
– user535733
Nov 20 at 16:27