sbackup fails to write to destination drive since 10.04

Bug #575184 reported by Nick Allen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sbackup (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: sbackup

Hi,
Summary to create problem
1. launch simple backup
2. select destination
3. save settings (not sure if this is needed)
4. click 'backup now'
5. check destination for newly created directory

Verbose:
I have been successfully using sbackup for over a year on previous versions of Ubuntu, so assume this problem may be to do with Ubuntu 10.04. sbackup appears to load correctly, but I found I had to re-enter all of my data concerning which folders to backup & where to backup to, which I then successfully saved. However, when clicked on 'backup now' no folder was created on my destination.
 The backup destination is a USB connected standalone hard disk (iomega), and I am able to create & delete folders on it using normal file manager settings (I don't need root privilege) Computer is an asus eee 1000 with SSD hard disk. OS is Ubuntu 10.04 I've also tried launching from a terminal using 'sudo /usr/sbin/simple-backup-config' but this produced the same result - GUI okay, but no files written to iomega disk.
I've searched my system logs but can't find any reference to sbackup which has stumped me a bit! (I think I've searched all of the logs under 'simple' & 'sbackup' as well as 'backup' but couldn't find any reference to this program? If you tell me where to look I'll happily try again & submit anything needed.

Nick

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: sbackup 0.10.5ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Tue May 4 15:13:58 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: sbackup

Revision history for this message
Nick Allen (nick-tallguy) wrote :
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.