[Bug 209314] Re: Crash No Such File Or Directory
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 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 209314] Re: Crash No Such File Or Directory
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 209314] Re: Crash No Such File Or Directory
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 209314] Re: Crash No Such File Or Directory
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 directories when trying to restore etc.) and error messages are similar - everything below File /usr/share/sbackup/srestore.py, line 112 is identical in both cases. I too regard this bug as quite critical. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 209314] Re: Crash No Such File Or Directory
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 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 209314] Re: Crash No Such File Or Directory
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 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 File Or Directory https://bugs.launchpad.net/bugs/209314 You received this bug notification because you are a direct subscriber of the bug. - OMG, Sweet deal for Yahoo! users/friends: Get A Month of Blockbuster Total Access, No Cost. W00t ** Attachment added: unnamed http://launchpadlibrarian.net/12997760/unnamed -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 209314] Re: Crash No Such File Or Directory
** 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 209314] Re: Crash No Such File Or Directory
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 the archive is not extracted and there are no files to copy to the proper location. So perhaps the real bug is that sbackup is unable to create tgz files larger that 2GB? Maybe I didn't notice my backup failed on Ubuntu 7.10 when I created it. sbackup did successfully create an incremental backup using the full backup. I bet sbackup doesn't even check files.tgz when doing an incremental, but just checks what file versions have changed by looking at flist or something. So, the real bug is that sbackup is unable to create tgz files larger that 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 209314] Re: Crash No Such File Or Directory
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 209314] Re: Crash No Such File Or Directory
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 209314] Re: Crash No Such File Or Directory
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
