sbackup/nssbackup fails if exclude-path contains an equal-sign
Bug #412934 reported by
AllesMeins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nssbackup |
Fix Released
|
Medium
|
Jean-Peer Lorenz | ||
sbackup |
Fix Released
|
Medium
|
Martin Schaaf | ||
sbackup (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
The title says it pretty much. I've added a directory with an equal-sign in its name to my exclude list. This causes sbackup to stop working. Luckily I've noticed it by chance a few days later.
Starting sbackupd from a terminal reports the following:
$ sudo sbackupd
Traceback (most recent call last):
File "/usr/sbin/
dirconfig = dict([ (k, int(v)) for k,v in conf.items(
ValueError: invalid literal for int() with base 10: 'Backups=_/ = 0'
A second problem is, that the directory in question is not displayed in the config-dialog. I had to remove it myself in /etc/sbackup.conf to get everything working again.
Im using Xubuntu 9.04 (amd64)
Related branches
description: | updated |
Changed in sbackup: | |
assignee: | nobody → Martin Schaaf (mascha) |
Changed in nssbackup: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
summary: |
- sbackup fails if exclude-path contains an equal-sign + sbackup/nssbackup fails if exclude-path contains an equal-sign |
Changed in nssbackup: | |
status: | Fix Committed → Fix Released |
Changed in sbackup: | |
status: | New → Fix Committed |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu development version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 412934, and any other logs that are relevant for this particular issue.