simple-backup-config.py crashed with NoOptionError in get()

Bug #311429 reported by kh
268
This bug affects 39 people
Affects Status Importance Assigned to Milestone
sbackup (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: sbackup

Sbackup crashed with the above msg after being successfully installed via Synaptic on ubuntu 8.10 on a usb flash drive.
Sbackup is 0.10.5ubuntu2

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/share/sbackup/simple-backup-config.py
InterpreterPath: /usr/bin/python2.5
Package: sbackup 0.10.5ubuntu2
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/sbin/simple-backup-config
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=da_DK.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/sbin/simple-backup-config']
SourcePackage: sbackup
Title: simple-backup-config.py crashed with NoOptionError in get()
Uname: Linux 2.6.27-7-generic i686
UserGroups: backuppc

Revision history for this message
kh (klaus-heide) wrote :
description: updated
Revision history for this message
Nick Jenkins (nickpj) wrote :

Identical problem here - crash reported by apport, with the description "simple-backup-config.py crashed with NoOptionError in get()". Running Ubuntu 8.10; AMD64 Architecture; same traceback/package/ExecutablePath/ProcCmdline/etc. I'm not using a USB flash drive though (just using a normal standard SATA hard disk).
Happens after going System -> Administration -> Simple Backup Config -> then changing the selected radio option on the main "general" tab.

Revision history for this message
CafeNinja (cafeninja) wrote :

When this error occurred on my machine, there was no visible problem in the application interface. It was when I had already clicked on save and then execute. After closing and reopening it would seem that there was a partial backup made and the files.tgz was corrupted as a volume. In my case it may have been while compressing the .tgz that the error occurred since it did not crash the UI.

I've added an exclude statement to the folder where the corruption in the files.tgz occurred (based on the file being extracted that causes the archive to fail extract). I'll run it again and see if there are further issues.

--
CafeNinja

Revision history for this message
CafeNinja (cafeninja) wrote :

The incremental backup that was configured when this error was received ran without issue. I'm going to try and force a full backup now to see if it happens again.

--
CafeNinja

Revision history for this message
MoLE (moleonthehill) wrote :

Seems to be still happening with the latest Karmic updates and python libs.
- identical issue as described by CafeNinja above.

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

Hi,

Can you test the following ?
https://launchpad.net/nssbackup/+announcement/2189
It's NSsbackup. It will be the new version of Sbackup. It's the supported version of Sbackup. We (NSsbackup team) don't change Sbackup anymore. We will push to have NSsbackup replacing Sbackup in the repositories.

It can upgrade previous versions of Sbackup version. But I anyway suggest that you backup your Sbackup confguration and move your backup folder before testing.

Revision history for this message
MoLE (moleonthehill) wrote :

Hi Oumar, your PPA doesn't appear to have packages for karmic koala (ubuntu 9.10) where I noticed the above error. Will you be planning on building packages for karmic, so I can test your latest release?

tags: added: bugpattern-needed
Revision history for this message
PJO (lexicographer) wrote :

This bug continues with Ubuntu 10.04 beta 1 (updated as of 2010-4-02)

I wasn't able to upload a crash report to launchpad after the last crash. I am attaching the report.

Sbackup was a very useful tool and I'm sorry to see it become abandonware. However, I read elsewhere on launchpad that

sudo sbackupd

works perfectly and I've just confirmed this. So, it's really just a question of fixing the crashing user interface that updates the config file and starts the backup job.

CAN SOME PYTHON WIZARD HAVE A LOOK?!

Note: I couldn't attach the original crash file. It seemed to be locked. I managed to open it with gedit and copy it. Here's the traceback:

Traceback:
 Traceback (most recent call last):
   File "/usr/sbin/simple-backup-config", line 578, in on_main_radio_group_changed
     self.parse_conf()
   File "/usr/sbin/simple-backup-config", line 402, in parse_conf
     if str(self.conf.get("general", "stop_if_no_target")) == "1":
   File "/usr/lib/python2.6/ConfigParser.py", line 540, in get
     raise NoOptionError(option, section)
 NoOptionError: No option 'stop_if_no_target' in section: 'general'

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Oumar Aziz OUATTARA : you state in your comment #6 that sbackup is replaced by nssbackup. The ppa given has nssbackup for Jaunty, with no updates for karmic or lucid. We still have sbackup in lucid, with beta2 freeze in effect. Has there been any progress on this? To all appearances, sbackup is a very much alive project being developed on SourceForge: http://sourceforge.net/projects/sbackup/ .

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in sbackup (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
PJO (lexicographer) wrote :

The About info in the program needs to be updated to reflect the changelog (from v0.10.4 to v0.10.5, and hopefully v0.10.6 later).

The traceback details are unchanged apart from the update to python 2.6 in the first traceback report above, which I overlooked earlier. Maybe this could have been looked at earlier? Sorry I do not know python.

Is it too late to hope that this might be fixed in 10.04?! It's such a great little utility -- when it works.

Revision history for this message
alun phillips (acw-phillips) wrote :

Was having the same issues on 10.04 Followed Oumar's advise (#6) and installled nss-backup from ppa, and am very glad to report Backup now fully functional.

tags: added: bugpattern-written
removed: bugpattern-needed
Revision history for this message
PJO (lexicographer) wrote :

I've given up on Sbackup, for now anyway. Back In Time, which is in the Lucid repository is similar but better, with snapshot capability. Also v. simple and easy to use.

Revision history for this message
swarfendor437 (pc-athome) wrote :

simple backup crashed as I was attempting to create backup of Ultimate Edition 2.7 which I had created using unetbootin. I downloaded the restricted drivers for the built in broadcom wireless and was wanting the configuration to be backed up for next usb boot.

swarfendor437

Revision history for this message
Davy Zhu (zhushenli) wrote :

I add one line code to
  def on_main_radio_group_changed(self, *args):
to give stop_if_no_target a initial value.

When click "General"->"Use recommend ...", program will not throw exception. Please check it in your environment.

BTW, is the project dead?

tags: added: patch
Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

No, the project is not dead. In fact, it is more alive than ever. Updated version 0.11.0 is just released (includes status icon, GIO support and more). Have a look at the project's website https://launchpad.net/sbackup You can find source tarballs and links to our PPA there. Read also comment #6 of this bug report.
Thanks.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Thanks for reporting this issue and helping to make sbackup better.

Does this still happens with the latest release of sbackup 0.11.4? Please consider to update, if you are on Lucid you can use our PPA at https://edge.launchpad.net/~nssbackup-team/+archive/ppa.

Thanks.

Changed in sbackup (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Patrick Martin (patrickmmartin) wrote :

Hi: I've moved onto JoliCloud which sits on top of 9.04, I understand, and also Ubuntu 10.4.

Will update and re-test on those environments within the next week or two, so we should have a good resolution before hitting expiry in 59 days.

Thanks, Patrick

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for sbackup (Ubuntu) because there has been no activity for 60 days.]

Changed in sbackup (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.