[Nssbackup-team] [Bug 1179080] Re: sBackup unable to be configured for external media destination

2013-06-26 Thread Jean-Peer Lorenz
*** This bug is a duplicate of bug 1174124 *** https://bugs.launchpad.net/bugs/1174124 ** This bug has been marked a duplicate of bug 1174124 sbackup fails to start -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to

[Nssbackup-team] [Bug 1179080] Re: sBackup unable to be configured for external media destination

2013-06-24 Thread Anton
Hi Jean-Peer, I'll be installing 13.04 in a couple of weeks (will be spending 6 hours in the train to Berlin - perfect time), and will be happy to test things then and there. (At the same time, I may start looking into Mint.) Groetjes, Anton. -- You received this bug notification because you

[Nssbackup-team] [Bug 1179080] Re: sBackup unable to be configured for external media destination

2013-06-23 Thread Jean-Peer Lorenz
** Also affects: sbackup/0.11 Importance: Undecided Status: New ** Changed in: sbackup/0.11 Status: New = Confirmed ** Changed in: sbackup/0.11 Importance: Undecided = High ** Changed in: sbackup Status: New = Confirmed -- You received this bug notification because

[Nssbackup-team] [Bug 1179080] Re: sBackup unable to be configured for external media destination

2013-06-23 Thread Jean-Peer Lorenz
Thanks to all for reporting this issue. I'll look into it and fix it asap! Sorry for any inconvinience. @Alvin Ho (alfkh): maybe it is better to stick to a LTS version (currently 12.04) with long term support and stability? As a side note from the developer view: same holds for me...things are

[Nssbackup-team] [Bug 1179080] Re: sBackup unable to be configured for external media destination

2013-06-11 Thread Marcus Fislage
Just as info. I have exactly the same problem since I upgraded to Ubuntu 13.04. Backup to the standard folder on the laptop works but a new destination cannot be set. -- You received this bug notification because you are a member of Simple Backup Maintainers, which is subscribed to sbackup.

[Nssbackup-team] [Bug 1179080] Re: sBackup unable to be configured for external media destination

2013-06-06 Thread Alvin Ho
Workaround avail, albeit not a very nice 1. Fortunately for me, i installed a 12.04.2LTS partition on the same disk. I managed to boot into that partition restore my data to it. Since it was not a lot of data, I was able to restore it without too much pain. I'm quite a newbie at this, so to me,

[Nssbackup-team] [Bug 1179080] Re: sBackup unable to be configured for external media destination

2013-05-21 Thread Anton
Dear Roger, Are you using sbackup as root (super-user) or as (regular) user? Are there any special (non alphabetical) characters in your directory name(s)? Could you check if you can set the desired local backup target using the configuration file (/etc/sbackup.conf for root, or

Re: [Nssbackup-team] [Bug 1179080] Re: sBackup unable to be configured for external media destination

2013-05-21 Thread Roger McCowan
Dear Anton, I am using sbackup as root, because I want to have regular scheduled backups and that has not been possible with normal user access. Specifically, nothing has changed in my directory structures at all, the only change being from 12.10 to 13.04. All my folder names are alphabetical

Re: [Nssbackup-team] [Bug 1179080] Re: sBackup unable to be configured for external media destination

2013-05-14 Thread Roger McCowan
Hi Catalin, Thank you for the feedback. Unfortunately, the functionality remains affected for me. Although I selected Use custom local backup directory and clicked away the messages that came up a couple of times, selected the external drive, clicked away the messages a couple more times, it

[Nssbackup-team] [Bug 1179080] Re: sBackup unable to be configured for external media destination

2013-05-13 Thread Catalin Hritcu
I have the same problem after the 13.4 update, but it doesn't seem to have affect the functionality of simple backup. I just click away a couple of such messages and then it works fine. -- You received this bug notification because you are a member of Simple Backup Maintainers, which is