New question #61376 on NSsbackup:
https://answers.launchpad.net/nssbackup/+question/61376
Hi Jean-Peer,
I'm embarrassed to come and ask for help as soon as my first time with
NSsbackup but I've followed the instructions for installing through Synaptic
and it fails, due to dependency problems.
Public bug reported:
Binary package hint: sbackup
When the target directory contains # (number sign), sbackupd fails with message
"E: Target directory is not writable - please test in simple-config-gnome!"
even though the access rights are set correctly (with no # backup works just
fine).
The
Thank you for taking the time reporting this bug.
At the moment I am unable to confirm this issue with sbackup 0.10.x due
to the lack of a configured SAMBA share.
Moreover, please note, that most development work takes place on the
forked project NSsbackup. It would help a lot if one of you could
** Attachment added: "nssbackup.log.tar.gz"
http://launchpadlibrarian.net/22756011/nssbackup.log.tar.gz
--
no backup is performed
https://bugs.launchpad.net/bugs/330651
You received this bug notification because you are a member of NSsbackup
team, which is subscribed to NSsbackup.
__
Public bug reported:
When I run backup, NSsbackup never finishes it. It pops up a
notification about the backup sessions starting and then that it started
to commit files to disk. Then it starts to use 100 % of CPU and the
directory with the backup is created, except the files.tar.bz2 size is 0
an
The issue occurs spontaneously. Nevertheless, it is based on known
problems sending desktop notifications to users from root/system
services.
** Changed in: nssbackup
Importance: Undecided => Medium
Assignee: (unassigned) => Jean-Peer Lorenz (peer.loz)
Status: New => Triaged
--
No
Public bug reported:
No desktop notifications when running NSsbackup as superuser:
When running NSsbackup as superuser, no desktop notifications appear on
Backup start, failure or Backup ending. The notifications were showed if
NSsbackup is invoked as 'normal' user (from Applications->Utilities).
Thank you for taking the time reporting this bug. These errors will be
corrected as fast as possible.
** Changed in: nssbackup
Importance: Undecided => Low
Assignee: (unassigned) => Jean-Peer Lorenz (peer.loz)
Status: New => Confirmed
--
Cosmetic errors
https://bugs.launchpad.net/
Needs further investigation. Don't no whether this issue is still
present.
** Changed in: nssbackup
Status: Confirmed => Triaged
--
Restore does not gives the good access rights
https://bugs.launchpad.net/bugs/146617
You received this bug notification because you are a member of NSsbacku
Exception handling was added in 0.2 RC3. Nevertheless, showing
notifications for root users does not work as expected so far.
** Changed in: nssbackup
Status: Fix Committed => Fix Released
--
NSsbackup does not properly handle errors from the notification module
https://bugs.launchpad.ne
Bug #319294 status changed in NSsbackup:
Fix Committed => Fix Released
Status change explanation given by Jean-Peer Lorenz:
Exception handling was added in 0.2 RC3. Nevertheless, showing
notifications for root users does not work as expected so far.
https://bugs.edge.launchpad.net/nssbackup
This is also an issue for me, but it's more of a wishlist entry than a
bug since samba shares don't appear to be explicitly supported. My
share requires a password, and it doesn't seem to be saved (despite
selecting remember forever), so I expect this would be a problem.
--
Automatic time-set sb
12 matches
Mail list logo