This bug is still marked as Incomplete so we are now going to close this
bug report. Please upgrade to the latest release Karmic 9.10 - If this
bug is still reproducible please reopen the bug by setting the status to
New. Thanks
** Changed in: sbackup (Ubuntu)
Status: Incomplete = Invalid
Is this symptom still reproducible in 8.10 or 9.04?
** Changed in: sbackup (Ubuntu)
Status: New = Incomplete
--
Crash No Such File Or Directory
https://bugs.launchpad.net/bugs/209314
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Reopening because of identical tracebacks under different circumstances
than described in the original bug.
** Changed in: sbackup (Ubuntu)
Status: Invalid = New
--
Crash No Such File Or Directory
https://bugs.launchpad.net/bugs/209314
You received this bug notification because you are a
I suggest reopening this bug. Yesterday, I posted a question about the
same error:
https://answers.launchpad.net/ubuntu/+source/sbackup/+question/30719
I have backed up to an external USB drive (an Iaudio X5 really) directly
connected to my laptop. The symptoms (creation of empty temporary
Thank you for your bug report.
After your comments, I believe I can safely put this bug as invalid.
right ? just tell me if I should reopen it .
Regards
** Changed in: sbackup (Ubuntu)
Assignee: (unassigned) = Oumar Aziz OUATTARA (wattazoum)
Status: New = Invalid
--
Crash No Such
Perhaps the correct action would be to add some checking that the backup
was created successfully. I didn't get a notification that the backup
failed.
Oumar Aziz OUATTARA [EMAIL PROTECTED] wrote: Thank you for your bug report.
After your comments, I believe I can safely put this bug as
** Attachment added: Full crash log
http://launchpadlibrarian.net/12980278/_usr_share_sbackup_simple-restore-gnome.py.0.crash
--
Crash No Such File Or Directory
https://bugs.launchpad.net/bugs/209314
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is NOT a bug, it turns out that the created archive was corrupt.
Manually trying to extract the archive gave me a unexpected end of
file on the files.tgz that sbackup made. Looking closer at it's size,
files.tgz was exactly 2147483647, 1 byte short of 2GB. I bet this
failure occurs when
I just realized that my nas is sharing it's volume over samba, it may
only support a max filesize of 2GB.
--
Crash No Such File Or Directory
https://bugs.launchpad.net/bugs/209314
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Mounting my NAS using cifs instead of cifs seems to have worked.
--
Crash No Such File Or Directory
https://bugs.launchpad.net/bugs/209314
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Mounting my NAS using CIFS instead of SMBFS seems to have worked.
--
Crash No Such File Or Directory
https://bugs.launchpad.net/bugs/209314
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
11 matches
Mail list logo
